Remaining usage comes first
A slim rail keeps the useful percentage visible. Hover for reset timing, or click to pin the detail card.
Usage Overlay keeps your remaining Codex allowance and reset time beside the desktop app, without modifying Codex, reading conversations, or owning your authentication.
Preview project · Windows 10/11 x64 · MIT licence · Executable currently unsigned

Designed for focus
The interface stays quiet until you need the reset time, connection status, or a closer look at the current limit.
A slim rail keeps the useful percentage visible. Hover for reset timing, or click to pin the detail card.
The rail shows a neutral “--” instead of presenting an old percentage as current after a failed connection.
Choose either edge, nudge the rail, drag it anywhere, follow Codex across monitors, or pause it for 15 minutes.
Use a fixed theme or let the overlay infer the active Codex surface without saving or logging screen content.
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.
Read App Server documentationUsage Overlay launches codex app-server --stdio as a child process.
It requests account/rateLimits/read through newline-delimited JSON-RPC.
account/rateLimits/updated keeps the rail current, with polling as a fallback.
The native non-activating window updates without taking keyboard focus from Codex.

Native settings
General, Visibility, Position, Appearance, and Connection controls live in one native window. Save and Cancel are explicit, theme choices preview safely, and validation keeps impossible thresholds or paths from being written.
Open-source preview
The repository includes the architecture, privacy policy, security guidance, 11 dependency-free specifications, CI, CodeQL, build scripts, release validation, and the MIT licence.
No completed GitHub Release or signed installer is claimed yet. The current executable is unsigned, so this page points to the source and documentation rather than presenting a download as ready.
Go deeper
The case study covers the product tradeoffs, App Server connection, privacy boundary, testing, and open-source preparation.