Skip to content

pricing: gpt-6.2-astra is not on the pricing card; every Codex step is costed at the Sonnet fallback #14741

Open

Description

@rjwalters

What happens

The fleet moved Codex draws from gpt-6-astra to gpt-6.2-astra on 2026-11-18. The pricing card in effect does not list it, so every Codex usage span is costed at the newest Sonnet rate:

[WARN] Unknown model 'gpt-6.2-astra' is not on the pricing card in effect — /home/ubuntu/loom-daemon/.loom/pricing.json (verified 2026-09-18); cost is being estimated at the newest Sonnet rate and may be badly wrong

That is about 40–90 WARNs/h per worker (400 on worker-2 in the current log). Cost telemetry for every Codex step is wrong until it is priced.

#10750 / #10777 fixed the same gap for gpt-6-astra / gpt-6.1-sol.

What to do

  • Add gpt-6.2-astra (and any other model the fleet store's roleDraw currently names) to the pricing card, with the verification date and source.
  • Consider a CI check that every model named in shipped defaults is on the card, so the next model bump cannot ship unpriced.

Acceptance

  • No Unknown model 'gpt-6.2-astra' WARN on a host running the fixed release.
  • Codex usage spans carry a cost from the card, not the Sonnet fallback.

Filed from an attended fleet check on 2026-11-20.


Curator Enhancement (2026-11-20, verified against origin/main @ 21f0291)

Problem Statement

The pricing card has gpt-6-astra and gpt-6.1-sol rows but no gpt-6.2-astra row. The card is an ordered substring cascade, and "gpt-6-astra" is not a substring of "gpt-6.2-astra" (checked by reading match in defaults/pricing.json:184-185). The new id therefore falls through to the Sonnet fallback and logs the WARN quoted above. The card deliberately has no trailing gpt-6 catch-all, because the variants differ up to 100x in price (see notes in defaults/pricing.json). The fix is a new explicit row.

Acceptance Criteria

  • defaults/pricing.json and .loom/pricing.json each gain a gpt-6-2-astra row with "match": ["gpt-6.2-astra"], placed BEFORE any row that could shadow it.
  • The rates come from the vendor page named in notes (https://platform.openai.com/docs/pricing, Standard tier, short-context). The Builder reads them live. This curation does NOT supply a price and none is to be guessed.
  • notes records the read date and source for the new row. verified_on handling follows the existing rule: it stays at the OLDEST vendor date.
  • The compiled card in loom-daemon/src/activity/resource_usage.rs (match chain near line 375, doc table near line 218) gets the same row. shipped_pricing_asset_agrees_with_the_compiled_card and both_pricing_entry_points_agree pass.
  • A test asserts ModelPricing::lookup("gpt-6.2-astra") is Some and not equal to the gpt-6-astra rates unless the vendor page says so (extend the test near resource_usage.rs:841).
  • Any other model currently named in the fleet store's roleDraw that is missing from the card is added in the same PR. The Builder lists those it found in the PR body.

Implementation Guidance

Copy the gpt-6-astra row shape, set the new id, match and rates, and mirror it into the compiled card. Rejected: a gpt-6 catch-all (the card forbids it, since prices span 100x); fuzzy-matching gpt-6.2-astra onto the gpt-6-astra rates (a guessed price is worse than an unpriced WARN).

Out of Scope

  • The issue's "consider a CI check" suggestion. Filed separately at loom:triage if wanted; it needs a decision on which "shipped defaults" source lists models.
  • Modelling Long-context, Batch, Flex, Fast or Ultrafast tiers.
  • Backfilling or re-costing historical spans.

Affected Files

  • defaults/pricing.json - add gpt-6-2-astra row and notes entry
  • .loom/pricing.json - same row (resync copy of the defaults)
  • loom-daemon/src/activity/resource_usage.rs - compiled-card row and lookup test
  • loom-daemon/tests/model_pricing_card.rs - extend only if its agreement test needs it

Test Plan

  • Manual verification: cargo test -p loom-daemon pricing (targeted, -j at most 2) passes.
  • Automated tests: the lookup test and the card-agreement tests above.
  • Edge cases: openai/gpt-6.2-astra (prefixed id) also resolves; gpt-6-astra still resolves to its own row.
  • Out-of-band: the post-release Unknown model 'gpt-6.2-astra' WARN is gone on a host running the fixed release.

Activity

  1. added
    loom:triageNew issue awaiting Curator enhancement. Applied by: humans or any agent filing an issue (intake).
    on Nov 20, 2026
  2. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    PR #14741's loom:curating claim is held by the curator of sweep step-curator-14741-1795150288 on host host-d0749b00. This comment is a PR lease record (#9401): its liveness signal is its own forge-assigned updated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. See defaults/docs/lease-record.md § "PR-phase leases".

  3. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    📝 Curator: Enhanced the body with AC, guidance, Out of Scope, affected files and a test plan; original preserved above. Duplicate check: none. Premise gate: out of scope. The rate for gpt-6.2-astra is deliberately not supplied; the Builder must read it from the vendor page.

    loom dashboard

  4. added
    loom:curatedCurator-enriched, awaiting approval. Additive; coexists with loom:issue. Applied by: Curator only.
    points:2Story-point size class 2. Applied by: Curator via loom-daemon curation-complete.
    and removed
    loom:curatingCurator is enhancing this issue. Applied by: Curator only (claim label).
    loom:triageNew issue awaiting Curator enhancement. Applied by: humans or any agent filing an issue (intake).
    on Nov 20, 2026
  5. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    PR #14741's loom:evaluating claim is held by the champion of sweep step-champion_promote-14741-1795150408 on host host-7ec0fa4c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assigned updated_at, renewed while the champion works and released when it is done. Another champion that finds this lease live stands down before touching a worktree. See defaults/docs/lease-record.md § "PR-phase leases".

  6. added
    loom:evaluatingChampion is evaluating this proposal (claim label, stale after 15m). Applied by: Champion only.
    loom:issueApproved for work. Applied by: humans, Champion, sweep gate — see curator.md.
    and removed
    loom:evaluatingChampion is evaluating this proposal (claim label, stale after 15m). Applied by: Champion only.
    on Nov 20, 2026
  7. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    Champion Review: APPROVED

    This issue has been evaluated and promoted to loom:issue status. All quality criteria passed:

    • Clear problem statement
    • Technical feasibility
    • Implementation clarity
    • Value alignment
    • Scope appropriateness
    • Quality standards
    • Risk assessment
    • Completeness

    Cited paths and lines verified on origin/main @ 21f0291 (defaults/pricing.json, .loom/pricing.json identical, resource_usage.rs match chain and tests, tests/model_pricing_card.rs). No duplicate open PR or issue. Author gate: TRUSTED.

    Goal Alignment: Restores correct cost telemetry for every Codex step (currently costed at the Sonnet fallback, ~40-90 WARNs/h per worker). The Builder must read the gpt-6.2-astra rates live from the vendor page; none is to be guessed.

    Ready for Builder to claim.


    Automated by Champion role

    loom dashboard

  8. added
    loom:buildingBuilder is implementing this issue. Applied by: Builder only (claim label).
    and removed
    loom:issueApproved for work. Applied by: humans, Champion, sweep gate — see curator.md.
    on Nov 20, 2026
  9. 19 remaining items

  10. rjwalters commented on Nov 20, 2026

    @rjwalters
    MemberAuthor

    This issue is being worked by an in-session /loom:sweep run sweep-insession-s38728-ThuNov191721502026 on host host-d9142cf3, published at 2026-11-20T09:27:15Z. This comment is a lease record (Issue #6320, Epic #6165) in the identical format loom-daemon's dispatch-time write uses (#6179) — its liveness signal is this comment's own forge-assigned updated_at, never the timestamp in this text. It is renewed by sweep-lease-renew.sh (#6180) for as long as this sweep's own process is alive, and simply ages out afterwards. Readers: the daemon's reclamation gate (#6286) refuses to reclaim this claim while the lease is fresh, dispatch-time ordering (#6287) yields to it, and sweep-lease-fence.sh (#6309) fences this sweep's own push/PR-open against it. See defaults/docs/lease-record.md.

  11. rjwalters commented on Nov 20, 2026

    @rjwalters
    MemberAuthor

    This lease (sweep sweep-insession-s38728-ThuNov191721502026 on host host-d9142cf3) was released with loom-daemon lease release (#12103): the claimant stood down and its renewal loop was stopped.

  12. added
    loom:issueApproved for work. Applied by: humans, Champion, sweep gate — see curator.md.
    and removed
    loom:buildingBuilder is implementing this issue. Applied by: Builder only (claim label).
    on Nov 20, 2026
  13. rjwalters commented on Nov 20, 2026

    @rjwalters
    MemberAuthor

    Partial Increment Merged

    PR #14772 merged with a non-closing Part of / Contributes to reference, so this issue remains open for further work.

    Action taken:

    • Removed loom:building label
    • Added loom:issue label to return to the ready queue

    This issue is now available for the next increment (a subsequent /loom:sweep will treat it as ready rather than in-flight).


    Reset by merge-pr.sh (#3667) at 2026-11-20T09:47:58Z

    loom dashboard

  14. added
    loom:triageNew issue awaiting Curator enhancement. Applied by: humans or any agent filing an issue (intake).
    and removed
    loom:issueApproved for work. Applied by: humans, Champion, sweep gate — see curator.md.
    on Nov 20, 2026
  15. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    PR #14772, which closes this issue (a closing keyword, or built on the issue's own feature/issue-N branch), has merged, but the issue is still open. It goes back to Curator (loom:triage) instead of to a Builder: close it if #14772 finished the work, or curate it again if work remains. This is done once per merged PR (#11853, #12251).

  16. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    PR #14741's loom:curating claim is held by the curator of sweep step-curator-14741-1795174048 on host host-e1d4c843. This comment is a PR lease record (#9401): its liveness signal is its own forge-assigned updated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. See defaults/docs/lease-record.md § "PR-phase leases".

  17. loom-fleet-dispatch commented on Nov 20, 2026

    @loom-fleet-dispatch
    Contributor

    Curator (2026-11-20, landed-route for PR #14772, verified on origin/main): the code criteria are delivered. defaults/pricing.json:173 has the gpt-6-2-astra row, the compiled card matches it (resource_usage.rs:379), and the lookup tests cover bare, openai/ and codex/ ids. The PR priced the only explicit model in the current roleDraw.

    Still open after #14772 is only the out-of-band acceptance item: confirm that a host running the fixed release no longer logs Unknown model 'gpt-6.2-astra' and that a Codex usage span carries a card cost. That needs a live fleet host, so no Builder step can do it. Routing to loom:operator. Step for a human: after a host has resynced .loom/pricing.json or run a release newer than v0.20.5, grep its daemon log for the WARN, then close this issue. The CI-check idea stays out of scope, as curated.

    loom dashboard

  18. added
    loom:operatorA human must act or decide; the body's decision block says what. Only a human removes it.
    and removed
    loom:triageNew issue awaiting Curator enhancement. Applied by: humans or any agent filing an issue (intake).
    loom:curatingCurator is enhancing this issue. Applied by: Curator only (claim label).
    on Nov 20, 2026
  19. rjwalters commented on Nov 20, 2026

    @rjwalters
    MemberAuthor

    The published v0.20.6 tag at e3642753 contains the new pricing row. An authorized telemetry read from publication at 12:06:37 UTC through 13:36 UTC captured 32 naturally emitted Codex usage spans for gpt-6.2-astra across workers 1–4. All 32 reported Loom 0.20.0 at 4fc12aee9, and no span carried a USD cost. A same-worker sample of 403 dispatch spans also identified only that older producer revision, through the last sampled dispatch at 13:35:28 UTC.

    The scoped structured-log feed returned 165 WARN-severity records and zero exact missing-model messages, alongside those unpriced spans. That feed cannot establish coverage of the daemon's stderr or its deduplicated warning path. A fresh installed card or newer release plus correctly priced natural usage still needs to be observed on the same worker before accepting this issue. The older pricing asset can take precedence over the compiled fallback when it is present.

    loom dashboard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    loom:curatedCurator-enriched, awaiting approval. Additive; coexists with loom:issue. Applied by: Curator only.loom:operatorA human must act or decide; the body's decision block says what. Only a human removes it.points:2Story-point size class 2. Applied by: Curator via loom-daemon curation-complete.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions