What
Add an opt-in setting so studio code can flash the terminal tab / show a system notification (via standard BEL + OSC 9 escape codes) when an agent turn finishes or pauses on an AskUserQuestion. Off by default; toggled with a new /notifications slash command.
Why
Agent turns can run for several minutes. Right now the only way to know a turn finished or is waiting for input is to keep watching the terminal. A lightweight, dependency-free signal would let users switch away and come back when needed.
How
Proof-of-concept (draft PR to follow): a notifyTerminal() helper writes the escape sequence to stderr, gated behind a notificationsEnabled cli.json flag and guards that keep it from reaching non-terminal consumers (desktop app IPC, remote-session daemon). Wired into both the interactive TUI and headless --json mode.
Manually tested on Windows across a few terminals, results vary:
- Warp — tab flash + system notification
- Git Bash — tab flash only
- PowerShell 7 (x64) — no visible effect
- CMD — no visible effect
macOS/Linux terminals untested.
What
Add an opt-in setting so studio code can flash the terminal tab / show a system notification (via standard BEL + OSC 9 escape codes) when an agent turn finishes or pauses on an
AskUserQuestion. Off by default; toggled with a new/notificationsslash command.Why
Agent turns can run for several minutes. Right now the only way to know a turn finished or is waiting for input is to keep watching the terminal. A lightweight, dependency-free signal would let users switch away and come back when needed.
How
Proof-of-concept (draft PR to follow): a
notifyTerminal()helper writes the escape sequence to stderr, gated behind anotificationsEnabledcli.json flag and guards that keep it from reaching non-terminal consumers (desktop app IPC, remote-session daemon). Wired into both the interactive TUI and headless--jsonmode.Manually tested on Windows across a few terminals, results vary:
macOS/Linux terminals untested.