AIUsageWatchCodex accounts,
with room to work.
See the main weekly Codex allowance for each configured login, with account colors and available reset information.
One bar for each configured Codex account
If you use Codex across personal and work logins, a single balance is only part of the picture. AIUsageWatch can display separate CODEX_HOME directories together, with distinct names, colors and letters. The filled portion of each bar shows the allowance remaining for that account. Reading several accounts does not automatically switch the login used by your coding tools.
How the reading works
The app asks the local Codex CLI app-server for the rate limits belonging to each configured directory’s saved login. It selects the main weekly limit, rather than a side model’s separate quota. If the app-server is unavailable, local session transcripts can provide a fallback. The source and reading status matter: a historical transcript is not the same as a fresh account response.
Install and sign in to the Codex CLI, then select the appropriate directory in AIUsageWatch Preferences. Use an independent CODEX_HOME for each additional login. The menu provides percentages and available reset times; the compact bars make it easier to compare accounts while working.
Don’t let a banked reset expire unnoticed
When Codex reports available banked resets and expiry dates, a warning dot can flag the account 1–14 days before expiry. The default warning window is two days. Open the menu for banked reset counts and expiry dates, then decide how to use the banked reset through your provider tools. The app does not use banked resets automatically; warnings depend on the app running and current expiry data being available.
Read the starter behavior first
A live weekly reading of 100% remaining can trigger one small Codex request to start a weekly window that would otherwise remain idle. It uses the saved login and default available model and consumes a small amount of allowance. A red dot shows a request in progress or a failure; the menu offers retry information. Attempts are remembered in memory, so relaunching can allow another request. Historical transcript fallback never sends starter requests. Read the complete behavior →
Weekly allowance is not a billing estimate
AIUsageWatch does not calculate token costs or an authoritative invoice, and the weekly percentage does not predict an exact number of requests left. Other provider restrictions can still apply. If your goal is historical token analysis, read the ccusage comparison; if you need broader reporting, read the CodexBar comparison.
Common questions
Does AIUsageWatch only read Codex usage?
It reads usage through the local CLI app-server or historical transcripts, and a live 100% weekly reading can trigger a small starter request. That request consumes allowance. The attempt is remembered in memory, and relaunch or manual retry can result in another request.
Is AIUsageWatch free and available for Mac?
AIUsageWatch is a free native macOS app requiring macOS 14 or later. Its public release is in preparation. Provider plans and charges still apply.
A clearer view of your AI allowance.
AIUsageWatch is free. Public release is in preparation.