Win-CodexBar is a Windows-native desktop application designed to display usage statistics for OpenAI Codex, Claude Code, and over 40 other AI coding tools. It provides developers with real-time visibility of their API session and weekly limits directly from the system tray, ensuring they can monitor and manage their resource consumption efficiently.
Key Features:
Comprehensive Provider Support: Tracks usage across platforms like Codex, Claude, Cursor, Gemini, Copilot, and more.
Dynamic System Tray Icon: Shows current session and weekly usage with a two-bar meter for quick overview.
Browser Cookie Import: Supports Chrome, Edge, Brave, Firefox, and other browsers for seamless credential management.
Credential Hardening: Protects sensitive data using Windows DPAPI for secure storage of API keys and tokens.
Command-Line Interface (CLI): Offers scripting capabilities with codexbar usage and codexbar cost.
WSL Support: Works seamlessly in Windows Subsystem for Linux environments.
Audience & Benefit:
Ideal for developers using AI coding tools to optimize resource management. By keeping usage limits visible at all times, Win-CodexBar helps users avoid overages and stay informed about their API consumption without switching contexts or logging into provider dashboards. It simplifies monitoring across multiple platforms, enabling better cost control and workflow efficiency.
Win-CodexBar can be installed via winget for a seamless setup experience.
Winget distribution is approved through microsoft/winget-pkgs. New releases may take a little time to appear in Winget after the GitHub release is published because each version is pinned to its own installer URL and SHA-256 hash.
Checksums: each release includes .sha256 files for manual verification
The installer includes the desktop app, Microsoft's Evergreen WebView2 bootstrapper, app icon, Start Menu shortcut, uninstall metadata, and the Visual C++ runtime bootstrap needed on clean Windows machines. The portable exe is the same desktop app without installer integration; release builds statically link the WebView2 loader, so portable users only need the Microsoft Edge WebView2 Runtime installed on the machine.
First Run
Launch CodexBar — it sits in the system tray
Click the tray icon to open the usage panel
Open Settings → Providers, enable the services you use
For cookie-based providers, click the provider and use Browser Cookies → Import
For CLI-based providers (codex, claude, gemini), make sure you're logged in
CLI
codexbar usage -p claude # single provider
codexbar usage -p all # all enabled providers
codexbar cost -p codex # local cost from JSONL logs
Providers
Provider
Auth
Tracks
Codex
OAuth / CLI
Session, Weekly, Credits
Claude
OAuth / Cookies / CLI
Session (5h), Weekly
Cursor
Cookies
Plan, Usage, Billing
Factory
Cookies
Usage
Gemini
gcloud OAuth
Quota
Copilot
GitHub Device Flow
Usage
Antigravity
Cookies / LSP
Usage
z.ai
API Token
Quota
MiniMax
API / Cookies
Usage
Kiro
Cookies / CLI
Monthly Credits
Vertex AI
gcloud OAuth
Cost
Augment
Cookies
Credits
OpenCode
Local Config
Usage
Kimi
Cookies
5h Rate, Weekly
Kimi K2
API Key
Credits
Amp
Cookies
Usage
Warp
Local Config
Usage
Ollama
Cookies
Usage
OpenRouter
API Key
Credits
JetBrains AI
Local Config
Usage
Alibaba
Cookies
Usage
NanoGPT
API Key
Credits
Infini
API Key
Session, Weekly, Quota
Perplexity
Cookies
Credits, Plan
Abacus AI
Cookies
Credits
Mistral
Cookies
Billing, Usage
OpenCode Go
Cookies
Usage
Kilo
API Key / CLI
Usage
Codebuff
API Key / Local Config
Credits, Weekly
DeepSeek
API Key
Balance
Windsurf
Local Cache
Daily, Weekly
Manus
Cookies
Credits, Refresh Credits
Xiaomi MiMo
Cookies
Balance, Token Plan
Doubao
API Key
Request Limits
Command Code
Cookies
Monthly Credits, Purchased Credits
Crof
API Key
Credits, Request Quota
StepFun
Oasis Token
5h, Weekly
Venice
API Key
USD / DIEM Balance
OpenAI API
API Key
Credit Balance
Privacy
On-device only — no data sent anywhere except provider APIs
No disk scanning — only reads known config paths and browser cookies
Opt-in cookies — extraction only runs for providers you enable
Protected credential stores — app-managed API keys, manual cookies, and token accounts are written through the secure-file layer; on Windows this uses user-scoped DPAPI where available
Safe diagnostics — diagnostic snapshots expose provider/source/status metadata only, never raw cookies, API keys, bearer tokens, or OAuth values
Verified updates — automatic installer downloads require a GitHub SHA-256 digest and the installer is re-verified immediately before apply
