Kiro CLI and q chat compatibility
AgentPeek recognizes kiro-cli plus the context-proven compatibility command q chat. Start a Kiro conversation and the monitored session stays labeled by project in the notch, with its conversation, model, session tokens, process state, and terminal close at hand.
Hooks belong to selected custom agents
Kiro hooks are fields inside a selected custom-agent JSON file under ~/.kiro/agents or a project’s .kiro/agents. They are not a global built-in-agent hook surface. AgentPeek has no custom-agent selector, so it does not install or mutate those files; Kiro monitoring instead uses process state and local session stores. Those external hooks also expose no native permission-request response channel, so approvals stay in Kiro, with Open Terminal available on the monitored session.
Direct Chat through native Kiro ACP
The session composer launches kiro-cli acp to load a session, send a follow-up prompt, stream its reply, and cancel a turn in flight. The ACP client also carries Kiro’s native permission exchange plus session mode and model controls while it owns that Direct Chat session.
Local folders in Quick Routes
Quick Routes opens Kiro’s skills, agents, prompts, steering, CLI and MCP settings, sessions under ~/.kiro/sessions/cli, and ~/.kiro root.