Agent HUD · Guides · Supported clients
CodeBuddy and WorkBuddy usage on Mac
CodeBuddy and WorkBuddy keep the same kind of records in their own directories, and Agent HUD keeps them apart.
At a glance
| Quota | None |
|---|---|
| Account | None |
| Running · completion | No · CodeBuddy Stop hook |
| Credentials read | None |
What you see
None for either.
How the account is named
None.
Running turns and completions
Running turns are not detected for either. CodeBuddy reports completions through its Stop hook; WorkBuddy does not.
What Agent HUD reads
The project transcripts under each client's own configuration directory, with sub-agent transcripts joined to the session that started them. Tool results are skipped, and the IDE extension logs and the WorkBuddy database are not read. No credentials are read.
Common questions
- Are CodeBuddy and WorkBuddy combined into one client?
- No. They stay separate sources, so their sessions and token usage are never mixed, even though they record the same way.
- Why does neither show quota?
- Their transcripts carry no billing attribution. Sessions, turns and token counts are read as usual; there is simply nothing that says what the allowance is.
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