Repository navigation
Conversation
perf(ci): bring CI optimizations to usage branch
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.
Adds a bounded local usage ledger for provider-reported service quantities, without storing transcript text or inferring token counts or prices. Traditional OpenAI-compatible text processing now records token fields when the provider reports them, with purpose and provider breakdowns in the desktop usage page. Cache and reasoning fields remain separate because provider semantics can overlap. Clearing invalidates in-flight writers, and the UI identifies the available data as incomplete.
This remains a draft: ASR, TTS, multimodal and other LLM paths are not fully instrumented, legacy history is limited, and loss accounting and shutdown durability require further work. It builds on #1408 and does not yet satisfy the requested complete usage dashboard.
Validation: focused ledger and provider integration tests, strict core Clippy, macOS cargo check, frontend production build, metrics test and Chromium/WebKit usage tests. Full platform CI and iOS checks are running for this revision.