Agent HUD · Guides · Supported clients
Pi usage and quota on Mac
Pi runs on other providers' plans, so its quota is theirs — what Pi contributes is the record of what it actually did.
At a glance
| Quota | Through the Kimi, GLM and Go pools |
|---|---|
| Account | Billing pool |
| Balance or cost | Per-request cost from the log |
| Running · completion | Yes · Yes, with the observer |
| Credentials read | Plan entries only |
What you see
None of its own. Windows arrive through the Kimi, GLM and OpenCode Go pools, depending on which plan paid for the request.
How the account is named
A billing pool, the same pool the plan would have anywhere else.
Running turns and completions
Both running turns and completions are detected, the latter through the observer's turn files.
What Agent HUD reads
Pi's session logs, the turn files its observer writes, and the configuration that says which provider and model a request used.
Common questions
- Why does Pi show the same quota as Kimi or GLM?
- Because it is the same allowance. The pool identifies who pays rather than which program asked, so a plan used from Pi and from its own client is one set of windows.
- What does the observer add?
- It writes a small record when a turn finishes, which is what lets completions be detected for Pi. Without it, sessions still appear but their turns do not close.
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