Sessions with the full picture
kimi sessions appear in the notch with live state, current activity, files and commands on the timeline, transcripts read from Kimi’s local session logs, and subagents shown under their parent. When Kimi blocks on its own approval prompt, AgentPeek flags the session for attention and jumps you to the right terminal; the composer sends follow-up prompts into resumable sessions.
Kimi usage windows and reset times
AgentPeek reads Kimi’s account-wide five-hour and seven-day limits from its managed usage API. Each bar includes the reset time Kimi reports. AgentPeek uses the Kimi Code sign-in already on your Mac. It also reads local session logs for the by-day token chart and budget alerts.
Setup and routes
Hooks merge into ~/.kimi-code/config.toml as managed entries, or the equivalent path under $KIMI_CODE_HOME, and Doctor repairs them. The managed wiring covers all 16 Kimi hook events, including PermissionRequest, PermissionResult, and Interrupt; approval events remain observation-only and are answered in Kimi’s terminal. Quick Routes covers the active Kimi home: skills, config, mcp.json, logs, and sessions.