Skip to content

Add Daybreak model pricing - #2902

Open
0xSMW wants to merge 7 commits into
steipete:mainfrom
0xSMW:daybreak-blue-red-pricing
Open

Add Daybreak model pricing#2902
0xSMW wants to merge 7 commits into
steipete:mainfrom
0xSMW:daybreak-blue-red-pricing

Conversation

@0xSMW

@0xSMW 0xSMW commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • price Daybreak Blue at GPT-5.6 Sol rates while preserving its runtime identity
  • price Daybreak Red at published GPT-5.6 Cyber rates; leave undocumented dimensions unavailable
  • require a complete long-context catalog tuple for models with explicit-only pricing
  • preserve models.dev overrides and invalidate cached estimates when bundled pricing changes

Proof

  • exact head: 7b593f52e8e4ab35080ff2f43dadaa3cc8a59c6f
  • redacted real local-session aggregate recorded gpt-daybreak-blue-latest
  • cumulative counters: 5,398,304 input, 4,823,366 cached input, 57,521 output, 5,455,825 total
  • computed standard cost: (574,938 × $5 + 4,823,366 × $0.50 + 57,521 × $30) / 1M = $7.012003
  • counters are cumulative session/thread totals; this evidence does not claim independent per-call attribution
  • focused pricing suite: 57 tests passed
  • architecture gatekeeper suite: 38 tests passed
  • full test suite: 856 selections across 72 groups passed with 0 retries, failures, or timeouts
  • make check: passed
  • GitHub CI: 9/9 checks passed on the exact head

Redacted Daybreak Blue pricing proof

Sources: Blue model, Red model, and API pricing.

@clawsweeper

clawsweeper Bot commented Aug 13, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

@clawsweeper clawsweeper Bot added merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. P2 Normal priority bug or improvement with limited blast radius. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Aug 13, 2026
@clawsweeper

clawsweeper Bot commented Aug 13, 2026

Copy link
Copy Markdown

Codex review: needs maintainer review before merge. Reviewed August 19, 2026, 10:25 AM ET / 14:25 UTC.

ClawSweeper review

What this changes

Adds bundled Daybreak Blue and Red price resolution, preserves exact models.dev overrides, and tests unavailable undocumented pricing dimensions.

Merge readiness

⚠️ Ready for maintainer review - 3 items remain

The patch is correct and its real-session pricing proof is sufficient. Keep this PR open for a maintainer decision on whether CodexBar should ship bundled fallback rates for Daybreak aliases that may later be retargeted.

Priority: P2
Reviewed head: b0577dda544083de37f529988929f09136d959ef
Owner decision: Required. See Decision needed.

Review scores

