CodexBar for Android

Android port of CodexBar by @steipete — the macOS menu bar app for monitoring AI service quotas.

Monitor AI service quotas from your Android device. Track Claude, Codex (ChatGPT), GitHub Copilot, Gemini, Cursor, z.ai, ZenMux, Kimi Code, ElevenLabs, OpenRouter, Synthetic, Chutes, DeepSeek, Venice, Moonshot API, Cline, IBM Bob, Fireworks AI, Devin, and Antigravity usage in one place. Optional private companions keep Claude and Gemini authentication inside their official CLIs and add local Codex context/token telemetry without exporting session content.

_{Demo quota data is shown in screenshots. No account credentials are included.}

Latest release — v0.16.4

v0.16.4 improves tablet, landscape and resizable-window layouts. Headers stay full width on every page; Usage chooses readable overview/detail panes using width, height and font scale; Connections and Settings use adaptive columns. Continuous pages, provider ordering, optional haptics, saved connections and existing companions remain available. Version code 49 keeps the production signer and saved data. Release notes and verification · Adaptive layout

Recovery from v0.16.1/v0.16.2: those optimized APKs cannot start their own updater. Download CodexBar-Android-v0.16.4.apk with the GitHub app and install over the existing app once; do not uninstall. The WorkManager constructor fix from v0.16.3 remains enforced by release checks. Shared PC history, spend and remote settings require Windows v0.71.0 or later. In-app updates

Liquid Glass

Liquid Glass supports long-press-and-slide tabs and switches, native glass sliders, daily Unsplash photography, and consistent settings, connection and analytics controls. The default six-photo rotation needs no key; optional personal Editorial keys are encrypted on the device. Photography and privacy · Input verification

History and Spend share a Trends tab. The GitHub tab shows profile activity, a contribution calendar and repository shortcuts; available private data depends on the account and granted permissions. Release notes

_{Android API 36 emulator captures of the real Compose screens with synthetic data; these are not physical-device acceptance results.}

GitHub profile widgets

Add profile widgets from GitHub → Edit → +. Group favorite repositories in a two-column Pinned widget; legacy individual pins migrate automatically. Public badges and authored tech stacks use public profile data without sending account tokens. Annual statistics and the animated calendar cover the last 365 days, while the commit-period cards keep their calendar-period meaning.

Windows usage sharing

Download Win-CodexBar + Mobile Connect EXE directly. Enable Settings → Mobile Connect in the updated app (published v0.70.6 and older: Advanced → Android sharing), select LAN or Tailscale, and paste its private code into Android Connections → Usage source & Windows connection. Windows must remain running. The Windows EXE is unsigned; the Android APK retains its production signature. Setup guide

Choose Collect on this phone to use saved phone connections, or Collect on Windows to receive PC-collected data. Advanced phone exceptions allow individual services to stay on the phone. Pairing, credentials, exceptions and source/account-specific histories survive mode round trips. Legacy selections migrate to exceptions; Use Windows for all services clears them explicitly. Offline Windows never silently switches to a different phone account, and newly enabled known PC providers sync at refresh.

For use away from home, connect both devices to the same Tailscale network and select the PC's 100.x.x.x address. The phone's exit node can remain None. Tailscale access rules and Windows Firewall must allow TCP 43825; the app does not change those settings. Tailscale device connection guide

Provider details also show Local usage on this PC: today/30-day/selected-period tokens and estimated USD costs when Windows has a completed local-log scan. These may include multiple accounts; they are separate from the current quota account and billed charges. Unknown values remain unknown, and aggregation time is displayed. Gemini CLI and Gemini Apps now have separate entries. Gemini Apps current/weekly usage and reset times are collected on Windows and displayed on Android v0.9.8 or later.

Features

v0.10.0 adds drag ordering, PC-backed History / Spend, tablet layouts, reset notification setup and opt-in PC controls. Gemini Apps and Gemini CLI remain separate; phone/Windows modes and Tailscale without an exit node are retained. See the release notes.

