English | 한국어 | 中文 | 日本語 | Español

ddiring

Completion notifications that actually tell you which session finished.

Running 5–10 Claude Code sessions across iTerm, Cursor, and a session manager? A bare "task complete" banner is useless — you still have to hunt through every window. ddiring ("띠링" — the Korean ding!) makes each notification answer three questions at a glance: which project folder (title), which terminal or app the session lives in (subtitle), and what you asked it to do (body — a 70-char summary of your last prompt). On macOS with terminal-notifier, click it to jump straight to that app.

Quick Start • Why ddiring? • How it works • Features • Commands • Requirements

---

Quick Start

1. Add the marketplace

/plugin marketplace add https://github.com/fivetaku/gptaku_plugins.git

2. Install

/plugin install ddiring

3. Restart Claude Code

(Hooks and commands only register after a restart.)

4. Use it

Nothing to do — every session now rings when it finishes:

• ✅ my-app / iTerm / "fix the flaky auth test and rerun CI" — done, in iTerm
• ⏸️ blog / Cursor / "waiting for permission" — a session needs you
• Click the notification (macOS + terminal-notifier) to focus that app

Optional, for click-to-focus:

brew install terminal-notifier

Why ddiring?

Multi-session work has one recurring micro-pain: something finished, but the stock notification won't say what or where. Session IDs don't help either — you can't map a3f9c2 to "the refactor I kicked off in Warp". ddiring shows the three things you actually recognize: the folder name, the app name, and your own last prompt.

How it works

A Stop hook fires when a session finishes responding (plus a Notification hook for permission/input waits, shown with ⏸️). The script:

1. reads the transcript tail (200KB first, expanding to 2MB if needed) to extract your last real prompt — tool results, system tags, and interrupt markers are skipped;
2. identifies the host app from the process environment — __CFBundleIdentifier on macOS, env probing (TERM_PROGRAM → WT_SESSION → ConEmuPID, innermost-first to dodge inherited-variable false positives) on Windows;
3. fires the notification: terminal-notifier (clickable) or osascript on macOS, a PowerShell 5.1 WinRT toast on Windows.

Because hooks run the script from a file, mapping fixes apply to already-running sessions immediately — no restart needed.

Features

• 30+ app mappings, research-verified (local Info.plist, Homebrew cask definitions, upstream repo configs): Terminal, iTerm2, VS Code (+Insiders), VSCodium, Cursor, Windsurf (Devin), Antigravity, Warp, Ghostty, Alacritty, kitty, WezTerm, Tabby, Hyper, Zed, JetBrains, Rio, Termius, Wave, Positron, Kiro, Trae, Xcode — plus Claude Code session managers: Paseo, cmux, Conductor, Orca, Sculptor, Superset, Crystal, Waku, Jean, Fletch, Constellagent, GraphCode, Clave, Xum.
• tmux/Zellij pass-through — multiplexer sessions show the host terminal via inherited environment (no separate detection; a tmux server attached from a different app than it started in may show the original host).
• Quiet by default — soft chime at volume 0.2; mute or retune via env vars.
• Windows support (experimental) — PowerShell toast from the Git Bash hook path; the toast backend itself needs no extra install, but prompt extraction needs Python 3 (falls back to a generic message without it). Display-only, not yet verified on real hardware — reports welcome.
• Unknown apps degrade gracefully — falls back to TERM_PROGRAM or the raw bundle ID; one-line fix to add a mapping.
• Self-check that verifies display, not just delivery — a notification can fire successfully and still be swallowed by macOS (screen sharing or mirroring, Focus mode, missing permission), leaving sound with no banner. /ddiring doctor sends a test notification and reads the OS's own verdict to say whether it was actually shown, and if not, exactly why. Runs once automatically on first use.

Commands

Command	What it does
/ddiring	show current status (env config, terminal-notifier presence, detected terminal)
/ddiring test	fire a test notification from this session's transcript
/ddiring doctor	diagnose notifications that fire but never appear (screen sharing/mirroring, Focus, permission)
/ddiring volume 0.1 / mute	change volume / mute

Configuration

Set in the "env" block of your Claude settings file (applies to newly started sessions):

Variable	Default	Meaning
DDIRING_SILENT	0	1 = banner only, no sound (macOS)
DDIRING_VOLUME	0.2	0.0–1.0 (macOS)
DDIRING_SOUND	Glass.aiff	any /System/Library/Sounds/*.aiff (macOS)
DDIRING_HIDE_BODY	0	1 = hide the prompt body (privacy on lock screen / screen share)

Note: notification bodies appear in the OS notification center and on the lock screen — set DDIRING_HIDE_BODY=1 if your prompts are sensitive. First run of /ddiring also installs the marketplace-wide update-notifier hook (shared across gptaku plugins).

Requirements

• macOS (full support) or Windows + Git Bash (experimental); silently no-ops elsewhere
• python3 (ships with macOS) — used for transcript parsing
• Optional: terminal-notifier for click-to-focus (macOS)

License

MIT — see also DISCLAIMER.md.