Codex weekly usage dropped from ~70% to ~7% at 5-hour reset boundary

Summary

Codex weekly usage remaining suddenly dropped from about 70% to about 7% around the 5-hour usage reset boundary.

This appears to be a usage accounting or dashboard reconciliation bug, possibly involving cached input, repeated/background goal continuation, or reset-boundary quota recomputation.

Observed

• Before the 5-hour reset boundary: weekly usage remaining was about 70%.
• After the 5-hour reset boundary: weekly usage remaining showed about 7%.
• No intentional manual workload equivalent to that drop was performed at that moment.

Approximate time:

• 2026-05-18 around 05:00 JST

Surface:

• Codex desktop app
• Codex usage dashboard

Local evidence

Codex.app local storage contains usage/quota-related keys:

• quotaBytesUsed
• week
• remaining_threshold_percent
• free_go_usage_set
• plan_up

Codex local logs around the same time show very large token usage events, mostly cached input:

• 2026-05-18 04:59:04 JST
• total_tokens=4,035,352
• input_tokens=4,024,782
• cached_input_tokens=3,993,728
• non_cached_input_tokens=31,054
• output_tokens=10,570

• 2026-05-18 05:03:20 JST
• total_tokens=4,035,352
• input_tokens=4,024,782
• cached_input_tokens=3,993,728
• non_cached_input_tokens=31,054
• output_tokens=10,570

There was also a repeated goal_context continuation loop shortly before this, which may have caused background or repeated accounting.

Expected behavior

• A 5-hour usage reset should not reduce the weekly remaining quota.
• Cached input should not be double-counted or over-counted against weekly usage.
• Background or automatic continuation turns should not unexpectedly drain weekly usage.
• The dashboard should distinguish actual usage from display/reconciliation errors.

Actual behavior

Weekly usage remaining dropped abruptly from about 70% to about 7% at or near the 5-hour reset boundary.

Related issues

Possibly related:

• #19536
• #19918
• #15039
• #16889
• #14593
• #21141

Request

Please investigate whether Codex weekly usage accounting is double-counting cached input, background/automatic goal continuation turns, or reset-boundary reconciliation events.