Unified quota monitoring for 21 providers: Claude, Codex, GitHub Copilot, Gemini CLI, Gemini Apps (Windows), Cursor, z.ai, ZenMux, Kimi Code, ElevenLabs, OpenRouter, Synthetic, Chutes, DeepSeek, Venice, Moonshot API, Cline, IBM Bob, Fireworks AI, Devin, and Antigravity
Liquid Glass interface in light and dark appearance with a floating navigation bar
A compact Usage overview with official provider icons, a saved custom provider order, two quota windows per provider, symmetric cards, and details on tap
Provider cards with animated rings, bars, exact values, reset countdowns, pace forecasts, and retained history charts
Codex reset-credit inventory, provider-reported model quota windows, and exact expiry details
Optional privacy-preserving Codex companion for current context usage and input, cached-input, output, reasoning, daily, and per-model token totals
Adaptive phone navigation and a two-pane large-screen dashboard
Quick Settings tile for at-a-glance status
Twelve widget layouts with a live 347 × 69dp preview, background RGB and opacity, light/dark text, per-provider colors, provider order, corner radius, and text size
Configurable background refresh plus explicit refresh actions that supersede stale queued work
Built-in stable-release update prompt with a direct link to this fork's signed APK
Independently configurable persistent notification and time-bounded API 36 promoted Live Update, both synchronized with every dashboard refresh
Live progress, remaining quota, reset, pace, Refresh, and Stop on eligible Android 16 / One UI Now Bar surfaces, with a compatible ongoing notification elsewhere
Now Bar entries that name the provider and its remaining quota, summarize the other monitored providers when expanded, and open that provider's detail when tapped
Secure device-code account connection for Codex and GitHub Copilot, plus an encrypted local Claude Code companion that never exports Anthropic credentials
Claude companion pairing from one QR scan or a pasted code, and automatic reconnection when the companion's computer receives a new local address
Independent reset alerts for quota-window renewals, increases in available Codex resets, and resets expiring within 24 hours
On-device reset history with detected times, balance changes, expiry reminders, and a clear-history action
DataStore + Android Keystore-backed credential storage
English and Japanese per-app language selection
Light/dark appearance and responsive widget layouts

Reset alerts and widget editing

In Settings → Notifications, reset alerts can be enabled independently of the persistent notification. Both dashboard refreshes and background updates detect changes; Android notification permission is required. Alerts follow successful refreshes, so the refresh interval, network failures, and Android battery restrictions can delay them.

Open a provider's detail to see its reset history, retained for up to 90 days and 100 events per provider. The first successful response establishes a baseline. Later responses record quota-window renewals and net changes in Codex reset balances. A decrease can mean use or expiry; this is an observed activity log, not the provider's complete redemption history. Changes between refreshes can be missed. Clearing the log keeps the detection baseline, while disconnecting or replacing an account clears its history. The log is excluded from Android backups.

Existing widgets keep disconnected providers available in their editor so they can be deselected without reconnecting. An existing widget can also be saved with no providers; reopening it preserves that empty selection.

Codex insights

_{All release screenshots were captured from the debug-only deterministic harness on an Android 16 emulator. They contain demo data, not account credentials.}

Live monitoring and large screens

Download

Signed APKs are available on this fork's Releases page.

Install the release APK

Download the signed CodexBar-Android-v<version>.apk from the latest release assets (older releases use app-release.apk). Do not install a source archive or a debug APK from an untrusted location.

For an integrity check, download SHA256SUMS from the same Release and compare the APK hash on your computer:

# Windows PowerShell
(Get-FileHash ".\CodexBar-Android-v<version>.apk" -Algorithm SHA256).Hash

# macOS or Linux
sha256sum "CodexBar-Android-v<version>.apk"

Transfer the APK to the Android device if it was downloaded elsewhere, then open it from the browser or file manager.
If Android blocks the installer, allow Install unknown apps only for the browser or file manager currently opening the APK. The exact Settings path varies by device manufacturer.
Choose Install. For an update, install over the existing app so encrypted settings and provider connections remain in place.
After installation, turn off the temporary Install unknown apps permission again.

If Android reports a signature conflict, first confirm that both APKs came from this repository's Releases. Uninstalling the existing app is a last resort because it deletes locally encrypted credentials, settings, and cached usage data.

No hosted CodexBar backend is used. Provider tokens stay on-device. The optional Claude, Gemini, and Codex companions are local-network processes on your own computer: the Claude and Gemini companions drive only the official CLI views and never read or serve provider tokens, while the Codex companion serves only bounded aggregate token/model metadata and never prompts, responses, file paths, working directories, session IDs, or account tokens.

Security & Backup

Provider credentials are stored in codexbar_secure_prefs, an on-device DataStore whose values are encrypted with Android Keystore-backed AES-GCM keys. That DataStore is explicitly excluded from Android cloud backup and device-to-device transfer. After restoring or moving to a new device, providers must be linked again instead of reusing undecryptable credential ciphertext from the old device.

Architecture & Verification

Setup

For normal use, install the signed APK from the latest release and open Connections to link providers or enter fallback credentials.

For local development:

Install OpenJDK 17 (or any JDK 17+)
Clone and open the project in Android Studio
Build and install the debug APK
Open the app and go to Connections to link providers or enter fallback credentials

Connecting Accounts

Device-code sign-in: exact flow

Codex and GitHub Copilot use a device-code flow. The app intentionally shows the code before opening a browser so it can be copied safely:

Open Connections, expand the provider, and tap Connect account.
Wait for the one-time code card. The browser does not open automatically.
Tap Copy paste-ready code. The copied value removes spaces and separators so the entire code can be pasted into the first field, including pages that display split code boxes.
Tap Open sign-in page and verify the browser address before entering the code.
Paste the complete code, sign in to the intended account, and approve the connection.
When the website reports success, return to the same Connections screen before the displayed expiry time. Do not force-close the app.
Wait for the app to validate the returned credential and show the connected state. Browser success alone does not mean the on-device validation and encrypted save have finished.
If the code expires or the app reports a failure, tap Connect account again and use the newly issued code. Do not reuse an old code.

Provider	Expected sign-in host	Before starting
Codex	`auth.openai.com`	Use the ChatGPT account whose Codex usage you want to monitor.
GitHub Copilot	`github.com`	Use the GitHub account whose Copilot usage you want to monitor.

Treat a sign-in code as a short-lived credential. Enter it only on the page opened by the app, and never include codes or tokens in screenshots, logs, notes, or GitHub issues. The app never asks for the provider password; password and multi-factor authentication remain in the provider's browser page.

Troubleshooting:

No code card appears: confirm the app is current, retry on a working network, and record only the app version and non-secret error text. Never attach the response body if it contains a device code.
The website says complete but the app is still waiting: return to the app, keep the network connected, and allow several seconds for polling and credential validation. If the displayed expiry passes, request a new code.
A DNS error appears: check Private DNS, VPN, ad blockers, and network access. Codex and GitHub Copilot sign-in retry transient DNS failures until the current code expires.
Sign-in succeeds but quota validation fails: confirm that the selected account has access to the provider product and usage data being monitored.

Claude (Anthropic)

Claude does not expose a supported third-party Android device-code flow for this plan-usage use case. The recommended connection therefore keeps sign-in inside the official Claude Code CLI:

Install Claude Code using Anthropic's current setup instructions, complete browser sign-in, then finish the first-run and folder-trust prompts from ~/.codexbar/claude-workspace as described in the companion setup guide.
Enter /usage and confirm that Current session appears.
Download CodexBar-Claude-Companion-v0.16.4.zip from the same Release as the APK and extract it.
On Windows, run start-windows.cmd. On macOS or Linux, run chmod +x start-macos-linux.sh once and then ./start-macos-linux.sh.
Keep the phone and computer on the same trusted Wi-Fi, or use the Tailscale setup for different networks. If the computer firewall prompts, permit Node.js on private networks only. In Claude under Connections, tap Scan QR securely in CodexBar and scan the displayed QR inside the app. Do not use the system camera. If Google Play services cannot open the scanner, paste the CBCLAUDE1... pairing code, then tap Pair & verify Claude companion.

The companion keeps one tools-disabled Claude Code terminal alive, requests /usage without creating a new session every refresh, waits for loading to finish and the complete view to stabilize, then discards the raw rendering. It encrypts only validated quota labels, percentages, reset times, a known plan label, and freshness for Android. Anthropic access/refresh tokens, setup tokens, prompts, responses, files, email addresses, and session text never leave the computer.

Do not paste the result of claude setup-token. Anthropic documents setup-token for long-lived inference automation; it carries inference scope and cannot provide the plan-usage view required here. Direct Claude token entry and refresh are disabled. An upgrade securely removes legacy Claude access/refresh records and asks you to pair the companion instead.

Codex (OpenAI / ChatGPT)

Follow the device-code steps above. The app opens https://auth.openai.com/codex/device only after you press Open sign-in page, polls for completion, and saves the returned tokens only after validation.

Manual fallback, if needed:

