fix: use consistent date range for menubar status queries#136
Merged
iamtoruk merged 1 commit intogetagentseal:mainfrom Apr 22, 2026
Merged
fix: use consistent date range for menubar status queries#136iamtoruk merged 1 commit intogetagentseal:mainfrom
iamtoruk merged 1 commit intogetagentseal:mainfrom
Conversation
The menubar showed stale prices because provider all used end:now while provider specific queries used end:endOfDay. Sessions with timestamps after now was captured were excluded from all providers but included in specific provider queries. Use periodInfo.range consistently across all parseAllSessions calls in menubar json status.
iamtoruk
added a commit
that referenced
this pull request
Apr 22, 2026
Stale menubar price fix (#136), variable-width status item default.
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
2 participants
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.
Problem
The menubar was showing stale prices. For example, menu bar showed $13.22 while the panel showed $23.86 for Claude.
Root Cause
The
--provider allquery usedend: now(current moment) while--provider claudeusedend: endOfDay.Sessions with timestamps slightly after
nowwas captured were:This caused the totals to mismatch.
Fix
Use
periodInfo.rangeconsistently across allparseAllSessionscalls in the menubar json status command.Testing
Verified with continuous monitoring for 15+ minutes. All checks pass.