Repository navigation
fix(usage): show a newer usage API percent in a session left idle - #767
Merged
Merged
Conversation
Claude Code sends the 5-hour and weekly percents with each of a session's API responses, and the usage widgets show those over the usage API's. A session left idle keeps the percents from its last response, so with `refreshInterval` its line redraws with the same numbers while other sessions or devices use up the limits. Once the transcript's last response is more than three minutes old (the usage cache's lifetime), the prefetch also asks the usage API for the windows the line shows, through the shared cache and without surfacing errors. Its percent wins when the API sent it after that response, for the same window and no lower, or for the next window once the payload's has reset. The forecast history dates the 5-hour percent by its source.
This was referenced Nov 6, 2026
Closed
This was referenced Nov 7, 2026
Closed
Closed
pcvelz
added a commit
to pcvelz/ccstatusline-usage
that referenced
this pull request
Nov 13, 2026
Upstream: Extra Usage Today widget (sirmalloc#811), newer usage API percent in an idle session (sirmalloc#767), thinking-effort brackets and per-level colors (sirmalloc#777), 256-color grid in Edit Colors (sirmalloc#778), context bar thin line mode (sirmalloc#794), progress-bar widget consolidation (sirmalloc#810), Zed IDE link mode (sirmalloc#800), Check for Updates deadline and proxy fixes (sirmalloc#806), Configure Status Line before an install (sirmalloc#807), emoji and grapheme fixes (sirmalloc#808, sirmalloc#803, sirmalloc#790), Nerd Font icon width in Ghostty and kitty (sirmalloc#801), cache temp file leak fix (sirmalloc#783), plus TUI, timer and separator fixes. Hand edits outside conflicts: - src/tui/components/__tests__/InstallMenu.test.tsx: fork-rename (ccstatusline@ -> ccstatusline-usage@) - src/utils/__tests__/hooks.test.ts: fork-rename (ccstatusline@ -> ccstatusline-usage@) - src/tui/__tests__/App.test.ts: fork-rename; upstream's new menu and preview tests step over the fork's Off Hours row and pin cyan where the fork's Model default is ansi256:124 - src/tui/components/__tests__/ColorMenuPalette.test.tsx: fork deviation - Model default is ansi256:124 - src/utils/__tests__/global-package-manager.test.ts: fork deviation - fixture path uses the fork package name ccstatusline-usage - src/utils/__tests__/migrations.test.ts: fork deviation - flexMode is a post-v1 key in the fork, the v1 sample uses globalBold - src/utils/__tests__/usage-prefetch.test.ts: fork deviation - stub the provider gate (resolveProvider) in upstream's idle-session and daily-spend tests; the fork reads weekly usage from the API only - src/utils/__tests__/update-checker.test.ts: lint import order - src/utils/usage-prefetch.ts: lint - drop the unused fetchUsageData import - src/widgets/WeeklyFableUsage.ts: compat fix - render through upstream's formatUsageBar (sirmalloc#810) so the line mode works; the inverted cursor follows the shared percent-widget rule - src/widgets/__tests__/line-bar.test.ts: compat fix - fork WeeklyFableUsageWidget, weeklyFableUsage field and Fable label; block metrics stubbed so the inactive-block case does not read the real cache - src/widgets/shared/__tests__/usage-display.test.ts: compat fix - the merged cycle has line mode after slider-only - src/widgets/__tests__/ThinkingEffort.test.ts: keeps the fork's real-settings-file harness, ports upstream's sirmalloc#777 cases onto it - bun.lock: upstream dependency updates, re-resolved by bun install - docs/test-retirements.md: ledger for 7 tests upstream replaced (sirmalloc#781 tab as one space, sirmalloc#805 settings write failures, sirmalloc#800 Zed IDE link mode), each naming its replacing test
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.
What
In a Claude Code session left idle, Block Usage, Weekly Usage and the per-model weekly widgets now catch up with usage from other sessions or devices. Once the session's last response is more than three minutes old, they show the usage API's percent when it's newer than the one Claude Code sent with that response.
Why
Claude Code sends the 5-hour and weekly percents with each of a session's API responses, and ccstatusline shows those over the usage API's. A session left idle keeps the percents from its last response. With
refreshIntervalset, its line redraws on that interval, but with the same numbers: while another session took the 5-hour block from 20% to 60%, an idle one still said 20% until its next prompt. On this machine, withrefreshInterval: 30, idle sessions' lines looked frozen although Claude Code was rerunning the command every 30 seconds.How
/clear): the payload's percents stand.getUsageFetchedAtMs), for the same window (resets within a minute of each other), and no lower: usage never falls within a window, so a lower percent is another login's, after the credentials changed since the session's last response. Once the payload's window has reset, the API's current window wins.Demo
Piped with fake data in a scratch HOME: an idle session whose last response, 20 minutes ago, came with 5h 20% and weekly 50%, while the usage API's cache, written just now, says 60% and 55%. Before, the line keeps the payload's 20% and 50%. After, it shows the API's 60% and 55%.
Powerline, before and after:
Plain, before and after:
Testing
usage-prefetch.test.ts(a scratch transcript dates the payload, a fake clock fixes now):session-usage-history.test.ts: the 5-hour percent is dated by the API's fetch time once it replaced the payload's.main:bun test3700 pass, 0 fail (Bun 1.4.2).bun run lint: clean.security: an idle session (last response 20 minutes ago) went from5h: 20.0% Weekly: 50.0%to5h: 60.0% Weekly: 55.0%; with a response a minute ago it kept5h: 20.0% Weekly: 50.0%.