The Absurd Workaround to Check Model Usage
davidmanheim · x · 2026-07-16
The author vented about the ridiculous lengths they had to go through just to let a model check its own usage stats: taking screenshots, pulling data from another session, and fiddling with permissions even after the model "saw itself being roasted on Twitter," before finally routing to the billing API for an answer.
Replies noted that this isn't just a Claude Code issue; Codex also refuses outright, and Grok initially couldn't see the data either. However, once granted sufficient permissions, they all eventually managed to find the needed info via the billing API.
Related event: LLM Agent Dark Pattern Hides Token Usage to Drive Spending(4 posts)→
More from coding & agent
- Building a Secure AI Agent Gateway: Self-Hosting OAuth for Multiple SaaS Apps — Defiant_Cod_2654 · 2026-07-22
- Rowboat launches as an open-source, local-first AI coworker with memory — ycombinator · 2026-07-22
- Scoble says AI “loops” really means long-running multi-agent workspaces — Scobleizer · 2026-07-22
- Kimi Code opens a waitlist as Moonshot rolls out its coding product — Fabulous_Bonus_8981 · 2026-07-22
- Open-source runtime lets each repo define its own AI code reviewer — ibabufrik · 2026-07-22
- Indie Dev Asks: What's Actually Broken in Your AI Agent's Memory Today? — AcceptableTime7937 · 2026-07-22