Kimi: quota, live status and replies
Agent HUD reads Kimi Code's sessions, shows when it is working and when it replies, and shows the limits of your Kimi Code plan.
Updated 2026-10-29
At a glance
| Feature | Kimi |
|---|---|
| Tokens and sessions | ✓ |
| Quota | ✓ |
| Live status | ✓ |
| Approvals | — |
| Questions | — |
| Replies | ✓ |
| One click back | — |
| Turns and calls | — |
What you see on the HUD
Your Kimi Code plan reports its limits, such as the five-hour window, the monthly total and, on older plans, the week. The most used of them sets Kimi's colour in the glow, and the hover lists them with their resets, beside Kimi's sessions and their tokens.
Which account does it count against?
The Kimi Code plan behind the sign-in or API key Kimi Code already holds. Agent HUD asks the plan's own usage service with it, on the Kimi platform that key belongs to; it signs in to nothing and refreshes no token. Usage on Kimi's China platform is priced from the China list, and on the international platform from the international list.
Running turns and replies
The HUD shows Kimi working or done, and a finished turn brings a New reply reminder. Both come from the logs Kimi Code keeps. One click back is not available for Kimi, and approvals and questions stay in Kimi Code.
What does Agent HUD read?
Kimi Code's session logs in its own folder, for tokens and sessions. For the quota, its existing sign-in or the key in KIMI_CODE_API_KEY. No message goes to a model.
On iPhone and Apple Watch
On the same network as the release, iPhone and Apple Watch show Kimi's quota, tokens and sessions without a subscription. Agent HUD Remote shows them on any network.