Agent alerts
See when an agent finishes or needs your input while you are watching another terminal or application.
Set up once per host
- Open a Local, WSL or SSH tab on the host where the agent runs.
- Open Settings → Session → Agent integration and choose Set up… for that host. Review the file changes and confirm. When Claude Code or Codex starts on a host that is not set up, the tab offers the same step.
- Press Send test alert, then switch to another tab within five seconds.
The tab you are watching never alerts. Other tabs show the alert text in their subtitle and mark their workspace. On Windows the taskbar button flashes and shows how many tabs are waiting.
What each agent needs
Claude Code sends nothing by default. Agent integration adds its alert hook, which reports finished turns and permission prompts. Codex CLI rings by default; agent integration makes it send the text of its reply or question. Any program can alert with a terminal bell, OSC 9 or OSC 777.
For Gemini CLI, enable general.enableNotifications: true. Inside tmux, enable allow-passthrough on. The terminal must receive the bell or notification sequence for NeuroTerm to show it.
Platform behaviour and troubleshooting
- Windows supports taskbar flashing and an overlay count of tabs needing attention. Linux notification presentation depends on the desktop environment; do not expect the Windows taskbar count.
- If the test works but Claude stays silent, install or update the Claude alert hook on the active host.
- If the test is silent, move away from the active tab and check app alert toggles, operating-system notification permissions and Do Not Disturb.
- Notifications are limited to at most one per tab every ten seconds. Repeated events in that window may not create another notification.
A completion hook waits for Claude’s background agents and workflows to finish. Long-running background shells and monitors do not hold it back.