Repository navigation
feat(cost): display authoritative models.dev cost_usd in desktop session header #7
Description
Context & Background
In OpenCode upstream commit 7b33bcea4e (feat(desktop): show session tokens and cost on the session view (#53785)), upstream introduced a UI display in the session view header showing accumulated tokens and estimated cost for the active session.
In our fork (developing-today/opencode), we calculate exact per-request USD costs derived from the official models.dev token catalog pricing and store it directly in the route_attempt table under column cost_usd (migration 20261014094820_route_attempt_cost_usd.ts). Currently, upstream's new desktop session cost view computes a rough estimate or reads client-side estimates rather than our authoritative server-calculated database value.
Feature Objective
Wire our authoritative cost_usd database metric from route_attempt directly into OpenCode's session metadata and the desktop session view, ensuring that users see exact dollar costs calculated from the official models.dev pricing snapshot.
Technical Specifications
1. Aggregate Session Cost in Session Service
- In
packages/core/src/session.tsorpackages/core/src/session/generate.ts:- When returning or subscribing to
SessionInfo/ session state: - Query total
cost_usdby summing all attempts forsession_idinroute_attempt:SELECT COALESCE(SUM(cost_usd), 0.0) AS total_cost_usd FROM route_attempt WHERE session_id = ? AND outcome = 'success';
- Populate
session.costwith this exact value (formatted in USD currency, e.g.$0.042).
- When returning or subscribing to
2. Protocol & Client Contract
- In
packages/protocol/src/groups/session.tsandpackages/schema/src/session.ts:- Ensure
SessionInfo.costis typed as a number (USD) and documented as authoritativemodels.devcomputed cost. - When new LLM attempts finish in
publish-llm-event.ts, emit an updated session telemetry event carrying the latest totalcost_usd.
- Ensure
3. Desktop Session UI Component
- In
packages/app/src/session/(orpackages/desktop/src/where#53785renders):- Ensure the header component formats the authoritative
cost_usdvalue:- Values < $0.01:
<$0.01 - Standard values:
$0.04,$1.28
- Values < $0.01:
- On hover, provide a tooltip breaking down input token cost, output token cost, and cache savings.
- Ensure the header component formats the authoritative
Key Files & References
packages/core/src/database/migration/20261014094820_route_attempt_cost_usd.ts:cost_usdcolumn definitionpackages/core/src/model-usage.ts&model-plan.ts: Token catalog pricing and cost calculation formulaspackages/core/src/session/runner/publish-llm-event.ts: Emitting session cost updatespackages/desktop/andpackages/app/src/session/: Session header view components
Acceptance Criteria
- The session view header displays the exact sum of
cost_usdrecorded for that session inroute_attempt. - As new turns complete, the displayed dollar cost updates in real-time.
- Pricing matches official token pricing from the bundled
models.devcatalog. - Unit tests in
packages/core/test/verify session cost aggregation from multiple attempts.
Activity
dezren39 commentedon Oct 27, 2026
Intake review
Still live (verified this run): no aggregation of the authoritative
route_attempt.cost_usdinto session metadata exists inpackages/core/src(noSUM(cost_usd)-style query found), so the desktop session header still cannot be showing the server-calculated figure the filing asks for. Thecost_usdcolumn itself is live and written per attempt (it is the same column opencode #549's observer-retryable finding concerns).Related: opencode #8 (continuation cost stitching — the rollup semantics there affect what a session total should include), opencode #9 (cache savings reporting shares the route_stats surface).
Notes / risks: the smallest of the five opencode feature specs in this batch (effort/m): one aggregate query, one field on session info, one header binding. Risk is mostly definitional — session total should be the sum over all attempts including continuations and retries, and the UI should say so.
Suggested approach: add the aggregate in the session service, expose it on SessionInfo, bind the desktop header to it, and cover the sum with a core test using seeded route_attempt rows.
— fleet monitor intake (repo-fleet-monitor, 2026-10-26 20:19 CDT run)
dezren39 commentedon Oct 28, 2026
🤖 Agent note · triage confirmed — real gap, decomposes into two packets (not one small fix)
b0633cc697lineage). The desktop session header does not display the authoritativeroute_attempt.cost_usdsum, and no existing surface carries that exact number into the session view. Code evidence:route_attempt.cost_usdexists and is written per attempt: migrationpackages/core/src/database/migration/20261014094820_route_attempt_cost_usd.ts; write sitepackages/core/src/session/runner/step.ts:419(cost_usd: SessionUsage.calculateCost(input.model.cost, tokens)).Session.Info.costexists (packages/schema/src/session.ts:48,Money.USD) but is a different number: it is accumulated by the session projector from per-step LLM-event costs (packages/core/src/session/projector.ts:62,cost = session.cost + event.cost), i.e. the event-carried estimate the issue describes — not aSUM(route_attempt.cost_usd). Other consumers depend on this field (e.g. compaction spend,packages/core/src/session/compaction.ts:354), so silently re-sourcing it is a design decision, not a patch.packages/core/src/model-route-log.ts:656(costUsd: coalesce(sum(cost_usd),0)in the sharedusageColumns) andsessionUsageat :659 aggregates it per session — but (a) it is exposed only to route-usage/stats surfaces, not toSession.Infoor the app, and (b) itscostUsdsums all outcomes, while this issue's spec sumsoutcome = 'success'only — the filter is part of the work.packages/app/src/session/header/session-header.tsxandsession-header-actions.tsxcontain no cost or token rendering at HEAD (grep: zero hits) — upstream feat(desktop): show session tokens and cost on the session view anomalyco/opencode#53785's header display is not present in this fork's app header, so the UI piece is build-new, not re-wire.Session.Infofield (e.g.costAuthoritative) sourced from a success-onlyroute_attemptsum vs re-sourcingInfo.cost(must audit projector/compaction consumers first); success-only aggregation can extendModelRouteLog.sessionUsage's columns or a session-scoped query; add the aggregation tests this issue's criterion 4 asks for inpackages/core/test/.packages/app/src/session/header/consuming that field, with the issue's formatting rules (<$0.01under a cent,$0.04/$1.28standard) and the hover breakdown; live update follows the session-info subscription once packet 1 emits it.dezren39 commentedon Oct 30, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 30, 2026
Triage verdict: parts 1–2 LANDED (by a different mechanism), part 3 (header UI) remains — routed as task 3778
Verified on
main3a1c3a0c78(2026-10-30, issue-sweep-rotating):Part 1 — aggregate session cost: LANDED, no SQL SUM needed.
SessionInfo.costexists:packages/schema/src/session.ts:48(cost: Money.USD), served from the session row atpackages/core/src/session/info.ts:37.packages/core/src/session/projector.ts:62,723).packages/core/src/session/runner/step.ts:663computes the event cost and:489computesroute_attempt.cost_usd, both asSessionUsage.calculateCost(input.model.cost, tokens)— identical catalog pricing, two accumulations. ASUM(route_attempt.cost_usd)would add nothing (and would miss non-runner cost events such as compaction,packages/core/src/session/compaction.ts:658, which also feed session cost).Part 2 — protocol & client contract: LANDED.
packages/client/src/solid/data.ts:1505-1513—cost(sessionID)returns the session's own cost for a subsession, or the root family's summed cost (root + subsessions).Part 3 — session header rendering: NOT landed.
packages/appcalls that selector or renders session cost: grep for a.cost(call inpackages/app/src= 0 hits. Every cost reference in the app is model catalog pricing (providers/models), not session spend.Routing: the UI-only remainder is enqueued as queue task 3778 (repo-health-opencode-pilot, small_fix, packet
hidden_files/packet-7-fix.json): render the family cost in the session header via the existing selector,<$0.01under a cent,$X.XXotherwise, reactive as steps land. The tooltip breakdown from the original spec is a stretch goal in the packet only if the data is already in the client store — no new protocol surface.🤖 Agent note · triaged
21 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked-up
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
Session.Info.cost, building a core test harness, then adding UI, tooltip, and live-update coverage. The scheduled lane cannot safely finish that scope; no code edits or worktree were started.dezren39 commentedon Nov 4, 2026
🤖 Agent note · blocked — packet_defect (task 3778)
~/git/fleet/3778-7-cost-headercreated from origin/maincd60d2db90, no code edits madeSUM(route_attempt.cost_usd WHERE outcome='success'), the issue's own intake review says the total should be "the sum over all attempts including continuations and retries", and the current projector total additionally includes compaction spend (packages/core/src/session/compaction.ts, UsageRecorded with no route_attempt row). These are three different totals; the packet must name one and state what happens to the other consumers ofSession.Info.cost(e.g. compaction spend).Session.Info(packages/schema/src/session.ts) carries only totalcost: Money.USDplus token counts — no input-token cost, no output-token cost, and nocache_savings_usd(that column exists only onroute_attempt, aggregated only inpackages/core/src/model-route-log.tsfor stats surfaces). The required hover breakdown (input cost / output cost / cache savings) therefore needs either a schema/protocol addition — which the packet explicitly excludes — or client-side repricing, which the issue itself rejects as the non-authoritative estimate.Session.Info.costupdates today because the projector accumulatesUsageRecordedevents and publishesUsageUpdated. Route attempts are written directly in the runner with no corresponding event, so a SQL-sum source has no defined trigger to refresh the header "as new turns complete" (acceptance 2).