Titpea
One banner per wait
Names the request, like Bash: npm run build; gone once answered.
Pulse · Menu-bar status for coding agents
Which agent needs you.
Red means blocked. Your turn stays quiet. Every lamp says why.
Not notarized: allow each new build once with Open Anyway in System Settings → Privacy & Security.
Four lamp colours, in the menu bar.
Only lamps
It never answers prompts, dispatches work, or shows tokens or cost.
This turn, in details
› lists the turn's tools, changed files, plan and subagents.
Orange means stalled
Pi and OpenCode only: twenty minutes without news.
Six agents, own hooks
Four turn red; Codex and Cursor show running and your turn.
Click to go
Its terminal when known, else the app; › opens details and timeline.
v33.0.0 Oct 21, 2026 Release notes ›
Where your data goes.
- State comes only from each agent's own hooks; Pulse reads no session files, transcripts or protected app data.
- The event log, readable only by you, keeps prompts cut to 200 characters with credentials redacted, on this Mac.
- Pulse makes no network connection: no update check, nothing reported. Releases… in Settings only opens the releases page in your browser.
FAQ
Which agents show waiting?
Four: Claude Code, Copilot CLI, OpenCode and Pi, through the hook, plugin or extension each vendor documents. Codex and Cursor show running and your turn only, and say they do not report waiting. A session that started before Pulse shows as process only until its next step.
What does installing the hooks change?
Install them from the setup card on first open or with Install all in Settings → Hooks; for Codex, Pulse writes only ~/.codex/hooks.json, then you run /hooks in Codex to trust it. Only observe-only events are added, and removing them restores each file byte for byte; a file changed since then loses only Pulse's entries.
Why is an agent not turning red?
Open Settings → Hooks. Each agent on this Mac has a row: installed, needs update, failed with its reason, or not installed; the last event Pulse heard from it and when; the last event it ignored and why; and whether the agent reports waiting. Install all brings every row that needs an update up to date. Copy report gives the same as plain text, plus each session's last three events, without paths, prompts, sessions or projects.
Does Ignore answer the agent?
No. Ignore on the banner, like ⌘D in the tray, only stops Pulse reminding you of that wait and withdraws its banner. The prompt still waits in the agent's own window, and Pulse stays in the background.
How do I remove Pulse?
In Settings → Hooks, Remove all restores each agent's untouched files byte for byte; a file you edited since loses only Pulse's entries. Then choose Quit Pulse from the menu-bar icon's right-click menu, drag Pulse.app to the Trash, and delete ~/Library/Application Support/Pulse. If you turned on Open at login, also remove Pulse in System Settings → General → Login Items.
Pulse
Working with agents
Once a coding agent is running.
- Pulse Which one needs you
-
Readout Read what it writes -
celagent Resume on another machine -
Agent Radar Scheduled research