Repository navigation
fix: correct model pricing and usage statistics for v1.2.1 - #13
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e6834116ea
ℹ️ 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".
| "anthropic/claude-haiku-5-5": ModelPrice(input: 0.1, output: 0.5, cacheRead: 0.01, cacheWrite5m: 0.125, cacheWrite1h: 0.2, | ||
| longContextThreshold: 100_000, | ||
| longContextInputMultiplier: 5, longContextOutputMultiplier: 5), |
There was a problem hiding this comment.
Retarget the Haiku family fallback to 5.5
When a log contains an unrecognized Haiku version such as claude-haiku-5-6, exactCanonicalKey preserves the unknown ID and price(forCanonicalKey:) still routes every claude-haiku-* ID to Haiku 4.5. After making 5.5 the current Haiku tier here, these approximate rows use 4.5's $1/$5 rates instead of 5.5's $0.10/$0.50 rates and miss the new 100K threshold, overestimating a short request by 10×. The family fallback should be advanced to the newly current tier as well.
Useful? React with 👍 / 👎.
Correct API estimates for GPT-6.1 Sol, Claude Sonnet 5.5, and Claude Haiku 5.5, including cache prices and Haiku's 100K prompt threshold. Preserve older model rates and update the current Sonnet/Haiku aliases.
Include every project in the Cost tab, follow Codex working-directory changes per turn, and apply one snapshot cutoff to usage totals and trends. Invalidate old parser caches so existing logs are reattributed on upgrade. Stamp version 1.2.1 and include its release notes.
Validation:
swift buildandmake testpassed locally. Six regression tests cover pricing, prompt boundaries, project totals/details, snapshot cutoffs, and modern/legacy Codex directory changes. Their assertion bodies produced 49 failures before the fixes and zero afterward using a local Command Line Tools runner; the full XCTest suite runs in CI.