Repository navigation
fix(grokbot): dim a reading past its reset, and find the active slot - #518
Merged
Merged
Conversation
Grok Bot only rewrites its weekly cache when it fetches, and can run for hours past a reset without doing so. The reading was only treated as stale past Grok Bot's own day-long expiry, so the notch showed the finished week's percent as live and sat on "Resetting…". A reading whose reset has passed now reads stale too. The slot blob names the account `auth0|user_…` while the cache key spells it URL-encoded (`auth0%7Cuser_…`), so the active account never matched and the freshest file always won. Decode the key's slot before comparing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vinzdg
added a commit
that referenced
this pull request
Nov 6, 2026
…panese - Claude Code sessions named by their title (#510); the lone Claude ring named when Claude Desktop uses another account (#511). - Cost indexer stats transcripts (#501) and acts only on changed readings (#514). - Krea AI (#490), a Xiaomi MiMo preset (#503), Grok multi-account (#515), Japanese up to date (#492), deficit rings by soonest expiry (#496). - Fixes: Claude weekly-only /usage (#527), remote Claude reuse (#522), remote Codex behind a proxy (#523), Kiro V2 engine and parsing (#528, #517), Kimi monthly quotas (#526), MiniMax China sk-api keys (#529), Grok Bot resets (#518), Developer ID team check (#491). - Windows: the taskbar strip drawn as the notch (#506), Claude accounts as rows (#502), Antigravity through agy.exe (#507), a hook auth token (#525).
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.
Summary
Grok Bot only rewrites its weekly cache when it fetches. It can run for hours after a reset without doing that. The notch kept showing the finished week's percent as live, and the card stayed on "Resetting…" until Grok Bot's own day-long
expiresAtMsran out.The selected account also never matched its cache. The slot blob writes
auth0|user_…, while the cache key writes the same slot URL-encoded asauth0%7Cuser_….Evidence
Real cache on a Mac (local time): read 11-01 18:23,
nextResetMs11-01 19:10,expiresAtMs11-02 18:23. That left the notch on "Resetting…" at 12% for about 23 hours.The fixture's hard-coded
nextResetMs(2026-10-13) is now in the past. It is now a parameter that defaults to three days out. The test that pins the recorded date passes that date explicitly.Merge Danger
Door: two-way
Blast Radius: Grok Bot only
After a reset, Grok Bot's ring is dimmed and dated, not shown at full strength, until Grok Bot writes a fresh reading. With several signed-in accounts, the selected account's cache now wins over a fresher neighbour, as intended.
🤖 Generated with Claude Code