Every AI coding limit, in your menu bar.

Tiny macOS 14+ menu bar app that keeps AI coding-provider limits visible and shows when each window resets. Codex, OpenAI, Claude, Cursor, Gemini, Copilot, Grok, GroqCloud, ElevenLabs, Deepgram, z.ai, MiniMax, Kiro, Zed, Vertex AI, Augment, OpenRouter, LiteLLM, LLM Proxy, Codebuff, Command Code, ClinePass, AWS Bedrock, and many newer coding providers. One status item per provider, or Merge Icons mode with a provider switcher. No Dock icon, minimal UI, dynamic bar icons.

• Plan around resets. Per-provider session, weekly, and monthly windows with countdowns to the next reset — stop guessing whether to start that long task.
• Credits, spend, and cost scans. Credit balances, Admin API spend dashboards, provider billing summaries, and local cost scans where the source exposes enough detail.
• Live status. Provider status polling surfaces incident badges in the menu and an indicator overlay on the bar icon.
• Privacy-first. Reuses existing provider sessions — OAuth, device flow, API keys, browser cookies, local files — so no passwords are stored.

• macOS 14+ (Sonoma)

Download: https://github.com/steipete/CodexBar/releases

brew install --cask codexbar

Homebrew formula (Linux today):

brew install steipete/tap/codexbar

Arch Linux AUR package:

yay -S codexbar-cli

Or download release tarballs from GitHub Releases:

• macOS: CodexBarCLI-v<tag>-macos-arm64.tar.gz, CodexBarCLI-v<tag>-macos-x86_64.tar.gz
• Linux (glibc): CodexBarCLI-v<tag>-linux-aarch64.tar.gz, CodexBarCLI-v<tag>-linux-x86_64.tar.gz
• Linux (static musl): CodexBarCLI-v<tag>-linux-musl-aarch64.tar.gz, CodexBarCLI-v<tag>-linux-musl-x86_64.tar.gz

• Open Settings → Providers and enable what you use.
• Install/sign in to the provider sources you rely on: CLIs, browser sessions, OAuth/device flow, API keys, local app files, or provider apps depending on the provider.
• Optional: Settings → Providers → Codex → OpenAI cookies (Automatic or Manual) to add dashboard extras.

Provider toggles and API keys live in the resolved CodexBar config file. New installs use ~/.config/codexbar/config.json; existing ~/.codexbar/config.json installs still load from the legacy path. You can script the same provider list that Settings → Providers uses:

codexbar config providers
codexbar config enable --provider grok
codexbar config disable --provider cursor

For API-key providers, store a key without opening Settings:

printf '%s' "$ELEVENLABS_API_KEY" | codexbar config set-api-key --provider elevenlabs --stdin

set-api-key trims the piped value, stores it with restrictive config-file permissions, and enables the provider by default. Use --no-enable to only save the key, or --api-key <key> for one-off local scripts where shell history is not a concern. See CLI configuration for the full flow.

• Codex — OAuth API or local Codex CLI, plus optional OpenAI web dashboard extras.
• OpenAI — Admin API key usage/cost graphs with legacy credit-balance fallback.
• Azure OpenAI — API key, endpoint, and deployment validation probe.
• Claude — OAuth API, browser cookies, or CLI PTY fallback; session and weekly usage where available.
• Cursor — Browser session cookies for plan + usage + billing resets.
• OpenCode — Browser cookies for workspace subscription usage.
• OpenCode Go — Browser or local SQLite data for Go usage windows.
• Alibaba Coding Plan — Web cookies or API key for coding-plan quotas.
• Alibaba Token Plan — Bailian browser/manual cookies for token-plan credits.
• Qwen Cloud — 5-hour and weekly individual Token Plan usage via browser/manual cookies.
• Gemini — OAuth-backed quota API using Gemini CLI credentials (no browser cookies).
• Antigravity — Local language server probe (experimental); no external auth.
• Droid — Browser cookies + WorkOS token flows for Factory usage + billing.
• Copilot — GitHub device flow + Copilot internal usage API.
• Devin — Chrome localStorage session or manual Bearer token for daily and weekly quotas.
• z.ai — API token for personal/team quota, MCP, 5-hour, and hourly usage windows.
• Manus — Browser session_id auth for credit balance, monthly credits, and daily refresh tracking.
• MiniMax — API token, cookie header, or browser cookies for coding-plan usage.
• T3 Chat — Browser cookies capture for Base and Overage usage buckets.
• ZoomMate — Chrome cookie auto-import or manual cURL capture for credits usage.
• Kimi — Auth token (JWT from kimi-auth cookie) for weekly quota + 5‑hour rate limit.
• Kilo — API token with CLI-auth fallback for Kilo Pass usage.
• Kiro — CLI-based usage; monthly credits + bonus credits.
• Vertex AI — Google Cloud gcloud OAuth with token cost tracking from local Claude logs.
• Augment — Augment CLI or browser cookies for credits tracking and usage monitoring.
• Amp — Browser cookie-based authentication with Amp Free usage tracking.
• Ollama — API key access plus browser cookies for Ollama Cloud usage windows.
• Synthetic — API key quota endpoint for rolling five-hour, weekly token, and search-hourly usage.
• JetBrains AI — Local XML-based quota from JetBrains IDE configuration; monthly credits tracking.
• Warp — API token for GraphQL request limits and monthly credits.
• ElevenLabs — API key for character credits and voice slot usage.
• OpenRouter — API token for credit-based usage tracking across multiple AI providers.
• Windsurf — Browser localStorage session import or local SQLite cache for plan usage.
• Zed — Zed editor Keychain session for plan, edit-prediction quota, billing cycle, and overdue invoices.
• Perplexity — Account usage credits from Perplexity usage data.
• Xiaomi MiMo — Browser cookies for balance and token-plan usage.
• Doubao — API key for Volcengine Ark request-limit probes.
• Sakana AI — Manual Cookie header for 5-hour and weekly quota windows.
• Abacus AI — Browser cookie auth for ChatLLM/RouteLLM compute credit tracking.
• Mistral — Browser cookies for API spend, credit balance, and monthly-plan usage.
• DeepSeek — API key for credit balance tracking (paid vs. granted breakdown).
• DeepInfra — API key for prepaid balance, current-month spend, and spending-limit tracking.
• Moonshot / Kimi API — API key for Moonshot/Kimi API account balance tracking.
• Venice — API key for DIEM or USD balance tracking.
• Codebuff — API token (or ~/.config/manicode/credentials.json) for credit balance + weekly rate limit.
• Crof — API key for dollar credit balance and request quota tracking.
• Command Code — Browser or manual cookies for monthly USD credits from Command Code billing.
• Qoder — Browser or manual cookies for Qoder big model credit usage.
• StepFun — Username + password login for Step Plan rate limits (5‑hour + weekly windows) and subscription plan name.
• AWS Bedrock — AWS access keys or a named AWS profile (SSO/assume-role via the AWS CLI) for Cost Explorer spend, monthly budgets, and optional CloudWatch Claude activity.
• Grok — Grok CLI billing RPC plus grok.com browser-session fallback.
• GroqCloud — API key for Enterprise Prometheus request/token/cache-hit metrics.
• LLM Proxy — API key + base URL for aggregate proxy quota stats and provider breakdowns.
• ClawRouter — API key for monthly budget, spend, requests, tokens, and routed-provider usage.
• sub2api — Self-hosted gateway key quota, subscription limits, wallet balance, and per-key usage.
• Wayfinder — Local router gateway polling for health, per-route breakdown, savings, and decision latency.
• LiteLLM — Virtual key + proxy URL for personal and team budget/spend tracking.
• Deepgram — API key usage summaries across speech, agent, token, and TTS metrics.
• Poe — API key for current point balance and recent points history.
• Chutes — API key for subscription usage, rolling and monthly quota windows, and pay-as-you-go quotas.
• Neuralwatt — API key for subscription kWh usage and prepaid credit balance.
• ZenMux — Management API key for rolling five-hour and seven-day quota windows plus PAYG balance.
• Open to new providers: provider authoring guide.

The menu bar icon is a tiny usage meter. Bar meaning is provider-specific, and errors/stale data can dim the icon or show an incident indicator.

• Multi-provider menu bar with per-provider toggles (Settings → Providers).
• Provider-specific usage meters with reset countdowns.
• Optional Codex web dashboard enrichments (code review remaining, usage breakdown, credits history).
• Inline spend and usage charts for API-backed providers such as OpenAI, Claude Admin API, OpenRouter, LiteLLM, z.ai, MiniMax, Mistral, and AWS Bedrock.
• Configurable cost-usage scans for Codex + Claude, plus reused chart UI for supported provider histories.
• A persistent Settings → Usage & Spend view for local 7/30-day estimates, grouped by native currency and limited to providers that expose cost history.
• Provider status polling with incident badges in the menu and icon overlay.
• Merge Icons mode to combine providers into one status item + switcher.
• Display controls for provider icons, labels, bars, reset-time style, and highest-usage auto-selection.
• Fresh installs default to Adaptive refresh. Existing users keep every valid stored choice, while legacy unset or invalid preferences resolve to 5 minutes. Manual and fixed 1m, 2m, 5m, 15m, and 30m alternatives remain available.
• Bundled CLI (codexbar) for scripts and CI (including codexbar cost --provider codex, claude, or both for local cost usage); macOS and Linux CLI builds available.
• WidgetKit widgets for supported providers.
• Localized app and website with a shared 21-language catalog, automatic website detection, persistent pickers, and RTL support.
• Optional session quota notifications and weekly-reset confetti.
• Privacy-first: on-device parsing by default; browser cookies are opt-in and reused (no passwords stored).

Wondering if CodexBar scans your disk? It doesn’t crawl your filesystem; it reads a small set of known locations (browser cookies/local storage, provider config files, local JSONL logs) when the related features are enabled. Plain Adaptive refresh never inspects local agent activity. The separate Adaptive (agent-aware) option asks before inspecting the running-process list (including command lines) to identify Codex/Claude and reading bounded known-session metadata. Declining returns to plain Adaptive. When allowed with Agent Sessions hidden, CodexBar retains only the latest activity time and discards session paths and identities. Provider tokens and token-account settings live in the CodexBar config file with restrictive file permissions. See the discussion and audit notes in issue #12.

• Full Disk Access (optional): only required to read Safari cookies/local storage for web-based providers. If you don’t grant it, use another supported browser, manual cookies/API keys, OAuth, or CLI/local sources where that provider supports them.
• Keychain access (prompted by macOS):
  • Chromium cookie import needs the browser “Safe Storage” key to decrypt cookies.
  • Claude OAuth bootstrap may read the Claude CLI Keychain item when CodexBar has no usable cached credentials.
  • CodexBar may use Keychain for browser cookie decryption, cached cookie headers, and OAuth/device-flow credentials where those sources require it.
  • How do I prevent those keychain alerts?
    • Open Keychain Access.app → login keychain → search the prompted item (for Claude OAuth, usually “Claude Code-credentials”).
    • Open the item → Access Control → add CodexBar.app under “Always allow access by these applications”.
    • Prefer adding just CodexBar (avoid “Allow all applications” unless you want it wide open).
    • Relaunch CodexBar after saving.
    • Reference screenshot:
  • How to do the same for the browser?
    • Find the browser’s “Safe Storage” key (e.g., “Chrome Safe Storage”, “Brave Safe Storage”, “Microsoft Edge Safe Storage”).
    • Open the item → Access Control → add CodexBar.app under “Always allow access by these applications”.
    • This removes the prompt when CodexBar decrypts cookies for that browser.
  • Last resort — stop all Keychain reads entirely: if "Always Allow" doesn't stick (e.g., macOS resets the ACL after a Chromium update or a partition_id reset), open CodexBar → Settings → Advanced → Keychain access and enable Disable Keychain access. CodexBar will no longer touch the Keychain. Browser-cookie-based providers will be skipped, but Claude/Codex OAuth via the CLI still works (it reads ~/.codex / ~/.claude config files, not the Keychain).
  • Prompt after uninstall? Deleting the app prevents a new launch from that bundle, but an already-running CodexBar process can keep requesting Keychain access until it quits. Check for that process, a Login Item, another installed copy, or a prompt that names a different requesting binary/path. See Keychain prompt troubleshooting for safe checks and what to include in a support report without sharing secrets.
• Files & Folders prompts (folder/volume access): CodexBar launches provider CLIs and local probes for some providers. If those helpers read a project directory or external drive, macOS may ask CodexBar for that folder/volume (e.g., Desktop or an external volume). This is driven by the helper’s working directory, not background disk scanning.
• What we do not request in the background: no Screen Recording or Accessibility permissions; user-triggered helper actions may ask macOS for Automation permission to open Terminal. No passwords are stored (browser cookies are reused when you opt in).

• Providers overview: docs/providers.md
• Provider authoring: docs/provider.md
• Issue labeling guide: docs/ISSUE_LABELING.md
• UI & icon notes: docs/ui.md
• CLI reference: docs/cli.md
• Configuration: docs/configuration.md
• Keychain prompts: docs/keychain-prompts.md
• CLI configuration: docs/cli-configuration.md
• Widgets: docs/widgets.md
• Architecture: docs/architecture.md
• Refresh loop: docs/refresh-loop.md
• Status polling: docs/status.md
• Sparkle updates: docs/sparkle.md
• Packaging: docs/packaging.md
• Development: docs/DEVELOPMENT.md
• Release checklist: docs/RELEASING.md
• Changelog: CHANGELOG.md

• Clone the repo and open it in Xcode or run the scripts directly.
• Launch once, then toggle providers in Settings → Providers.
• Install/sign in to provider sources you rely on (CLIs, browser cookies, OAuth/device flow, API keys, or local app/config files).
• Optional: set OpenAI cookies (Automatic or Manual) for Codex dashboard extras.

Requires macOS 14+ and Swift 6.2+.

./Scripts/package_app.sh        # builds CodexBar.app in-place with ad-hoc signing
open CodexBar.app

Dev loop:

./Scripts/compile_and_run.sh
./Scripts/compile_and_run.sh --test  # also run the sharded test suite before packaging/relaunching
make check                           # SwiftFormat + SwiftLint
make docs-list                       # list docs with frontmatter summaries

CLI install:

# after installing CodexBar.app in /Applications
./bin/install-codexbar-cli.sh

• ✂️ Trimmy — “Paste once, run once.” Flatten multi-line shell snippets so they paste and run.
• 🧳 MCPorter — TypeScript toolkit + CLI for Model Context Protocol servers.
• 🧿 oracle — Ask the oracle when you're stuck. Invoke GPT-5 Pro with a custom context and files.

• Win-CodexBar

• codexbar-waybar — Waybar custom module + GTK4 popover for Hyprland / Sway / other Wayland compositors, built on top of the bundled Linux CLI.
• Codexbar GNOME — GNOME Shell extension that brings CodexBar usage into the desktop panel.
• codexbar-cinnamon-applet — Linux Mint Cinnamon panel applet powered by CodexBar's JSON output.
• noctalia-codex-usage — Noctalia/Quickshell plugin that shows Codex 5-hour and weekly usage limits, built on top of the bundled Linux CLI.
• KodexBar — KDE Plasma widget that shows CodexBar usage in the Plasma panel, built on top of the bundled Linux CLI.
• codexbar-plasmoid — KDE Plasma 6 widget for CodexBar's meter icon, provider switcher, quota windows, pace, credits, local cost, and status, powered by the bundled Linux CLI.

• showy-quota — always-on AI plan quota strips for SketchyBar, tmux, and Zellij (standalone WASM plugin), built on codexbar serve / the bundled CLI.

Inspired by ccusage (MIT), specifically the cost usage tracking.

MIT • Peter Steinberger (steipete)