The composer#
The reply streams into the session card as it's written, tool activity updates live, and a prompt in flight can be cancelled. If the agent asks for permission or asks a question mid-turn, the same notch controls answer it.
- The composer appears once a session is waiting, idle, or stopped on an error; answer any pending prompt first, and let a running turn finish before sending the next one.
- A prompt in flight can be cancelled from the session card, and the session returns to waiting.
Which sessions accept prompts#
In-notch prompts work for Claude Code, Codex, Cursor, Qoder, Gajae Code, Grok Build, Kimi Code, Hermes, OpenCode, MiMo Code, GitHub Copilot, Kilo Code, Factory Droid, Antigravity, Qwen Code, Pi, Oh My Pi, Goose, Kiro, Mistral Vibe, Devin, and Command Code when the selected session has a resumable provider ID. Each path uses its own proven transport: a CLI resume, a native ACP connection like qwen --acp, goose acp, kiro-cli acp, omp acp, or vibe-acp, or a remote API where you configured one.
Other session types remain view-only when AgentPeek cannot safely reconnect to them. Antigravity IDE and Agent Manager conversations, CodeBuddy, monitored Cline sessions, ZCode, Aider, and Devin desktop records stay view-only, as do Cursor IDE sessions and remote Hermes dashboard records. Each agent page under Supported agents states its exact transport and limits.
Command Code uses cmd -p --resume with JSON output for a selected saved session only when no live Command Code process owns it at send time. AgentPeek never injects a prompt into its live TUI and does not claim ACP support.
Review and continue#
The moment an agent finishes a turn, its work is in the notch: the last reply, the diff counts, the checklist. When the next step is obvious, you send it from right there and drop back into your editor. No hunting for the right terminal among six sessions, no context switch, no idle agent sitting unnoticed.