Repository navigation
Support Bedrock cold recovery with official Codex - #7
Merged
Merged
Conversation
gpazo
marked this pull request as ready for review
October 27, 2026 05:49
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.
Cold checkpoints with the official Codex runtime refused built-in Bedrock providers and the cloud launcher's relative binary path. This change verifies Bedrock recovery offline and pins the installed official binary at trusted worker startup. Codex 0.164.0 remains unmodified.
The verifier keeps network and credentials unavailable, checks native history, and refuses configuration warnings. The egress proof accepts an unreachable-network result only with complete kernel evidence of a loopback-only namespace. The x64 CI fixture installs the cloud launch policy used by the cold checkpoint test.
Cold AWS workers exceeded the ordinary 30-second protocol deadline before their first response. Only the credential-free managed preflight gets a 120-second initialization ceiling. Policy verification, the sandbox canary, other RPC deadlines, and cancellation remain unchanged. Startup telemetry contains fixed labels and elapsed time.
Validation passed on
233b814:npm run check, targeted startup and cancellation regressions, and all CI jobs, including ARM and x64 native cold recovery.The newer main documentation commit is included. Earlier failed attempts remain recorded as failures and were separately cleaned up.