01
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.
02
Token totals Kimi never shows you
Kimi Code CLI keeps session wire logs under ~/.kimi/sessions but ships no usage dashboard. AgentPeek reads those logs locally and shows monthly token totals plus token volume in the by-day chart, with no network call and no separate sign-in. Kimi exposes no cost or quota percentage, so you get the honest count instead of an invented bar; daily token budgets and budget alerts still work against the totals.
03
Setup and routes
Hooks merge into ~/.kimi/config.toml as managed entries, repairable from Doctor. Quick Routes covers the Kimi folders that otherwise take digging: skills, config, mcp.json, logs, and sessions.