# Access token
cat ~/.codex/auth.json | python3 -c "import sys,json; print(json.loads(sys.stdin.read())['tokens']['access_token'])"

# Refresh token
cat ~/.codex/auth.json | python3 -c "import sys,json; print(json.loads(sys.stdin.read())['tokens']['refresh_token'])"

Do not extract bearer tokens from browser DevTools unless you are debugging locally and understand the exposure risk.

Optional private Codex telemetry companion

OpenAI's subscription quota response does not contain local Codex CLI context-window or token-count history. To add those insights without uploading session content, install CodexBar-Codex-Telemetry-Companion-v0.16.4.zip from the same GitHub Release as the app:

Install Node.js 20 or newer on the computer where Codex CLI or Codex desktop stores ~/.codex/sessions.
Extract the companion archive. On Windows, run start-windows.cmd; on macOS or Linux, run ./start-macos-linux.sh.
Keep the phone and computer on the same trusted Wi-Fi, scan the displayed QR code, and review the hidden pairing value in the Codex card under Connections.
Tap Pair & verify telemetry companion. Keep the companion running whenever local telemetry should refresh.

The scanner is bounded to recent session files and reads only token_count plus model metadata. Android receives current context usage, aggregate token categories, daily totals, and model totals. Requests use HMAC-SHA256 authentication with replay and rate-limit defenses; snapshots use AES-256-GCM; the server accepts only a numeric private address. Never expose its port through router forwarding, a public IP, or a public tunnel. Codex subscription quota, reset credits, and model-limit windows continue to come directly from OpenAI even when this companion is off.

Antigravity

Download CodexBar-Antigravity-Companion-v0.16.4.zip from the same Release as the APK. The Windows Antigravity companion reads model quotas and reset times from the running, signed-in Antigravity IDE. In Connections → Antigravity, scan its private QR with the in-app scanner. This account usage is separate from Gemini CLI and Claude subscriptions.

Keep Antigravity open and the PC awake. The optional tray resident starts at sign-in and recovers after a crash. For different networks, connect the phone and PC to Tailscale and pair using the PC's 100.x address on port 43824. Google credentials, conversations and files stay on the PC. Only explicitly reported model quotas are shown; weekly limits and credit balances are not inferred. These internal IDE endpoints may change after an Antigravity update.

The source checkout also includes a Windows Control Center that combines Claude, Antigravity, Gemini CLI, and Codex telemetry into one tray dashboard with per-provider pairing QR codes. It retains existing Claude and Antigravity phone pairings and reads Antigravity 2.0 weekly/five-hour model-group windows. Follow its setup guide to install it from the source checkout.

Gemini Apps

Use Win-CodexBar + Mobile Connect v0.70.6 or later for the separate usage limits shown in the Google Gemini Windows/web app. This version fixes Gemini's connection transport error and retains encrypted session renewals. If an older connection already expired, reconnect once after updating Windows.

Sign in to the official Google Gemini Windows app with your primary Google account, then close it once.
In Win-CodexBar, open Settings → Providers → Gemini Apps, enable it and connect using the desktop app.
After successful connection, reopen Gemini. Its login session is encrypted for your Windows user and remains on the PC.
On Android, pair Windows in Connections → Acquisition and choose Windows mode. Current (5-hour), weekly usage and reset times appear in the separate Gemini Apps card.

Your phone and tablet can use the same Windows pairing code at the same time. With both in the same Tailscale network, select the PC's Tailscale address; an exit node is unnecessary. Revoking Windows pairing invalidates that shared code on all devices.

Gemini Apps has no phone-only collector. Multiple Google-account selection, token counts, per-model quotas and verified account-dependent history are not provided by this integration. Reconnect after the Google session expires. The first-party quota RPC is undocumented and may change. Windows connection guide

Gemini (Google)

Gemini Apps and Gemini CLI have separate usage limits. The existing companion monitors Gemini CLI; it does not report the usage shown in Google's Windows or web app. Android connection settings and provider details identify that source explicitly. The connection card also opens Gemini Apps, where Settings → Usage Limits shows the app's usage as described in Google's official help.

Gemini Apps usage is now available through the Windows app described above. The Gemini CLI companion remains a separate collector and never substitutes its quota for Gemini Apps.

Direct Gemini OAuth inside the Android app remains disabled. CodexBar does not copy Gemini CLI credentials, embed a Google client secret, or call the internal cloudcode-pa service. Instead, the v0.12.1 companion drives the official Gemini CLI's /model view and sends only a sanitized quota snapshot over your trusted local network. Gemini CLI 0.61.0 or newer is required.

