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
- Anthropic researcher: 99% of engineers now run swarms of 300+ self-improving agents — AlishaOutridge · 2026-09-11
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11