Repository navigation
fix(usage): drop stale cached windows that have already reset - #736
Merged
sirmalloc merged 4 commits intoOct 29, 2026
Merged
Conversation
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
This was referenced Oct 31, 2026
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the usage API fails (429, timeout, network), ccstatusline falls back to the last cached response however old it is%2