You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit add8a55
Browse filesBrowse the repository at this point in the historyBrowse files
fix(responses): keep compaction blobs on the backend that minted them
A replayed compaction item carries an `encrypted_content` blob only its minting
backend can decode, and Codex replays it on every later turn. Two paths modified
or misrouted it, and because the item outlives the failure in the client
transcript, both wedged the session until its history was cleared — the routed
compaction turn the proxy itself drives replays the same item.
Relay: `scrubOcxCompactionItems` treated every non-`ocx1:` blob as OpenAI's and
forwarded it verbatim, with no check that the destination was the issuer. A
session that compacted on a canonical route and then switched to a routed
provider sent that blob to an upstream that could only answer "Could not decode
the compaction blob". Native blobs now travel only to destinations that mint
them — forward-auth routes, which relay the caller's own OpenAI credentials to
the ChatGPT backend or a relay in front of it, and the official OpenAI API under
key auth — and degrade elsewhere to the same opaque note the bridged parser uses.
Backfill: the response-side exemption list named `compaction` alone, so
`compaction_summary` and `context_compaction` received synthesized ids that the
client stored and replayed as "modified from the compact response". That
divergence was possible because the compact wire family was enumerated in three
places; it is now one predicate in `src/responses/compaction.ts`.
Co-Authored-By: Claude Fable 5 <[email protected]>
0 commit comments