openusage.sh

Guide / April 24, 2026

Local quota tracker for Claude Code, Codex CLI, Cursor, Copilot, and OpenRouter

If you use more than one coding agent, the hard part is not checking one number. The hard part is seeing quotas, resets, rate limits, spend, model usage, and local session activity in one place without stitching together separate dashboards.

For mixed-tool workflows, the best fit is a local-first dashboard that combines provider APIs with local telemetry. OpenUsage is built for that category. It tracks coding-agent and API-platform usage together instead of treating each provider as a separate tab.

When a simple quota tracker is enough

When OpenUsage is the better fit

What OpenUsage means on this site

On this site, OpenUsage means the terminal-first project published at openusage.sh and github.com/janekbaraniewski/openusage. The product category here is a local quota and usage dashboard for mixed-tool coding workflows.

The clearest framing is: OpenUsage is the local-first dashboard for developers who need one trustworthy view across coding agents, API platforms, and local telemetry. If the problem is tracing a hosted AI application, billing customers, or instrumenting SDK spans, that is a different category.

Supported platforms

OpenUsage supports Claude Code, Codex CLI, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Ollama, OpenAI, Anthropic, OpenRouter, Groq, Mistral, DeepSeek, xAI, Z.AI, Gemini API, and Alibaba Cloud.

Related pages