{"slug": "i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you", "title": "I built a terminal tool to see your AI coding limits before they stop you", "summary": "A developer built quota, a terminal tool that displays remaining usage for AI coding tools like Claude Code and Codex, reading provider state locally to avoid API calls. The tool aims to prevent mid-task rate limit interruptions by showing quota and reset times at a glance.", "body_md": "The worst moment in a coding session is hitting a rate limit mid-task.\n\nYou're deep in a refactor. Claude Code stops. Or Codex resets. And you spend the next 20 minutes switching tools, losing context, or just waiting. The \"Codex Resets\" thread on Hacker News got 270 points and 175 comments. The pain is widespread.\n\nThe problem isn't the limit — it's that you don't know how close you are until you hit it.\n\nI built [quota](https://github.com/Ozperium/quota) to fix that.\n\n``` bash\n$ quota\n\n  quota — your ai usage, at a glance\n\n  Claude Code   ████████████░░  3h 12m of 5h    reset in 2h 48m\n  Codex         ███░░░░░░░░░░░  3 of 40 reqs    reset in 4h 12m\n  Cursor        ──────────────  not connected\n```\n\nOne command. Shows remaining usage for every AI coding tool you have connected, along with reset times.\n\nYou can also run it in watch mode:\n\n```\nquota watch 30   # re-check every 30 seconds\n```\n\nOr pipe it into scripts:\n\n```\nquota --json | jq '.providers.claude_code.percent_remaining'\n```\n\n`quota`\n\nreads provider state **locally** — no API calls, no accounts, no telemetry. It reads from `~/.claude`\n\nand `~/.codex`\n\ndirectly, the same files the tools themselves write. Everything stays on your machine.\n\n```\nnpm install -g @ozperium/quota\nquota\n```\n\nClaude Code and Codex don't surface remaining quota prominently. You either have to open a browser dashboard or wait for the error. Neither is useful when you're mid-task in a terminal.\n\n`quota`\n\nlives where you work — in the terminal, right next to your code.\n\nGitHub: [https://github.com/Ozperium/quota](https://github.com/Ozperium/quota)\n\nnpm: [https://www.npmjs.com/package/@ozperium/quota](https://www.npmjs.com/package/@ozperium/quota)\n\n*Also in the stack: AgentSpec for testing AI agent behavior, and AICostTracker for tracking what you're spending on AI APIs.*", "url": "https://wpnews.pro/news/i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you", "canonical_source": "https://dev.to/pawfromoz/i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you-3a93", "published_at": "2026-07-23 22:23:44+00:00", "updated_at": "2026-07-23 23:01:55.604047+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "ai-tools"], "entities": ["Ozperium", "Claude Code", "Codex", "Cursor", "quota", "AgentSpec", "AICostTracker"], "alternates": {"html": "https://wpnews.pro/news/i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you", "markdown": "https://wpnews.pro/news/i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you.md", "text": "https://wpnews.pro/news/i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you.txt", "jsonld": "https://wpnews.pro/news/i-built-a-terminal-tool-to-see-your-ai-coding-limits-before-they-stop-you.jsonld"}}