Repository navigation
Conversation
Warp 0.2026.10 removed total_provider_cost_in_cents and now persists total_billed_cost_in_cents. Read it after total_charged_usage, as Warp does, so conversations without streamed charges keep their billed dollars instead of the credits estimate. Bump the warp parse version and DAILY_CACHE_VERSION to 77.
This branch has not been deployed
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
1 participant
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.
Summary
total_provider_cost_in_centsand now persiststotal_billed_cost_in_cents. Conversations without streamed charges lost their billed dollars and fell back to the credits estimate.total_charged_usageand before credits, the same order Warp uses. The legacy provider cost stays first, so existing numbers don't move.DAILY_CACHE_VERSION77 (76 is taken by fix(codex): read Zstandard-compressed rollouts #1786; merge that first).Testing / Verification
I have tested this locally against real data (not just unit tests)
npm testpassesnpm run buildsucceedsNot a UI change
New tests: billed only, provider only, both, charged plus billed. The billed-only case fails without the fix.
Local Warp history (3 conversations from March, no cost fields) exports byte-identical on main and this branch. It has no billed rows, so the new rung is covered by the tests and Warp's source, not live data.
The daily cache upgrades cleanly from a copy of a real cache, and the Warp slices are unchanged.