Supported agents

The capability model#

Not every agent exposes the same surface, and AgentPeek never pretends otherwise. Each integration is described along four capabilities:

• Monitoring: live sessions with state, activity, and timelines. Every supported agent has this.
• In-notch answers: permission prompts, questions, and plans answered from the notch. This works for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Kilo Code, Qwen Code, Pi, Oh My Pi Direct Chat, Cline, Goose Direct Chat, Kiro Direct Chat, Mistral Vibe Direct Chat, and Devin.
• Follow-up prompts: continuing a resumable session from the composer. This works for Claude Code, Codex, Cursor, Grok Build, Kimi Code, Hermes, OpenCode, MiMo Code, GitHub Copilot, Kilo Code, Factory Droid, Qwen Code, Pi, Oh My Pi, Goose, Kiro, Mistral Vibe, and Devin.
• Usage: token, cost, or limit readouts. Usage readouts cover Claude Code, Codex, Cursor, Kimi Code, Hermes, OpenCode, MiMo Code, Kilo Code, Qwen Code, Pi, Oh My Pi, Goose, Kiro, Cline, Mistral Vibe, ZCode, Devin, and Aider when its analytics log is already configured.

Qoder, CodeBuddy, Grok Build, Kimi Code, Hermes, Factory Droid, Oh My Pi, and ZCode surface prompts as observation-only attention flags, with approvals staying in the terminal. When an agent's records expose no usage, its sessions simply appear without usage numbers; AgentPeek never invents a quota, reset window, or cost.

Per-agent guides#

Every agent has its own page covering how it connects, what its sessions show, its prompt boundaries, and its usage sources:

• Claude Code
• Codex
• Cursor
• Qoder
• CodeBuddy
• 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
• Cline
• Mistral Vibe
• ZCode
• Aider
• Devin

Qoder, CodeBuddy, and Gajae Code#

Qoder and CodeBuddy use AgentPeek-owned observation hooks. Gajae Code uses its local SDK discovery file with process detection as a fallback.