See reset deadlines, usage runway, and token activity at a glance.
A lightweight Windows monitor for turning live Codex status into a clear, timezone-aware view.
Windows 10/11 · Portable app · Local-first · Open to contributions
Codex Monitor is a compact Windows companion for checking when Codex usage windows reset and how much useful runway remains. It combines exact reset timestamps, live countdowns, quota and token values, model planning estimates, a real activity calendar, and a seven-day trend view in one calm interface.
The GitHub repository keeps its original codex-reset-watch address, while the application itself is now presented as Codex Monitor.
A quick, readable view of reset status, timezone, usage, and monitor health.
 |
 |
| Usage Quota runway, observed tokens, and model planning. |
Calendar Real dates and local token activity in one view. |
UI captures are included to show the layout and user flow. Runtime values can vary by account and date.
The current release opens as a readable 625 x 735 quick-check window. Its Chrome-inspired title bar keeps refresh, minimize, maximize/restore, close, and quick actions in one aligned control group. The blue status header puts the next reset, exact countdown context, timezone, and connection state first; the tab row then separates the five decisions a visitor usually needs:
- Overview for the next safe reset, health checks, refresh, copy, and JSON export.
- Usage for remaining quota, observed token values, model families, and effort-based runway estimates.
- Calendar for real date-based local token activity.
- Trend for seven-day token and quota-window history.
- Resets for searchable, sortable deadlines with local and UTC timestamps.
The layout remains responsive when the window is resized or maximized: only the selected tab is displayed, while the content grid uses the additional width without changing the meaning of the data.
- Live reset deadlines with exact timestamps and continuously updated countdowns.
- A timezone selector that starts from the active Windows timezone.
- A native Rust/Tauri desktop app with a readable 625 x 735 quick-check window.
- Overview, Usage, Calendar, Trend, and Resets tabs with purposeful controls.
- Token values beside percentages, so remaining usage is easier to plan around.
- Model runway estimates for GPT-5.6 Sol, Terra, and Luna across supported effort levels.
- A real date-based token calendar built from timestamped local session activity.
- A seven-day trend view for observed token activity and quota-window snapshots.
- A Monitor health panel that distinguishes fresh, refreshing, partial, stale, and unavailable data.
- A matching PNG snapshot written to the project output and the Windows Desktop.
- A full-length Resets PNG export containing every available reset, saved beside
CodexMonitor.exe. - A classic browser dashboard for users who prefer the HTML workflow.
- Local-only serving through
127.0.0.1; credentials are never placed in the page or URL.
- Open the Releases page.
- Download
CodexMonitor-win-x64.zipfrom the latest release. - Extract it to a normal user folder.
- Run
CodexMonitor.exe.
The app performs the complete workflow internally: it selects an available private localhost port, starts its hidden monitor bridge, refreshes the Desktop PNG, and connects the UI without a BAT launcher. It uses the active Windows timezone first, and the selector can be changed whenever another supported timezone is more useful. The footer includes the small project signature: “made with care @benedictusrey ❤️”.
In the Resets tab, Save full Resets PNG creates a long image with every live reset, exact local and UTC times, granted time, status, and countdown. The native app saves it beside CodexMonitor.exe with a CodexMonitor-resets-full-<timestamp>.png filename. The export is private account data and should remain local.
For the original dashboard workflow, run this file from the repository root:
outputs\open-codex-reset-dashboard.bat
The BAT is retained as a compatibility entry point. When outputs\CodexMonitor\CodexMonitor.exe is present, it opens that self-contained app and does not start a second PowerShell monitor. If the portable build is not present, it falls back to the browser workflow: it refreshes outputs\codex-reset-deadlines.png, copies the verified snapshot to %USERPROFILE%\Desktop\codex-reset-deadlines.png, and opens http://127.0.0.1:8765/. It never opens the PNG in a separate window.
- Windows 10 or Windows 11, 64-bit for the portable Rust app.
- Microsoft Edge WebView2 Runtime for the native desktop app.
- A signed-in local Codex installation.
- Network access when live data is refreshed.
The browser and PowerShell workflow does not require Python or an additional package installation.
The @benedictusrey footer link is opened by Windows in the default browser. WebView2 is still required for the native app itself because it renders the Codex Monitor interface; only the external profile-link action leaves the app window.
Codex Monitor reads the existing local credential at:
%USERPROFILE%\.codex\auth.json
That file belongs to the user and must never be uploaded, committed, pasted into an issue, or included in a screenshot. The repository intentionally excludes auth.json, environment files, private keys, logs, and generated live PNG snapshots. The UI captures above show the product layout; any runtime values visible in them are illustrative and should not be treated as a public account record.
Live reset deadlines and usage telemetry are private account information too. Keep the generated PNG files on the local computer and inspect the GitHub Desktop change list before every commit.
The service exposes usage windows primarily as percentages rather than one universal raw-token balance. Codex Monitor therefore shows observed token values and model runway as planning aids, not as billing statements or guaranteed quotas. Estimates use the local samples available to the monitor, the current model credit profile, effort multipliers, and reset-window observations when those observations exist.
The reset cards remain the authoritative part of the display for the service-provided deadline. A calendar or estimate never invents a reset time.
outputs/
codex-reset-deadlines.ps1 Live data reader and PNG generator
codex-reset-dashboard.html Responsive browser dashboard
icon.png Public titlebar icon for the standalone HTML
start-codex-reset-dashboard.ps1 Local loopback server and lifecycle monitor
open-codex-reset-dashboard.bat Unified Windows launcher
docs/assets/
codex-reset-watch-public-preview.png Synthetic README preview
codex-monitor-overview.png Overview tab product capture
codex-monitor-usage.png Usage tab product capture
codex-monitor-calendar.png Calendar tab product capture
portable-rust/
src/main.rs Native monitor lifecycle and dynamic port selection
ui/index.html Embedded responsive interface
icons/ HD Windows and Tauri icon assets; icon.png is canonical
build-portable-rust.ps1 Windows release build script
portable-app/ Optional legacy WebView2 shell source
GETTING_STARTED.md Visitor installation and usage guide
PUBLISHING.md GitHub Desktop publishing walkthrough
RELEASES.md Versioned download and release notes guide
SECURITY.md Credential and data-handling policy
CONTRIBUTING.md Contributor workflow and issue guidance
Start with GETTING_STARTED.md to understand the user workflow, then read CONTRIBUTING.md before changing the dashboard or the local data bridge. The public release process, including the GitHub Desktop screens and the release attachment checklist, is documented in PUBLISHING.md and RELEASES.md.
If you build the native app locally, the generated package is outputs\CodexMonitor and the release ZIP is outputs\CodexMonitor-win-x64.zip. These build products are intentionally ignored by Git; attach the ZIP to a GitHub Release instead of committing it to the source tree.
Codex Monitor is created and maintained by @benedictusrey. Contributions, documentation improvements, and reproducible bug reports are welcome.
This is a local monitoring and planning utility, not an official quota-management client. Service response fields and rate behavior may change, so keep the app updated and treat estimates as guidance rather than guarantees.