fix(cli): mark depleted Codex quota critical - #34828
Conversation
|
Thanks for splitting the account-limit badge out of the earlier mixed-scope work. Current No correctness defect was identified in the submitted badge/cache logic by static review. Current Automated hermes-sweeper review. |
1c37f22 to
8d3b9ee
Compare
|
Resynchronized this contribution onto current The status-bar implementation was rebuilt against the current layout rather than mechanically rebasing the old patch, preserving the newer idle indicator, background-subagent status, resize recovery, width/overflow behavior, elapsed time, and YOLO state. The Codex account badge remains asynchronous and cached; a depleted session or weekly quota remains visibly critical, including the overflow path. Unsupported/non-Codex providers clear a prior Codex badge instead of leaking stale state. Validation run locally:
No deployment or active-instance change was performed. |
|
Updated the Codex quota handling to classify windows by A duration in the 6–8 day range is now treated as weekly. The status badge renders only a verified weekly window as used usage (for example Usage-pressure styles are tested at 80%, 90%, and 95%, including fractional values before display rounding. Unknown-duration windows remain generic and are never mislabeled as weekly. Validation: 87 focused CLI/account-usage/status-bar tests passed locally; ruff, Python compilation, and diff checks passed. |
Display consumed percentage (W42%) instead of remaining (W58%). Add 10-char Unicode usage gauge. Color thresholds use raw consumed percentage. Clean stale __pycache__ on deploy.
Summary
S0%orW0%).Test Plan
/usr/local/lib/hermes-agent/venv/bin/python3 -m pytest tests/hermes_cli/test_account_limits_status_bar.py tests/cli/test_cli_status_bar.py -qPrivacy / scope
This PR intentionally contains only the generic Hermes CLI quota/status-bar changes. Private Ops Center/outbox/dashboard work is excluded.