Uh oh!
There was an error while loading. Please reload this page.
feat(usage): add OpenCode provider priced from models.dev - #6014
feat(usage): add OpenCode provider priced from models.dev#6014SkyVence wants to merge 5 commits into
Conversation
The usage page only scanned Claude Code and Codex transcripts. Add OpenCode as a third provider: read its SQLite session store (~/.local/share/opencode/ opencode.db) with node:sqlite, price go/zen models from models.dev, and render the provider in web and mobile. OpenCode messages carry the real billed cost, so buckets use providerReported cost; the models.dev go/zen rates back the fallback and cache-savings figures. Model names stay qualified as providerID/modelID so the two subscriptions never collapse (deepseek-v4-flash is $0.07 vs $0.14 per 1M across tiers). USAGE_CONTRACT_VERSION bumped to 4; the scan cache gained a WAL identity so a live opencode session is never served stale. Done by opencode (deepseek-v4-flash) on the T3 Code worktree.
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
ensureRates replaced the shared rates table with a LiteLLM-only copy, dropping the models.dev go/zen overlay that ensureOpenCodeRates had merged in; the overlay was only re-applied when its own fetch ran, so an interleaving where the LiteLLM snapshot expired before the models.dev snapshot (a transient models.dev failure, a size-0 parse, or diverging disk timestamps) left the served table unpriced for OpenCode models until the models.dev cache lapsed. Keep the overlay in its own table and always re-merge it over litellmRates at read time, so one source refreshing can never evict the other's prices. The regression test drives the two TTLs apart with a failing first models.dev fetch and asserts the opencode models stay priced. Done by opencode (deepseek-v4-flash) on the T3 Code worktree.
There was a problem hiding this comment.
One convention issue found in the new server test: the UsageService module is imported with an aliased named import instead of a module namespace. Everything else in the diff (dependency acquisition via HostProcessEnvironment/HostProcessPlatform, make/layer shape, test-only provideService seams) follows the service conventions.
Posted via Macroscope — Effect Service Conventions
Uh oh!
There was an error while loading. Please reload this page.
Match the module convention used by server.ts, ws.ts and server.test.ts (`import * as UsageService`), instead of the aliased named import. Done by opencode (deepseek-v4-flash) on the T3 Code worktree.
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
ApprovabilityVerdict: Needs human review This PR adds OpenCode as a new usage provider, introducing substantial new capability including external API integration (models.dev), SQLite database reading for OpenCode's session store, new parsing logic, and UI changes. New features with this scope warrant human review. You can customize Macroscope's approvability policy. Learn more. |
There was a problem hiding this comment.
One finding in apps/server/src/usage/UsageService.ts: the rate-table rename left a stale rates shorthand in the UsageAggregator construction. No Effect service convention violations found in the rest of the changed scope (namespace imports, service tag/make/layer order, dependency acquisition, and test seams all look consistent with the conventions).
Posted via Macroscope — Effect Service Conventions
| timeZone: input.timeZone, | ||
| sinceDay: input.sinceDay, | ||
| untilDay: input.untilDay, | ||
| rates: servedRates, |
There was a problem hiding this comment.
rates was renamed to litellmRates in this PR, but the aggregator options still carry the old rates shorthand a few lines below, next to this new rates: servedRates. That is both a duplicate property and a reference to an identifier that no longer exists, so the module will not type-check. Consider dropping the stale entry.
...hourlyWindow,
- rates,
});Posted via Macroscope — Effect Service Conventions
t3dotgg
commented
Aug 23, 2026
Note 🤖 GPT-5.6 Sol responding on behalf of Theo Closing this PR after an automated pass over open pull requests. Duplicates another usage-reporting proposal while adding a broad client, contract, or provider integration. |
Problem
The usage page only scanned Claude Code and Codex transcripts, so sessions driven through OpenCode never showed up — no tokens, no cost, and no visibility into what the go/zen subscriptions are actually being billed.
Fix
~/.local/share/opencode/opencode.db) withnode:sqliteand fold its assistant messages into the daily usage scan (provider: "opencode").providerReportedcost; the models.dev go/zen rates back the fallback and cache-savings figures.providerID/modelID, so the go and zen subscriptions never collapse — e.g.deepseek-v4-flashis $0.07 vs $0.14 per 1M tokens across the two tiers.USAGE_CONTRACT_VERSIONbumped to 4; the scan cache gained a WAL sidecar identity so a live OpenCode session is never served stale.Screenshots
Before/after images of the usage page (no OpenCode usage → OpenCode provider with go/zen models)
Done by opencode (deepseek-v4-flash) on the T3 Code worktree.
Note
Add OpenCode as a usage provider with pricing from models.dev
opencodeas a new provider kind in the contract, UI, and server, reading usage from OpenCode's SQLite store (opencode.db) instead of JSONL files.ensureOpenCodeRatesfunction, merging it with existing LiteLLM rates viamergeRateTables.OPENCODE_DATA_DIR,XDG_DATA_HOME, or platform-specific defaults, and includes WAL sidecar identity in the scan cache to avoid stale reads.#a78bfa) with theOpenCodeIconmark in both web and mobile usage charts.Macroscope summarized c88952e.