QuotaKit

QuotaKit is a Columbus Labs app for tracking AI quota, usage, and spend across the tools you use. The Mac app gathers provider data locally, syncs it through iCloud, and the iPhone app turns that data into clear status views, alerts, share cards, and widgets.

This repository is the Columbus Labs QuotaKit codebase. It preserves upstream CodexBar history, but QuotaKit releases, bundle identifiers, iCloud containers, StoreKit products, and setup links are owned by Columbus Labs.

Get QuotaKit

• Mac setup: columbus-labs.com/quotakit/mac
• Mac releases: github.com/ColumbusLabs/QuotaKit/releases/latest
• Source repository: github.com/ColumbusLabs/QuotaKit

Install QuotaKit on your Mac first. After iCloud Sync is enabled on the Mac, the iPhone app can show synced quota data and send quota notifications.

Highlights

• Multi-provider quota tracking for Codex, Claude, Cursor, Gemini, Grok, OpenAI, Vertex AI, Mistral, Perplexity, OpenRouter, LiteLLM, ElevenLabs, Deepgram, and more.
• iCloud sync from Mac to iPhone, including quota windows, reset timing, provider status, spend, and account metadata.
• iPhone alerts when a provider runs out of quota or becomes available again.
• Cost dashboards with daily spend, model mix, provider share, and renewal-cycle progress.
• QuotaKit Pro widgets for Home Screen and Lock Screen status at a glance.
• Share cards for usage and cost views.

How It Works

1. Install QuotaKit on your Mac.
2. Enable the providers you use in Mac settings.
3. Turn on iCloud Sync.
4. Open QuotaKit on iPhone with the same iCloud account.

The Mac app does the provider-side work. The iPhone app is a companion that reads synced data, displays it clearly, and sends notifications.

Privacy

QuotaKit is designed around local collection and private sync. Provider credentials, browser sessions, local logs, and account data are read only for the providers you enable. Synced quota data stays in your iCloud account.

Some providers may require local permissions on macOS, such as access to browser cookies, provider CLI credentials, or Keychain items. Those permissions are used for quota collection and are not a general disk scan.

Development

This repo contains both the Mac app and the iOS companion app. iOS-specific work lives under CodexBarMobile/.

Common checks:

./Scripts/lint.sh lint

xcodebuild -project CodexBarMobile/CodexBarMobile.xcodeproj \
  -scheme CodexBarMobile \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro' \
  CODE_SIGNING_ALLOWED=NO test

Generate the iOS project after editing CodexBarMobile/project.yml:

cd CodexBarMobile
xcodegen generate

Documentation

Provider setup notes and Mac provider internals live in docs/providers.md.

• 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.
• 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.
• Kimi — Auth token (JWT from kimi-auth cookie) for weekly quota + 5‑hour rate limit.
• Kimi K2 (unofficial) — Legacy API key flow for credit-based usage totals.
• 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.
• CrossModel — API key wallet balance with daily, weekly, and monthly spend.
• 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).
• 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.
• 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.
• Open to new providers: provider authoring guide.

Upstream And Credits

QuotaKit is derived from:

• steipete/CodexBar

Columbus Labs maintains QuotaKit as a product fork with its own releases, setup flow, bundle identifiers, and support surface.

The Git history intentionally preserves upstream commits and contributors. That is why GitHub may show thousands of historical commits and many contributors even though Columbus Labs owns the QuotaKit product boundary.

See OPEN_SOURCE_CREDITS.md for recommended user-facing attribution copy and QuotaKit's product-boundary guidance.

License

MIT. See LICENSE.