Install and pair the private companion

Install Node.js 20 or newer and the current official Gemini CLI on a computer:

npm install -g @google/gemini-cli@latest
gemini

Launch the official CLI from ~/.codexbar/gemini-workspace, complete Google's sign-in and folder-trust prompts, verify /model shows usage limits, then exit it. Create that workspace first if needed.
Download CodexBar-Gemini-Companion-v0.16.4.zip from this repository's Release and extract it. Do not run a companion archive from another source.
On Windows, double-click start-windows.cmd. On macOS or Linux, run ./start-macos-linux.sh. The first launch installs only the versions pinned in package-lock.json.
Keep the phone and computer on the same trusted Wi-Fi. If the computer firewall prompts, permit private networks only.
Scan the displayed QR code with the phone and choose CodexBar, or paste the complete codexbar://gemini-pair?... value into the Gemini card.
Review the screen, then tap Pair & verify companion. Scanning or pasting never connects or saves the key automatically.
Keep the companion running while Gemini monitoring is needed. If the computer's local IP address changes, start it again and replace the pairing.

The pairing key is a local-device password: do not post it in screenshots, logs, or issues. Requests are authenticated with HMAC-SHA256, replay-protected, rate-limited, and responses are encrypted with AES-256-GCM. Android accepts only numeric local/private addresses and encrypts the pairing details with Android Keystore. The snapshot contains model labels, used percentages, reset times, tier, CLI version label, and freshness—never Google access/refresh tokens, client secrets, prompts, files, email addresses, or CLI session content.

Troubleshooting:

Pairing verification fails: confirm the companion still says it is ready, both devices use the same Wi-Fi, private-network firewall access is allowed, and both clocks use automatic time.
The companion cannot collect quota: open the official gemini command in its dedicated workspace, finish sign-in or any first-run prompts, verify /model shows model usage, exit, and restart the companion. Background collection stays paused while setup is required.
Android stops refreshing Gemini: the computer may be asleep, its IP may have changed, or the Wi-Fi may isolate clients. Restart and re-pair; do not expose the port through router forwarding or a public tunnel.

This design follows the official Gemini CLI's documented usage and quota command without using its OAuth credential to access Google's backend from a third-party client. Direct Android OAuth remains fail-closed because Google's limited-input device flow is not a general Android authorization mechanism and does not make Gemini CLI's internal quota service a supported API.

GitHub Copilot

Follow the device-code steps above. The app opens https://github.com/login/device only after you press Open sign-in page, then fetches Copilot quota data after GitHub authorization and on-device credential validation complete.

Cursor

Cursor does not currently expose a supported mobile device-code flow. The original macOS CodexBar reads a signed-in desktop browser session or Cursor.app state; Android cannot safely access either store. This port therefore starts with the original project's manual fallback: copy the Cookie request header from https://cursor.com/api/usage-summary in a signed-in desktop browser, paste it into the Cursor card, and select Validate & connect.

The app rejects malformed or multi-line values before network access, sends the cookie only to https://cursor.com, refuses HTTP and HTTPS redirects, and encrypts it with Android Keystore only after the usage endpoint accepts it. Never paste this value into an issue or chat. Signing out of Cursor invalidates the session.

Cursor cards show the billing-cycle Total, Auto, and API percentages, legacy request-plan usage when available, the cycle reset, plan name, and capped on-demand USD usage. Team and Enterprise personal/shared-cap fallbacks follow the original CodexBar mapping.

z.ai

Create or copy an API token from the z.ai Coding Plan dashboard, paste it into the z.ai card, and select Validate & connect. The app reads the personal quota response from the fixed Global endpoint at https://api.z.ai/api/monitor/usage/quota/limit and maps the Tokens, MCP/time, and shorter rolling token windows using the original CodexBar rules.

The token is sent only as a bearer credential to api.z.ai, never across redirects, never written to HTTP logs, and encrypted with Android Keystore after validation. BigModel China and team mode need additional region, organization, and project selectors; they intentionally remain unavailable rather than silently sending a Global token to a configurable host.

ZenMux

Create a Management API key at https://zenmux.ai/platform/management, then paste it into the ZenMux card in Connections and select Validate & connect. A normal ZenMux inference API key is not accepted by the management quota endpoints.

