codex-usage v2.3.7
codex-usage v2.3.7
v2.3.7 recognizes newer Codex per-turn token counter restarts and stops showing resolved historical warnings as active red alerts.
- Treats a restarted
total_token_usagethat exactly matcheslast_token_usageas a complete, exact increment. These normal new-turn boundaries no longer creategap_fallbackevents or data-quality warnings. - Keeps a distinct actionable warning when a cumulative boundary cannot be fully verified and only a conservative
last_token_usagefallback is possible. - Excludes legacy
cumulative_resethistory from the active warning count without deleting its audit rows. - Automatically removes stale file-rewrite or truncation warnings after a later scan successfully reconciles the same JSONL path.
- Preserves all existing Token totals and source JSONL files. No automatic historical rebuild is performed or required for this update.
v2.3.7 识别新版 Codex 按 Turn 重置 Token 累计值的行为,并停止把已经恢复的历史记录持续显示为红色告警。
- 当重置后的
total_token_usage与last_token_usage完全一致时,将其作为完整、精确的本次增量处理;正常的新 Turn 边界不再产生gap_fallback或数据质量告警。 - 如果累计边界确实无法完整核对、只能使用
last_token_usage保守补位,仍会生成单独的可处理告警。 - 旧版
cumulative_reset记录继续保留在本机数据库中作为审计历史,但不再计入当前红色告警数量。 - JSONL 文件改写或截断问题经后续扫描确认恢复后,对应的过时告警会自动清除。
- 保留现有全部 Token 统计和源 JSONL;本次更新不会自动执行,也不要求执行历史重建。