Repository navigation
Add GPT-6.1 Sol and zero-cost Auto-review pricing (v2.7.2) - #41
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
GPT-6.1 Sol usage currently remains unpriced, and separate Auto-review usage has no default rate. Add the published GPT-6.1 Sol input/cache/write/output rates and Codex Fast weighting, and default the exact
codex-auto-reviewmodel to zero cost while retaining raw token counts and pricing coverage.Auto-review zero pricing is explicitly documented as a local accounting policy based on the maintainer-reported Tibo statement, not a verified published API price. Existing manual overrides remain valid and take precedence; resetting one restores zero pricing and refreshes aggregate/session estimates. Main-model usage and unknown models retain their existing semantics.
Update the Dashboard, demo, bilingual docs, and v2.7.2 version/release notes. Fix the timezone assumptions in two existing date tests. No schema change or historical rebuild is required.
Validation
go vetpassed locally.git diff --checkpassed.