z.ai
API token-based provider for z.ai quota tracking.Features
- Tokens limit (primary window)
- Time limit / MCP window (secondary, if tokens also present)
- API region selection (global or BigModel China mainland)
- Custom quota URL override
Authentication
- Settings
- Environment Variable
- Config File
- Preferences → Providers → z.ai
- Enter your API token
- Select API region (Global or China)
API Endpoints
- Global:
GET https://api.z.ai/api/monitor/usage/quota/limit - China:
GET https://open.bigmodel.cn/api/monitor/usage/quota/limit - Custom: Set
Z_AI_QUOTA_URLenvironment variable - Host override: Set
Z_AI_API_HOSTenvironment variable
Kimi
Browser cookie-based provider for Kimi For Coding.Features
- Weekly request quota tracking
- 5-hour rate limit (300 minutes)
- Membership tier display (Andante, Moderato, Allegretto)
- Automatic and manual authentication
Authentication
- Automatic (Recommended)
- Manual Token
- Environment Variable
- Preferences → Providers → Kimi → Cookie source: Automatic
- Log in to https://www.kimi.com/code in your browser
- CodexBar imports cookies from Arc, Chrome, Safari, Edge, Brave, or Chromium
API Details
- Endpoint:
POST https://www.kimi.com/apiv2/kimi.gateway.billing.v1.BillingService/GetUsages - Authentication: Bearer token from
kimi-authcookie
Membership Tiers
| Tier | Price | Weekly Quota |
|---|---|---|
| Andante | ¥49/month | 1,024 requests |
| Moderato | ¥99/month | 2,048 requests |
| Allegretto | ¥199/month | 7,168 requests |
Kilo
API and CLI-backed provider for Kilo usage tracking.Features
- Auto-fallback from API to CLI auth
- Plan and activity tracking
- Configurable source mode (auto, api, cli)
Authentication
- API Token
- CLI Session
~/.codexbar/config.json:Source Modes
- Auto (default): Tries API first, falls back to CLI on 401/403 or missing credentials
- API: API token only
- CLI: CLI session only
API Details
- Endpoint:
https://app.kilo.ai/api/trpc - Authentication: Bearer token from config or environment
Kimi K2
API key-based provider for Kimi K2 credit tracking.Features
- Credit usage tracking (consumed / remaining)
- No explicit reset timestamp
Authentication
- Settings
- Environment Variable
Preferences → Providers → Kimi K2 → Enter API key
API Details
- Endpoint:
GET https://kimi-k2.ai/api/user/credits - Headers:
Authorization: Bearer <api_key>,Accept: application/json - Response header:
X-Credits-Remaining
Kiro
CLI-based provider for AWS Kiro usage tracking.Features
- Monthly credits percentage tracking
- Bonus credits tracking
- Plan name display (e.g., “KIRO FREE”)
- AWS Builder ID authentication via CLI
Authentication
- Install
kiro-cli - Log in with AWS Builder ID:
- CodexBar runs
kiro-cli chat --no-interactive "/usage"
CLI Command
Output Format
Kiro CLI returns ANSI-decorated usage table:- Monthly credits: percentage bar + reset date
- Bonus credits: consumed/total + expiry days
Status Page
- Manual link to AWS Health Dashboard
- No auto-polling
Vertex AI
Google Cloud OAuth provider for Vertex AI quota tracking.Features
- Cloud Monitoring quota usage (time-series metrics)
- Token cost tracking from local Claude logs (Vertex AI entries)
- Automatic project discovery
Authentication
- Install and configure gcloud:
- CodexBar reads
application_default_credentials.jsonfrom gcloud config directory
API Endpoints
- Cloud Monitoring timeSeries:
- Usage:
serviceruntime.googleapis.com/quota/allocation/usage - Limit:
serviceruntime.googleapis.com/quota/limit - Resource:
consumer_quotawithservice="aiplatform.googleapis.com"
- Usage:
Token Cost Tracking
Vertex AI Claude usage is logged to~/.claude/projects/ alongside direct Anthropic API usage.
Detection methods:
- Model name format (primary): Vertex AI uses
@as version separator- Vertex AI:
claude-opus-4-5@20251101 - Anthropic:
claude-opus-4-5-20251101
- Vertex AI:
- Metadata fields (fallback):
metadata.provider: "vertexai"or keys containingvertex/gcp
- Enable Vertex AI provider in Settings → Providers
- Enable “Show cost summary” in Settings → General
- Use Claude Code with Vertex AI model names (with
@format)
Environment Variables
GOOGLE_CLOUD_PROJECTGCLOUD_PROJECTCLOUDSDK_CORE_PROJECT
Augment
Browser cookie-based provider with automatic session keepalive.Features
- Credits tracking and monthly limits
- Usage monitoring (credits consumed)
- Plan information display
- CLI integration (
auggie account status) - Automatic session keepalive (prevents cookie expiration)
- Multi-browser support: Chrome, Chrome Beta, Chrome Canary, Arc, Safari
Authentication
- Automatic (Recommended)
- Auggie CLI
- Preferences → Providers → Augment → Enable
- Cookie source: Automatic
- Log in to https://app.augmentcode.com in Chrome Beta, Chrome, or Arc
Cookie Names
_session(legacy)auth0,auth0.is.authenticated,a0.spajs.txs(Auth0)__Secure-next-auth.session-token,next-auth.session-token(NextAuth)__Host-authjs.csrf-token,authjs.session-token(AuthJS)session,web_rpc_proxy_session(Augment-specific)
Session Keepalive
- Check interval: Every 5 minutes
- Refresh buffer: Refreshes 5 minutes before cookie expiration
- Rate limiting: Minimum 2 minutes between refresh attempts
- Session cookies: Refreshed every 30 minutes (no expiration date)
API Endpoints
- Credits:
https://app.augmentcode.com/api/credits - Subscription:
https://app.augmentcode.com/api/subscription
Amp
Browser cookie-based provider for Amp Free usage tracking.Features
- Amp Free daily usage meter
- Time-to-full reset countdown
- Hourly replenishment rate
Authentication
- Automatic
- Manual
- Preferences → Providers → Amp → Enable
- Cookie source: Auto (default)
- Log in to https://ampcode.com in Safari or Chromium-based browser
API Details
- Endpoint:
https://ampcode.com/settings - Parses embedded
freeTierUsagepayload from HTML - Computes time-to-full from hourly replenishment rate
JetBrains AI
Local XML-based provider for JetBrains IDE quota tracking.Features
- Monthly credits tracking
- Refill date countdown
- Auto-detects installed JetBrains IDEs
- Uses most recently modified IDE
Supported IDEs
- IntelliJ IDEA
- PyCharm
- WebStorm
- GoLand
- CLion
- DataGrip
- RubyMine
- Rider
- PhpStorm
- RustRover
- Android Studio
- Fleet
- Aqua
- DataSpell
Data Source
File locations:- macOS:
~/Library/Application Support/JetBrains/ - macOS (Android Studio):
~/Library/Application Support/Google/ - Linux:
~/.config/JetBrains/ - Linux (Android Studio):
~/.config/Google/
<IDE_BASE>/options/AIAssistantQuotaManager2.xml
XML Structure
quotaInfoattribute (JSON):type,current,maximum,tariffQuota.available,untilnextRefillattribute (JSON):type,next,tariff.amount,tariff.duration
Settings
- IDE Picker: Auto-detected IDEs list or “Auto-detect” (default)
- Custom Path: Manual base path override
Constraints
- Requires JetBrains IDE with AI Assistant enabled
- XML file only exists after AI Assistant usage
- Internal file format may change between IDE versions
OpenRouter
API token-based provider for OpenRouter credit tracking.Features
- Credit usage percentage tracking
- Balance display (total credits - usage)
- Rate limit information
- Multi-provider AI model access (OpenAI, Anthropic, Google, Meta, etc.)
Authentication
- Environment Variable
- Settings
- Config File
API Endpoints
-
Credits API (
/api/v1/credits):- Returns total credits purchased and total usage
- Balance = total_credits - total_usage
-
Key API (
/api/v1/key):- Returns rate limit information
Environment Variables
| Variable | Description |
|---|---|
OPENROUTER_API_KEY | Your OpenRouter API key (required) |
OPENROUTER_API_URL | Override base API URL (defaults to https://openrouter.ai/api/v1) |
OPENROUTER_HTTP_REFERER | Client referer sent as HTTP-Referer header |
OPENROUTER_X_TITLE | Client title sent as X-Title header (defaults to CodexBar) |
Notes
- Credit values are cached on OpenRouter’s side and may be up to 60 seconds stale
- Pre-purchase credits for usage
- Rate limits: 10+ credits = 1000 free model requests/day
Status Page
- Manual link to status.openrouter.ai
- No auto-polling yet
Antigravity
Local language server probe for Antigravity usage tracking.Features
- Model-specific quota tracking (Claude, Gemini Pro Low, Gemini Flash)
- Local-only (no external authentication)
- Automatic port discovery
- HTTPS and HTTP support
How It Works
-
Process detection:
- Finds
language_server_macosprocess with Antigravity markers - Extracts
--csrf_tokenand--extension_server_portflags
- Finds
-
Port discovery:
- Runs
lsof -nP -iTCP -sTCP:LISTEN -p <pid> - Probes all listening ports
- Runs
-
Connect port probe (HTTPS):
POST https://127.0.0.1:<port>/exa.language_server_pb.LanguageServerService/GetUnleashData- Headers:
X-Codeium-Csrf-Token: <token>,Connect-Protocol-Version: 1 - First 200 OK response selects the connect port
-
Quota fetch:
- Primary:
GetUserStatus - Fallback:
GetCommandModelConfigs - Retries over HTTP on
extension_server_portif HTTPS fails
- Primary:
Model Mapping Priority
- Claude (label contains
claudebut notthinking) - Gemini Pro Low (label contains
pro+low) - Gemini Flash (label contains
gemini+flash) - Fallback: lowest remaining percent
UI Mapping
- Primary: Claude quota
- Secondary: Gemini Pro quota
- Tertiary: Gemini Flash quota
Constraints
- Internal protocol (fields may change)
- Requires
lsoffor port detection - Local HTTPS uses self-signed cert (insecure TLS allowed)
- Requires Antigravity app running
Status Page
- Google Workspace incidents for Gemini product
Droid (Factory)
Web-based provider for Factory (Droid) usage tracking.Features
- Standard and Premium token usage tracking
- Billing window with reset date
- Multiple authentication fallback paths
- WorkOS token minting support
Authentication Methods (Fallback Order)
- Cached cookie header (Keychain)
- Stored session (
~/Library/Application Support/CodexBar/factory-session.json) - Stored bearer token (same session file)
- Stored WorkOS refresh token (same session file)
- Local storage WorkOS tokens (Safari + Chrome/Chromium/Arc leveldb)
- Browser cookies (Safari only) for Factory domains
- WorkOS cookies (Safari) to mint tokens
- Browser cookies (Chrome, Firefox) for Factory domains
- WorkOS cookies (Chrome, Firefox) to mint tokens
Cookie Domains
factory.aiapp.factory.aiauth.factory.ai
Session Cookie Names
wos-session__Secure-next-auth.session-tokennext-auth.session-token__Secure-authjs.session-token__Host-authjs.csrf-tokenauthjs.session-tokensessionaccess-token
API Endpoints
Base URL candidates (tried in order):https://auth.factory.aihttps://api.factory.aihttps://app.factory.ai
GET <baseURL>/api/app/auth/me- Org + subscription metadata + feature flags
POST <baseURL>/api/organization/subscription/usage- Body:
{ "useCache": true, "userId": "<id?>" } - Standard + Premium token usage and billing window
- Body:
WorkOS Token Minting
client_id: one ofclient_01HXRMBQ9BJ3E7QSTQ9X2PHVB7orclient_01HNM792M5G5G1A2THWPXKFMXBgrant_type:refresh_tokenrefresh_token: from local storage or session store- Optional:
organization_id,useCookie: true
Local Storage WorkOS Tokens
Safari:- Root:
~/Library/Containers/com.apple.Safari/Data/Library/WebKit/WebsiteData/Default - Finds
originfiles containingapp.factory.aiorauth.factory.ai - Reads
LocalStorage/localstorage.sqlite3
- Roots:
~/Library/Application Support/<Browser>/User Data/<Profile>/Local Storage/leveldb - Scans LevelDB files for
workos:refresh-tokenandworkos:access-token
Snapshot Mapping
- Primary: Standard usage ratio
- Secondary: Premium usage ratio
- Reset: Billing period end date
Status Page
OpenCode
Browser cookie-based provider for OpenCode usage tracking.Features
- Rolling 5-hour usage window (session)
- Weekly usage window
- Automatic workspace detection
- Browser cookie import with caching
Authentication
- Automatic
- Workspace Override
- Log in to opencode.ai in Chrome
- Enable OpenCode in Settings → Providers
- CodexBar automatically imports and caches cookies
API Endpoints
POST https://opencode.ai/_server- Workspaces: function ID
def39973159c7f0483d8793a822b8dbb10d067e12c65455fcb4608459ba0234f - Subscription: function ID
7abeebee372f304e050aaaf92be863f4a86490e382f8c79db68fd94040d691b4
- Workspaces: function ID
Usage Mapping
- Primary window: Rolling 5-hour usage (
rollingUsage.usagePercent, resets inrollingUsage.resetInSec) - Secondary window: Weekly usage (
weeklyUsage.usagePercent, resets inweeklyUsage.resetInSec)
Notes
- Responses are
text/javascriptwith serialized objects (parsed via regex) - Cookie import defaults to Chrome-only to avoid browser prompts
- Cached in Keychain (
com.steipete.codexbar.cache, accountcookie.opencode)
Warp
API token-based provider for Warp credit limits.Features
- Monthly credits usage tracking
- Next refresh time display
- Unlimited plan detection
- Token-based authentication
Authentication
- Settings
- Environment Variable
- Open Settings → Providers
- Enable Warp
- In Warp, go to Profile → Settings → Platform → API Keys
- Create an API key (starts with
wk-...) - Enter the key in CodexBar
API Endpoint
POST https://app.warp.dev/graphql/v2?op=GetRequestLimitInfo- Query:
GetRequestLimitInfo - Fields:
isUnlimited,nextRefreshTime,requestLimit,requestsUsedSinceLastRefresh
Usage Mapping
- Credits:
requestsUsedSinceLastRefresh/requestLimit - Reset:
nextRefreshTime - Unlimited plans: Shows “Unlimited” with full bar
Troubleshooting
Missing Warp API key
Missing Warp API key
Add a key in Settings → Providers → Warp, or set
WARP_API_KEY.Warp API error
Warp API error
Verify the token is valid and that your network can reach
app.warp.dev.Reference
Ollama
Browser cookie-based provider for Ollama Cloud Usage tracking.Features
- Plan tier detection (Free/Pro/Max)
- Session usage window
- Weekly usage window
- Automatic reset time tracking
Authentication
- Automatic
- Log in to ollama.com/settings in Chrome
- Enable Ollama in Settings → Providers
- Leave Cookie source on Auto (imports Chrome cookies by default)
How It Works
- Scrapes
https://ollama.com/settingsusing browser cookies - Parses:
- Plan badge from Cloud Usage header
- Session and weekly usage percentages
- Reset timestamps from
data-timeattributes
Usage Mapping
- Session: Percentage from session usage bar
- Weekly: Percentage from weekly usage bar
- Resets: ISO timestamps from
data-timeattributes
Troubleshooting
No Ollama session cookie found
No Ollama session cookie found
Ollama session cookie expired
Ollama session cookie expired
MiniMax
API token or browser cookie-based provider with coding plan tracking.Features
- Coding plan usage (available vs. total)
- Multiple authentication methods with fallback
- Region selection (Global or China mainland)
- Browser local storage token extraction
Authentication
- API Token (Recommended)
- Environment Variable
- Get your API token from MiniMax platform
- Settings → Providers → MiniMax
- Enter API token
- Select region (Global or China)
API Endpoints
- API token:
GET https://api.minimax.io/v1/coding_plan/remains- Requires
Authorization: Bearer <api_token>
- Requires
- Global web:
https://platform.minimax.io - China web:
https://platform.minimaxi.com - Coding plan page:
{host}/user-center/payment/coding-plan - Remains API:
GET {host}/v1/api/openplatform/coding_plan/remains
Fallback Order
- API token (if provided)
- Cached cookie header (Keychain)
- Browser cookie import (Safari → Chrome → Firefox)
- Browser local storage access token (Chromium)
- Manual cookie header override
Environment Overrides
MINIMAX_HOST- Set toplatform.minimaxi.comfor ChinaMINIMAX_CODING_PLAN_URL- Full URL override for coding plan pageMINIMAX_REMAINS_URL- Full URL override for remains APIMINIMAX_COOKIEorMINIMAX_COOKIE_HEADER- Manual cookie
Usage Mapping
- Primary: Percent used from
model_remains(used/total) - Window: Derived from
start_time/end_time - Reset: From
remains_timeorend_time
Notes
- Cookies alone often fail (status 1004); remains API expects Bearer token
- MiniMax stores
access_tokenin Chromium local storage (LevelDB) - JWT tokens are automatically extracted when using browser auth
Next Steps
Configure Multiple Providers
Enable and manage multiple providers simultaneously
Author a New Provider
Learn how to add support for a new provider