The app sends the key only as a bearer credential to https://zenmux.ai/api/v1/management/subscription/detail. It displays the rolling 5-hour and 7-day flow quotas from the documented response. The key is encrypted with Android Keystore after validation; prompts, inference requests, and request logs are never requested.

Kimi

Create a Kimi Code API key in the Kimi Code console, paste it into the Kimi card in Connections, and select Validate & connect. The app calls only https://api.kimi.com/coding/v1/usages and displays the short rolling window (normally 5 hours) together with the 7-day coding quota.

The API key is sent only as a bearer credential to the fixed HTTPS host, never follows redirects, never enters HTTP logs, and is encrypted with Android Keystore only after validation. The app does not request prompts, inference responses, or browser session cookies.

ElevenLabs

Create a restricted ElevenLabs API key with permission to read the user subscription, paste it into the ElevenLabs card, and select Validate & connect. The app calls https://api.elevenlabs.io/v1/user/subscription and displays character usage, voice slots, professional voice slots, the subscription tier, and the next character reset when provided.

Use the narrowest key permissions available. The key is sent only in the xi-api-key header to the fixed ElevenLabs HTTPS host, redirects and HTTP logging are disabled, and the key is encrypted with Android Keystore after validation. Generated audio, voices, projects, and request content are not fetched.

OpenRouter

Create a dedicated OpenRouter API key, preferably with a daily, weekly, or monthly credit limit, paste it into the OpenRouter card, and select Validate & connect. The app calls https://openrouter.ai/api/v1/key and maps the configured key limit, remaining credits, usage, reset cadence, and free-tier state. A management key is not required.

If no key limit is configured, the account remains connected and the dashboard/widget states that there is no spending cap while showing the reported spend. A configured limit adds an exact USD credit summary and a progress bar. The key is sent only as a bearer credential to the fixed OpenRouter HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation.

Synthetic

Create a dedicated Synthetic API key, paste it into the Synthetic card, and select Validate & connect. The app calls only https://api.synthetic.new/v2/quotas, maps subscription requests against the documented limit, and shows the renewal timestamp. Synthetic documents that quota checks do not consume subscription limits.

The key is sent only as a bearer credential to the fixed Synthetic HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation. Prompts, model responses, and request history are not fetched.

Chutes

Create a dedicated scoped Chutes API key, paste it into the Chutes card, and select Validate & connect. The app first calls https://api.chutes.ai/users/me/subscription_usage, whose official API description returns monthly and 4-hour usage versus caps, and falls back to the documented /users/me/quotas response when necessary.

The parser accepts the currently documented flexible quota payload without trusting arbitrary endpoints. The key is sent only as a bearer credential to the fixed Chutes HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation. Chute code, prompts, invocations, and request history are not fetched.

DeepSeek

Create a dedicated DeepSeek API key, paste it into the DeepSeek card, and select Validate & connect. The app calls only https://api.deepseek.com/user/balance and displays whether API calls are currently available together with each reported USD or CNY balance. DeepSeek does not expose a bounded quota in this endpoint, so the app intentionally shows an exact status instead of inventing a utilization bar.

The key is sent only as a bearer credential to the fixed DeepSeek HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation. Prompts, chat history, model responses, and usage records are not fetched.

Venice

Create a dedicated Venice API key with the narrowest permission that can read billing balance, paste it into the Venice card, and select Validate & connect. The app calls only https://api.venice.ai/api/v1/billing/balance, shows whether the account can make API calls, and displays USD/DIEM balances. When a DIEM epoch allocation is present, it also derives the consumed fraction for the progress bar from the documented remaining balance and allocation.

The key is sent only as a bearer credential to the fixed Venice HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation. Prompts, model responses, billing history, and inference request details are not fetched.

Moonshot API (International)

Create an API key on the international Moonshot API platform, paste it into the Moonshot API card, and select Validate & connect. This is deliberately separate from the Kimi Code card: Kimi Code subscription keys and Moonshot API billing keys use different account surfaces. The app calls only https://api.moonshot.ai/v1/users/me/balance and displays available, cash, and voucher balances without inventing a rolling quota bar.

The key is sent only as a bearer credential to the fixed international Moonshot HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation. The app does not automatically forward the key to the China-mainland host. Prompts, model responses, and request history are not fetched.

Cline

