Repository navigation
Correct missing speed-tier rates and default pricing aliases #1436
Description
Activity
This issue was auto-closed. Issues from new contributors are auto-closed by default.
Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.
Keep the issue short, concrete, and written in your own voice.
If a maintainer replies
lgtmi, your future issues will stay open. If a maintainer replieslgtm, your future issues and PRs will stay open.See CONTRIBUTING.md.
Update: #1437 is outdated. It was auto-closed before the source branch gained the inherited-history accounting fix, and GitHub froze that PR at commit
2500c5b.I pushed the complete four-commit branch at
b9cd694and opened #1438 as the replacement. It contains the inherited child-session replay correction together with the speed-tier and pricing-alias fixes. Focused and full test suites, formatting, type checks, flake checks, and secret scanning pass; all committed fixtures use synthetic data.#1438 was also auto-closed by the contributor gate. Please use #1438 for review and reopening; #1437 can remain closed.
@ryoppippi could this be merged?
hey! so does codex start recording fast/standard mode? they didn't record it before afaik.
Yes. Starting with CLI 0.144.0, rollouts persist
event_msg→thread_settings_applied→thread_settings.service_tier. The recorded values arepriorityfor Fast anddefaultfor Standard. I confirmed this against current upstream source and 0.144.x rollouts.There is one limitation: usage before the first persisted settings snapshot can remain unclassified. #1438 now consumes explicit tier markers chronologically, keeps
--speed fast|standardas full-report overrides, and uses the existing configuration fallback only for unclassified startup, legacy, and headless usage. It also prevents replayed parent settings from leaking into child usage and reconciles copied records deterministically before cost attribution.For all three current 5.6 variants, the update uses the documented 2× API Priority rate. The separate 2.5× figure is account-credit consumption; this report's
costUSDis an API-equivalent estimate. Transition, override, long-context, replay, duplicate-order, and unified-report coverage is included, and the full repository checks pass.The updated PR is #1438 at
65e8005.Automatic implementation was not started because the issue author GitHub email could not be resolved reliably for co-author attribution. A maintainer can implement the issue manually or provide a verifiable author email.
Historical audit: this discussion was auto-closed by the legacy contributor gate. That closure did not assess technical importance.
Audit result: resolved. A later merged change or the current
mainimplementation covers this request. This item is kept for history and does not need to be reopened.
What do you want to change?
Correct two cost-accounting paths in usage reports. When a speed tier has no published multiplier, retain standard pricing instead of assuming 2x. Also resolve a documented unsuffixed pricing family to its default entry before fuzzy matching, while preserving exact and partial user overrides.
The branch also marks golden snapshots as text and removes an unused timing-inference scratch plan.
Why?
The generic multiplier can overstate cost without supporting rate data. Longest-name fuzzy matching can select a non-default sibling, and partially specified overrides can lose inherited fields. Both paths can misstate reported cost.
How? (optional)
Use exact raw entry, canonical alias, then fuzzy fallback for pricing and context metadata. Canonicalize threshold lookups and inherit unspecified values from the canonical base entry. Add regression coverage for rates, context limits, thresholds, and override inheritance.