feat(billing): single-source usage via main-process relay#2358
Draft
k11kirky wants to merge 1 commit into
Draft
Conversation
This was referenced May 25, 2026
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced May 25, 2026
3562601 to
4055770
Compare
923dacd to
08d0f9b
Compare
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.

Problem
The renderer was polling the LLM gateway directly every 30 seconds to fetch usage data, coupling the renderer to the gateway and duplicating polling logic that the
UsageMonitorServicealready handles.Changes
The
UsageMonitorServicenow caches the most recent usage snapshot (latestUsage) and emits aUsageUpdatedevent after every successful poll. Two new methods are exposed:getLatest()to retrieve the cached snapshot synchronously, andrefreshNow()to trigger an immediate poll.The
usageMonitorRouterexposes these via three new tRPC endpoints:onUsageUpdated(a subscription that streams snapshots as they arrive),getLatest(a query to bootstrap the renderer before the first event), andrefresh(a mutation to force an immediate poll). ThellmGateway.usagequery endpoint has been removed since it is no longer needed.The
useUsagehook in the renderer now subscribes toonUsageUpdatedinstead of polling on an interval. It bootstraps fromgetLateston mount and exposes arefetchthat calls therefreshmutation. The window-focus-based refetch interval logic has been removed entirely.How did you test this?
Three new unit tests were added to
service.test.ts:UsageUpdatedis emitted and the snapshot is cached on every successful poll.UsageUpdatedis not emitted and the snapshot remainsnullwhen the gateway throws.refreshNowtriggers a fresh poll and returns the resulting snapshot.Publish to changelog?
No