Measure Result What it means
Overall readiness 🦞 diamond lobster (5/6) Strong focused coverage and inspected real-session proof support a correct, bounded implementation; only the alias-fallback policy needs maintainer acceptance.
Proof confidence 🦞 diamond lobster (5/6) ✨ media proof bonus Sufficient (screenshot): The supplied redacted terminal image shows a real local Daybreak Blue session aggregate and the resulting after-fix estimate; no private identifiers are visible.
Patch quality 🦞 diamond lobster (5/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Verified Sufficient (screenshot): The supplied redacted terminal image shows a real local Daybreak Blue session aggregate and the resulting after-fix estimate; no private identifiers are visible.
Evidence reviewed 4 items Current implementation: The PR adds distinct local Daybreak Blue and Red identities, uses published fallback rates, and deliberately returns no estimate for Red cache-write or incomplete long-context pricing.
Regression coverage: Focused tests cover local identity preservation, catalog override precedence, missing long-context fields, and the active cache-write lane.
Real behavior proof: The inspected redacted terminal image identifies a real local session with gpt-daybreak-blue-latest and shows the token counters and resulting $7.012003 estimate; the PR discussion clarifies that these are cumulative session counters.
Findings None None.
Security None None.

Live Verification

Command: swift build -c release --product CodexBarCLI && ./.build/release/CodexBarCLI --help

Result: FAIL (failed) — execution before step 1 run: sh -lc pnpm install --ignore-scripts --frozen-lockfile failed: ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-11.22.0.tgz

sh -lc pnpm install --ignore-scripts --frozen-lockfile failed: ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-11.22.0.tgz

Assertions:

  • FAIL expect_output: Usage:

How this fits together

CodexBar derives local cost estimates by combining scanned Codex token counters with pricing resolved from a custom overlay, the models.dev cache, or bundled rates. This PR changes the bundled fallback path for Daybreak model identities and the resulting estimate cache key.

flowchart LR
A[Local Codex usage] --> B[Model identifier]
B --> C[Pricing resolver]
D[Custom price overlay] --> C
E[models.dev cache] --> C
F[Bundled Daybreak rates] --> C
C --> G[Context-rate selection]
G --> H[Local cost estimate]
Loading

Decision needed

Question Recommendation
Should CodexBar ship bundled fallback prices for Daybreak aliases that can be retargeted, with models.dev taking precedence when available? Approve documented fallbacks: Ship the Blue and Red fallback mapping and update the bundled table when the provider changes public alias targets or rates.

Why: The code is internally consistent, but accepting a mutable alias as an offline pricing fallback is a product-data policy choice rather than a mechanical correctness question.

Before merge

  • Resolve merge risk (P1) - Daybreak aliases may be retargeted or repriced; exact models.dev entries take precedence, but offline or missing catalog data will continue to use the bundled mapping until it is updated.
  • Complete next step (P2) - A maintainer should choose whether mutable Daybreak aliases are acceptable bundled fallback inputs before merge.
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Pricing and test delta production +89 net, tests +294 net The added policy is accompanied by focused coverage for fallback, override, long-context, and cache-write cases.

Merge-risk options

Maintainer options:

  1. Accept the documented fallback policy (recommended)
    Merge with the understanding that mutable Daybreak aliases require a bundled-rate update if their public target or list prices change.
  2. Use catalog-only Daybreak pricing
    Pause this PR if maintainers prefer missing offline estimates over a bundled mapping for aliases that may move.

Technical review

Best possible solution:

Approve the documented fallback policy only if maintainers accept periodic updates for mutable Daybreak aliases, while retaining exact models.dev precedence and unavailable estimates for undocumented dimensions.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a bug reproduction: this is a new pricing capability, and the submitted terminal proof shows the added Blue estimate against a redacted real local session.

Is this the best way to solve the issue?

Yes for the implementation mechanics: exact catalog records override bundled data and undocumented dimensions remain unavailable; maintainer approval is still needed for the mutable-alias fallback policy.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 453174fe13ee.

Labels

Label changes:

  • add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
  • remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.

Label justifications:

  • P2: This changes local cost estimates for two model aliases without indicating a security, availability, or urgent workflow failure.
  • merge-risk: 🚨 other: A shipped offline fallback can become stale if a mutable Daybreak alias changes target or public rate.
  • rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The supplied redacted terminal image shows a real local Daybreak Blue session aggregate and the resulting after-fix estimate; no private identifiers are visible.
  • proof: sufficient: Contributor real behavior proof is sufficient. The supplied redacted terminal image shows a real local Daybreak Blue session aggregate and the resulting after-fix estimate; no private identifiers are visible.
  • proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The supplied redacted terminal image shows a real local Daybreak Blue session aggregate and the resulting after-fix estimate; no private identifiers are visible.

Evidence

What I checked:

Likely related people:

  • 0xSMW: Authored the merged GPT-5.6 Sol/Terra/Luna pricing implementation that established the fallback and cache-invalidation pattern extended here. (role: introduced adjacent bundled pricing behavior; confidence: high; commits: aa40f1eb4b5e; files: Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift)
  • Yuxin Qiao: Authored recent provider-qualified lookup, refresh, and historical-pricing changes in the same pricing resolver. (role: recent pricing-routing contributor; confidence: high; commits: 728ca278d440, 2371835a13d4, b14166aaf2e8; files: Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift)
  • Peter Steinberger: Git shortlog shows the strongest long-term contribution concentration in the pricing resolver, including catalog and API Fast behavior. (role: frequent pricing-area contributor; confidence: medium; commits: 501e95150fd5, 405a2a467867; files: Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (8 earlier review cycles)
  • reviewed 2026-08-13T09:03:11.836Z sha 31c6db3 :: needs real behavior proof before merge. :: [P1] Remove unverified Daybreak identifiers | [P2] Normalize before excluding Blue from Fast pricing
  • reviewed 2026-08-13T09:22:13.817Z sha d7b1d50 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-13T11:08:51.604Z sha d7b1d50 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-14T06:25:27.900Z sha dbb5ccc :: needs changes before merge. :: [P2] Reject incomplete long-context pricing tuples
  • reviewed 2026-08-14T07:27:13.202Z sha 088d3aa :: needs changes before merge. :: [P2] Validate cache-write availability in the active pricing lane
  • reviewed 2026-08-14T07:51:34.525Z sha 7b593f5 :: needs maintainer review before merge. :: none
  • reviewed 2026-08-14T08:32:32.633Z sha 7b593f5 :: needs maintainer review before merge. :: none
  • reviewed 2026-08-18T05:56:39.451Z sha 497ba47 :: needs maintainer review before merge. :: none

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 31c6db31da

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift Outdated
@0xSMW

0xSMW commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

Addressed the review findings in d7b1d50:

  • provider-qualified local Blue IDs no longer receive API Fast pricing
  • missing long-context prices become unavailable at the resolved catalog threshold
  • public Blue and Red aliases are documented by the linked OpenAI model pages
  • an isolated, network-denied scan of a real local session identified gpt-daybreak-blue-latest and priced 5,455,825 tokens at $7.012003

Focused pricing tests (55), architecture gatekeeper tests (38), and make check pass.

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Aug 13, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

@clawsweeper clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. and removed rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. labels Aug 13, 2026
@0xSMW

0xSMW commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

@clawsweeper re-review last review seems stuck

@clawsweeper

clawsweeper Bot commented Aug 13, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

@clawsweeper clawsweeper Bot added rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. and removed rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. labels Aug 13, 2026
@0xSMW

0xSMW commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

Exact-head real-session proof for dbb5ccc869de1889a2eee156fd464ca46d7acf10:

source: redacted aggregate from one real local Codex session log
session date: 2026-08-12
network: not used
credentials / account IDs / session IDs / paths / prompts: REDACTED

model context:          gpt-daybreak-blue-latest
input_tokens:           5,398,304
cached_input_tokens:    4,823,366
output_tokens:             57,521
reasoning_output:          18,636 (included in output_tokens)
total_tokens:           5,455,825

uncached_input = 5,398,304 - 4,823,366 = 574,938

(574,938 × $5.00
 + 4,823,366 × $0.50
 + 57,521 × $30.00) / 1,000,000

RESULT: $7.012003

The exact cumulative total_tokens value occurs in one local log whose model context is gpt-daybreak-blue-latest. These are cumulative session/thread counters; this evidence does not claim independent per-call attribution.

Verification on the merged exact head:

  • CostUsagePricingTests: 55 passed
  • make test: 856 selections across 72 groups passed; 0 retries, failures, or timeouts
  • make check: passed

Redacted Daybreak Blue pricing proof

@clawsweeper re-review
@codex review

@clawsweeper

clawsweeper Bot commented Aug 14, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dbb5ccc869

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift Outdated
@clawsweeper clawsweeper Bot added proof: sufficient Contributor real behavior proof is sufficient. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. and removed rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Aug 14, 2026
@0xSMW

0xSMW commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

The partial long-context pricing finding is fixed in 088d3aa98, its review thread is resolved, and the exact head passes focused pricing tests, architecture gatekeeper tests, make check, and the full 72-group suite with zero failures, retries, or timeouts. The redacted real-session proof remains attached above.

@codex review
@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Aug 14, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 088d3aa98f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift
@0xSMW

0xSMW commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

The active-lane cache-write finding is fixed in 7b593f52e, its thread is resolved, and the exact head passes 57 focused pricing tests, 38 architecture gatekeeper tests, make check, and the full 72-group suite with zero failures, retries, or timeouts. The redacted real-session proof remains attached in the PR body.

@codex review
@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Aug 14, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 7b593f52e8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@0xSMW

0xSMW commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

Final exact-head verification is complete: all 9/9 GitHub checks pass on 7b593f52e, automated review completed with +1, all review threads are resolved, local focused suites and make check pass, the full local 72-group suite has zero failures/retries/timeouts, and the accepted redacted behavior proof is attached.

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Aug 14, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

@clawsweeper clawsweeper Bot added proof: 📸 screenshot Contributor real behavior proof includes screenshot evidence. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. and removed status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Aug 14, 2026
@0xSMW

0xSMW commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Aug 18, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

…ricing

# Conflicts:
#	Sources/CodexBarCore/Generated/CodexParserHash.generated.swift
#	Tests/CodexBarTests/ProviderArchitectureGatekeeperTests.swift
@0xSMW

0xSMW commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Aug 19, 2026

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

Re-review progress:

@clawsweeper clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. P2 Normal priority bug or improvement with limited blast radius. proof: 📸 screenshot Contributor real behavior proof includes screenshot evidence. proof: sufficient Contributor real behavior proof is sufficient. rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant