v0.2.0 Forum Post Draft
Use this draft only after v0.2.0 is tagged and the GitHub Release, PyPI
package, GHCR image, and documentation site have passed the release checklist.
Copyable Post
I released Codex Quota Monitor v0.2.0, a small self-hosted dashboard for people who run Codex OAuth accounts behind CLIProxyAPI.
It turns the pool’s 5h and weekly quota into Plus-equivalent remaining capacity, shows which accounts are still good candidates for routing, and explains missing quota, health, stats, and reset data without scraping the browser UI.
It is useful if you:
- run more than one Codex OAuth account behind CLIProxyAPI;
- want to see quota, resets, account health, and live usage from one page;
- want machine-readable
/api/v1/*endpoints, Prometheus metrics, or account recommendations for wrappers and agents; - prefer a self-hosted tool with loopback-first defaults instead of a hosted analytics service.
Two-minute UI preview:
uv tool install codex-quota-monitor==0.2.0
cqm --demo
Then open http://127.0.0.1:4516/. Demo mode uses built-in sample data and does not need CLIProxyAPI, a management key, or auth files.
Run it against an existing local CLIProxyAPI management endpoint:
cqm \
--management-base-url http://127.0.0.1:8317 \
--management-key-file /path/to/management-key \
--gateway-health-url http://127.0.0.1:8317/healthz \
--auth-dir /path/to/auth-files
Other install paths:
- Docker:
ghcr.io/xsyxnx/codex-quota-monitor:0.2.0 - Nix:
nix run github:xsyxnx/codex-quota-monitor/v0.2.0#codex-quota-monitor -- --help - NixOS module:
inputs.codexQuotaMonitor.nixosModules.default
Links:
- Project: https://github.com/xsyxnx/codex-quota-monitor
- Docs: https://xsyxnx.github.io/codex-quota-monitor/
- Quick Start: https://xsyxnx.github.io/codex-quota-monitor/quick-start.html
- Security self-audit: https://xsyxnx.github.io/codex-quota-monitor/security-audit.html
Security and scope notes:
- This project connects to an existing CLIProxyAPI deployment; it does not install, upgrade, or manage CLIProxyAPI.
- The default service listens on
127.0.0.1; use an authenticated reverse proxy before exposing it to a LAN or public tunnel. - It does not include built-in login, RBAC, hosted analytics, or account provisioning.
- Bug reports are most useful with the install method, version, deployment type,
and redacted
cqm doctoroutput.
Feedback: