Agent HUD · Guides · Supported clients
Kimi coding quota on Mac
Kimi's coding plan reports a weekly window plus whatever other windows the service lists, and Agent HUD keeps them under one pool per account.
At a glance
| Quota | Weekly plus listed windows |
|---|---|
| Account | Billing pool, account scoped |
| Running · completion | Yes · Yes |
| Credentials read | Read in memory, never written |
What you see
The weekly window, plus each window the service lists with its own duration. The plan comes from your membership level.
How the account is named
A billing pool scoped to the Kimi account, so an API key and an OAuth login of the same account share one pool rather than splitting into two. When the account cannot be confirmed, the pool stays scoped to the credential and says so.
Running turns and completions
Both running turns and completions are detected.
What Agent HUD reads
The Kimi wire logs, its OAuth slots and its device id. Tokens are never refreshed or written back.
Common questions
- I use Kimi through OpenCode or Pi as well — is it counted twice?
- No. The pool identifies who pays, so the same Kimi plan reached from another program is the same pool and the same windows.
- How are the mainland and global services told apart?
- They are different pools, because they are different services with their own allowances. The realm is part of what identifies the pool, so their windows are never mixed.
Last updated: 2026-09-20 · The behaviour described here is documented in full, with the code it comes from, in Agent HUD Open. providers.md