Track who is using your team's shared Claude Code and Codex subscriptions
ai-usage collects usage of shared Claude Code, Codex and Grok subscriptions from teammates' computers, servers and bots, and shows what is left and who is using how much. Version 0.6.2 added a website.
Source
@SergeyBaus on X · 2026-10-14
Written in our own words. Credit to the original author. Link checked 2026-10-22.
What they did
ai-usage collects usage of shared Claude Code, Codex and Grok subscriptions from teammates' computers, servers and bots, and shows what is left and who is using how much. Version 0.6.2 added a website.
Result (as claimed)
The team can see remaining limits before someone runs out mid-task.
Tools they used
Cost: Claude Code: from $17/mo; OpenAI Codex: free plan, paid from $8/mo; Grok Bot: from $30/mo.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Claude Code, OpenAI Codex, Grok Bot. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Track who is using your team's shared Claude Code and Codex subscriptions What the original author did: ai-usage collects usage of shared Claude Code, Codex and Grok subscriptions from teammates' computers, servers and bots, and shows what is left and who is using how much. Version 0.6.2 added a website. Reported result (as claimed by the author): The team can see remaining limits before someone runs out mid-task. Source: https://x.com/SergeyBaus/status/2110511636897218586 Tools they used: Claude Code, OpenAI Codex, Grok Bot Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Track who is using your team's shared Claude Code and Codex subscriptions What the original author did: ai-usage collects usage of shared Claude Code, Codex and Grok subscriptions from teammates' computers, servers and bots, and shows what is left and who is using how much. Version 0.6.2 added a website. Reported result (as claimed by the author): The team can see remaining limits before someone runs out mid-task. Source: https://x.com/SergeyBaus/status/2110511636897218586 Tools they used: Claude Code, OpenAI Codex, Grok Bot Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Track who is using your team's shared Claude Code and Codex subscriptions What the original author did: ai-usage collects usage of shared Claude Code, Codex and Grok subscriptions from teammates' computers, servers and bots, and shows what is left and who is using how much. Version 0.6.2 added a website. Reported result (as claimed by the author): The team can see remaining limits before someone runs out mid-task. Source: https://x.com/SergeyBaus/status/2110511636897218586 Tools they used: Claude Code, OpenAI Codex, Grok Bot Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to vibe code an app with Claude Code · How to use Claude Code and Codex together · How to build a website with AI agents · How to replace SaaS subscriptions with vibe-coded tools
Related use cases
Manage Claude Code, Codex and Grok agents from one workspace
Built Offrun to run Claude Code, Codex, AGY and Grok Build side by side and see who needs attention and what usage remains.
Use a Grok Bot to orchestrate your Claude and Codex coding threads
A developer uses a Grok Bot as the orchestrator of his Claude and Codex agents in T3 Code. He set up webhooks so the Grok Bot is notified when a thread finishes, then open-sourced it as a template for T3 or plain Claude and Codex CLI threads.
Watch all your coding agents in a calm pixel room on your Mac
Shrine shows what your Claude Code, Codex, OpenCode, Cursor and Grok Bot sessions are doing on your Mac; pushes and merged PRs furnish a small pixel room.
Put Claude Code, Codex and Gemini in one terminal list with live status
A developer built agent manager, a local terminal app that connects to the subscriptions and tools you already have. Instead of separate tabs where one agent sits on an unseen permission prompt, every session appears in one list with live status.