Grok CLI: tokens, live status and replies
Agent HUD follows Grok CLI's sessions on this Mac: their tokens, when Grok CLI is working and when it replies. Its quota is not read yet.
Updated 2026-10-26
At a glance
| Feature | Grok CLI |
|---|---|
| Tokens and sessions | ✓ |
| Quota | — |
| Live status | ✓ |
| Approvals | — |
| Questions | — |
| Replies | ✓ |
| One click back | — |
| Turns and calls | — |
What you see on the HUD
The HUD shows when Grok CLI is working, and the hover lists its sessions with their tokens. There is no Grok CLI quota on the HUD. The quota of the Grok Bot desktop app is read separately; see Grok Bot.
Which account does it count against?
Agent HUD does not read a Grok CLI account yet. Its tokens count under Grok CLI in your statistics, without an account or plan beside them.
Running turns and replies
The HUD shows Grok CLI working or done, and a finished turn brings a New reply reminder. Both come from the records Grok CLI keeps. One click back and Grok CLI's quota are not available yet. Approvals and questions stay in Grok CLI.
What does Agent HUD read?
The session updates and logs Grok CLI keeps in its own folder, ~/.grok unless GROK_HOME names another. Agent HUD reads no Grok credential and sends no message to a model.
On iPhone and Apple Watch
On the same network as the release, iPhone and Apple Watch show Grok CLI's tokens and sessions without a subscription. With Agent HUD Remote you can also read its conversations, on any network.