Repository navigation
v1.47.0: opt-in shared Codex host for a flow walk - #294
Merged
Merged
Conversation
The top walker starts one codex app-server on a Unix socket when the graph sets defaults.codex_host or the operator sets PUPPETMASTER_CODEX_HOST=1. Each Codex agent and judge then runs as a thread on it, not as its own codex exec process. Repairs resume their thread, a cut interrupts only its own turn, and file changes and commands are reported as codex exec items for the write-scope gate. Forks, bypass, native steer, custom executables, non-config extra arguments, other homes and Windows keep codex exec. Version 1.47.0.
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.
What
Opt-in: the top flow walker starts one
codex app-serveron a Unix socket. Each Codex agent and judge of the walk runs as a thread on it, not as its owncodex execprocess."defaults": {"codex_host": true}orPUPPETMASTER_CODEX_HOST=1. Off by default.codex exec --jsonitems. The write-scope gate, rollout usage and resume do not change.codex exec. A host that fails before the turn also falls back.Why
Codex lab R200: about 114 s from
codex execlaunch to the first turn for each cold builder, because the lab guards each process. Native subagents start in 0.05 s (R202).Proof
tests/test_codex_host.py(fake WebSocket host, split frames, cut, approval, resume, walker lifecycle).codex app-serverprocess, 0codex execprocesses. The write-scope gate saw each worker's own path.codex execstart is about 1.7 s).