Skip to content

fix(usage): drop stale cached windows that have already reset - #736

Merged
sirmalloc merged 4 commits into
sirmalloc:mainfrom
effectustasi:fix/stale-usage-after-reset
Oct 29, 2026
Merged

sirmalloc merged 4 commits into
sirmalloc:mainfrom
effectustasi:fix/stale-usage-after-reset

Conversation

@effectustasi

Copy link
Copy Markdown
Contributor

When the usage API fails (429, timeout, network), ccstatusline falls back to the last cached response however old it is%2

When the usage API fails (429, timeout, network), ccstatusline falls back
to the last cached response however old it is, including windows whose
reset time has passed. After a night away, a 429 on the first fetch kept
"Session: 95%" on screen next to a 0m reset timer, for as long as the
Retry-After backoff lasted, although that window had reset hours ago.

A stale window whose resets_at has passed is now left out, as Claude Code
does in rate_limits, so the widget reports the fetch error (or falls back
to transcript blocks for the reset timer) instead of the old usage.
…-reset

# Conflicts:
#	src/utils/__tests__/usage-fetch.test.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants