Skip to content

feat: record reported text-processing usage - #1414

Draft
appergb wants to merge 9 commits into
feat/service-usage-dashboardfrom
feat/service-usage-ledger
Draft

appergb wants to merge 9 commits into
feat/service-usage-dashboardfrom
feat/service-usage-ledger

Conversation

@appergb

@appergb appergb commented Nov 8, 2026 •

Copy link
Copy Markdown
Collaborator

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.

@appergb appergb changed the title feat(core): start local service usage ledger feat: record reported text-processing usage Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant