Codex
Claude
CursorKeep Codex, Claude and Cursor usage beside the app you are working in. Version 0.4.3 adds optional automatic Claude renewal, so an expired access token does not mean another browser login. Clear error messages and recovery actions remain in the card.
Version 0.4.3 · Windows 10/11 x64 · Installer + portable ZIP · MIT licence · Unsigned release
Focused on the main limit
The rail keeps the main Codex limit in view. The detail card adds returned primary and secondary windows, reset timing, and connection status.
Version 0.4.3 follows Codex, Claude and Cursor. Claude leads with its 5-hour limit when available, while weekly usage stays in the detail card. Cursor reads the editor’s current allowance and reset time, or team spend through the Admin API.
An amber attention marker and a clear reason explain missing data. Claude distinguishes expired sign-ins, connection failures, access denials and rate limits. Copy the sign-in command, open settings or retry from the card.
Upgrades migrate saved Claude and Cursor opt-ins, including their usage sources. Explicit current settings take precedence, and new installations keep both integrations off until enabled.
Enable automatic renewal once to keep Claude usage working after access-token expiry and app restarts. It renews the saved sign-in with Anthropic and updates it safely on your PC. This separate permission is off by default.
Usage Overlay deliberately selects the main Codex limit and keeps Spark or other model-specific buckets out of the interface.
The detail card shows primary and secondary windows as separate labelled rows when App Server provides both.
Signing out or switching Codex accounts clears the previous reading and refreshes usage for the active account.
Windows alerts can fire once when a returned limit crosses the configured amber or red threshold. They are off by default.
Check for updates makes one user-triggered request to the public GitHub release endpoint and never installs anything automatically.
Disconnect releases only the App Server child process started by Usage Overlay. The rail also stays hidden on Codex-owned file picker, Open, and Save dialogs.
Platform support
Version 0.4.3 supports Codex, Claude and Cursor on Windows x64. Claude and Cursor are optional and can be enabled in Settings.
A narrow connection
Codex CLI keeps account ownership and network access. Usage Overlay requests rate-limit metadata through the documented App Server surface and renders it in a separate WPF process.
After you sign into another account in Codex, the overlay reloads usage automatically, normally within about seven seconds plus the request time when the login is saved to disk. Credential-manager changes can take about a minute. An expired login still needs you to sign in again; fresh usage requires a working connection.
Read App Server documentationUsage Overlay launches codex app-server --stdio as a child process.
It checks saved login-file timestamps and size every two seconds. A change clears the previous account’s usage and reconnects the overlay automatically, without reading credential contents.
It requests account/rateLimits/read, exposes the main bucket’s primary and secondary windows, and hides model-specific buckets.
Routine polls no longer force token refreshes. Stalled requests reconnect after 30 seconds, and late replies cannot restore usage from a previous account.
Privacy by scope
The product boundary is narrow in code and visible in the public repository. Account ownership stays with Codex CLI; Usage Overlay keeps only local settings and redacted diagnostics.
Codex owns authentication and account-data network access. The Codex source checks login-file metadata without reading credential contents. Claude and Cursor sources are opt-in and send tokens only to their own provider. Claude automatic renewal is a separate opt-in: it exchanges the existing refresh token with Anthropic and updates the private credentials file. It preserves existing permissions, scopes and unrelated account fields. These unofficial sources may change. No source reads conversations.
Preferences and diagnostic logs remain under the current Windows user profile. Sensitive-looking values are redacted before diagnostic messages are written.
Installation reporting is optional and off by default: a random installation ID and app version are sent to Haroone at most once per UTC day while running. No account, conversation, quota or log data is sent. Daily activity expires after 90 days; summaries expire after 90 inactive days. Disable reporting in Settings to stop future reports. There is no analytics SDK or advertising.
Native settings
General, Visibility, Position, Appearance, and Connection & diagnostics controls stay together. Save and Cancel are explicit, theme choices preview safely, and validation keeps impossible thresholds or paths from being written.
Installation and trust
Download app opens the public 0.4.3 installer. A portable ZIP and SHA256SUMS file are available in the same GitHub Release for users who prefer a manual install or want to verify the package before launch.
The installer, portable ZIP, manifest, and checksum file are published on GitHub.
The installer adds a normal Installed apps entry and uninstaller.
Compare the download with the published SHA256SUMS value.
Version 0.4.3 adds separately opt-in Claude sign-in renewal and prompt detection of saved-sign-in changes. With renewal enabled, the rail recovers from access-token expiry without launching a terminal, browser or model request. Revoked or expired renewal credentials still need sign-in. Release validation includes the build, 33 core specifications, renewal and account-switch regressions, a real renewal, app-restart checks and package checksums.
The published SHA-256 values match GitHub’s asset digests for both downloads. The installer is unsigned, so Windows SmartScreen may warn on first launch.
Go deeper
The case study covers the product tradeoffs, App Server connection, privacy boundary, testing, and open-source preparation.