Sessions with in-notch answers
kilo sessions appear in the notch with live state and tool activity. Permission prompts surface ready to answer: ⌘ A allows, ⌘ N denies. Questions flag the session for attention, and the composer sends follow-up prompts into resumable sessions. Kilo and OpenCode sessions stay cleanly separate, even though the tools are related.
Tokens and cost from the local database
AgentPeek reads Kilo's local session database and shows monthly token and cost totals, plus token volume in the by-day chart. Kilo reports no quota percentage, so the numbers are exactly what Kilo recorded, and daily token budgets and alerts work against them.
Setup and routes
A managed plugin installs at ~/.config/kilo/plugins/agentpeek.js, with Doctor repair. Quick Routes opens the Kilo plugins folder, config, and logs in one click.
Questions
Yes. Kilo Code sessions appear in the Mac notch with live state and tool activity, permission prompts are answered with a keystroke, questions flag the session for attention, and follow-up prompts go out from the composer.
From Kilo's local session database at ~/.local/share/kilo/kilo.db: monthly token and cost totals plus a by-day chart, with no network call and no separate sign-in. Older JSON-backed Kilo installations remain supported. Kilo reports no quota percentage, so AgentPeek shows the counts as Kilo records them.
No. AgentPeek identifies each tool separately, so Kilo and OpenCode sessions appear as themselves, each with its own usage totals, routes, and settings.