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.
Win-CodexBar is a Windows system-tray app for keeping AI coding-tool usage visible without opening a dozen dashboards. It ports the spirit of CodexBar to a Tauri + React desktop shell backed by shared Rust provider logic.
48 providers including Codex, Claude, Copilot, OpenRouter, Cursor, Gemini, DeepSeek, MiniMax, Kiro, Antigravity, Groq, and more.
Tray-first workflow with a compact provider grid, usage cards, refresh action, settings shortcut, and quit control.
Provider settings for source selection, credentials, cookie import, token accounts, API keys, regions, and tray-display preferences.
Windows credential protection for app-managed API keys, manual cookies, and token accounts, using user-scoped DPAPI where available.
Browser cookie import for Chrome, Edge, Brave, and Firefox, kept opt-in per provider.
Installed local CLI for scripting usage, cost, config, diagnostics, and loopback integrations.
Installer + portable builds with WebView2 runtime bootstrap, VC++ runtime bootstrap, and SHA-256 checksum files.
Install
Install with Windows Package Manager:
winget install Finesssee.Win-CodexBar
Or download the latest installer/portable build from GitHub Releases.
Installer: CodexBar--Setup.exe
Portable: CodexBar--portable.exe
Checksums: each release includes .sha256 files
Winget distribution is approved through microsoft/winget-pkgs. New versions can take a little time to appear because every Winget update is pinned to a specific release URL and installer hash.
First Run
Launch CodexBar from the Start Menu or portable executable.
Add the matching credential type: OAuth/device login, API key, browser cookies, local CLI login, or token account.
For Claude, browser cookies/sessionKey are preferred because they match Claude's settings-page usage. OAuth and CLI stay available as fallbacks. For CLI-based providers such as Codex and Gemini, sign in with the provider CLI first.
Latest Release
v0.33.2 fixes tray-panel dismissal so the popover closes on focus loss or Escape, without immediately reopening from the same tray click.
# Prerequisites: Node.js + pnpm. Rust and MinGW are installed by the script when needed.
git clone https://github.com/Finesssee/Win-CodexBar.git
cd Win-CodexBar
.\dev.ps1
Useful dev flags:
.\dev.ps1 -Release # optimized build
.\dev.ps1 -SkipBuild # relaunch the last build
CLI examples:
codexbar --help
codexbar diagnose --pretty
codexbar usage -p claude
codexbar usage -p all
codexbar cost -p codex
Installer builds include codexbar.exe as the console CLI and codexbar-desktop.exe as the tray app. Start Menu shortcuts launch the desktop app; terminal commands use codexbar.exe.
Release Builds
For local Windows release builds, use the cached release builder:
The script builds the real Tauri release binary plus the console CLI, verifies signed installer dependencies, packages with Inno Setup, writes installer/portable assets, writes SHA-256 sidecars, and can run a silent install/uninstall smoke test.