Create a dedicated API key in Cline, paste it into the Cline card, and select Validate & connect. The app calls only https://api.cline.bot/api/v1/users/me/plan/usage-limits and displays the provider-reported 5-hour, weekly, and monthly plan windows with their reset times.

The key is sent only as a bearer credential to the fixed Cline HTTPS host, redirects and HTTP logging are disabled, and it is encrypted with Android Keystore after validation. Prompts, model responses, and request history are not requested.

IBM Bob

Create an API key in the IBM Bob portal, paste it into the IBM Bob card, and select Validate & connect. The app reads the profile and aggregates the monthly Bobcoin usage and budget across visible teams, preserving the earliest reported refresh time.

API keys use IBM Bob's Apikey scheme, while structurally valid JWT credentials use Bearer. Regional endpoints returned by the profile are accepted only when they are HTTPS hosts strictly under bob.ibm.com; URL user info, ports, paths, queries, fragments, and lookalike domains are rejected. The encrypted credential is never logged, and prompts or coding history are not requested.

Devin

Create a cog_ personal access token or service-user key with ViewOrgConsumption, then enter it and the organization ID in Connections → Devin. Both are available through Devin Settings → Devin API. The app makes read-only requests to the official organization consumption endpoint, available across plans.

Devin shows organization ACUs consumed over the last 30 days, across Devin products. Daily boundaries use 08:00 UTC. This API does not expose a subscription limit or remaining credits, so CodexBar does not invent a percentage or reset countdown. A 403 indicates missing organization access or permission; 401 means the key needs replacing. No session creation, prompts, or inference requests are made.

Fireworks AI

Create a dedicated Fireworks API key and copy the account slug from the account URL. Enter both in the Fireworks AI card and select Validate & connect. The app calls only https://api.fireworks.ai/v1/accounts/{accountSlug}/billing/summary and totals rated spend for the last 30 days in the first reported currency.

The account slug is restricted to a short ASCII identifier, the API key is sent only as a bearer credential to the fixed Fireworks HTTPS host, redirects and HTTP logging are disabled, and both values are encrypted with Android Keystore after validation. Prompts, model responses, and inference history are not requested.

Build

./gradlew assembleDebug

APK output: app/build/outputs/apk/debug/app-debug.apk

Recommended local checks before opening a PR:

./gradlew --dependency-verification=strict testDebugUnitTest lint assembleDebug

Dependency Verification

Gradle Wrapper distribution checksums and dependency verification metadata are committed. When intentionally changing Gradle, plugins, or libraries, regenerate verification metadata with:

./gradlew --write-verification-metadata sha256 lint testDebugUnitTest assembleDebug

Review and commit gradle/verification-metadata.xml together with the dependency change. CI runs with --dependency-verification=strict and validates the Gradle Wrapper before compilation.

Release Builds

Public releases are built only from v* Git tags by the protected release workflow. Signing material must stay in GitHub environment secrets:

ANDROID_KEYSTORE_BASE64
ANDROID_KEYSTORE_PASSWORD
ANDROID_KEY_ALIAS
ANDROID_KEY_PASSWORD

The release workflow publishes signed APK/AAB artifacts, versioned Gemini and Codex companion ZIPs, Android and companion CycloneDX SBOMs, emulator screenshots, SHA256SUMS, a build provenance JSON file, and GitHub artifact attestations. Debug APKs from CI are short-lived test artifacts only.

Tech Stack

Kotlin 2.3.21, Jetpack Compose, Material 3 Expressive
Hilt (DI), Retrofit2 + OkHttp (networking)
WorkManager (background sync), DataStore + Android Keystore-backed encryption
Glance AppWidget, Quick Settings tile, Android notification/live monitoring APIs
Node.js companions for the official Gemini CLI and privacy-bounded Codex session telemetry, with authenticated encrypted local snapshots
KSP, kotlinx.serialization

Acknowledgments

Based on CodexBar by Peter Steinberger.

License

MIT

Name		Name	Last commit message	Last commit date
.github		.github
app		app
companion		companion
docs		docs
gradle		gradle
scripts		scripts
.gitattributes		.gitattributes
.gitignore		.gitignore
AGENTS.md		AGENTS.md
LICENSE		LICENSE
README.md		README.md
build.gradle.kts		build.gradle.kts
gradle.properties		gradle.properties
gradlew		gradlew
gradlew.bat		gradlew.bat
settings.gradle.kts		settings.gradle.kts

Latest commit

History

Folders and files

Repository files navigation