Preserve follow-up replies in built-in Codex subagent chats - #408
Merged
Conversation
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.
Built-in Codex could lose the interaction marker and answer after sending a follow-up to a completed subagent. Pin the published @openaide/codex-acp 1.2.2 release, which reopens the child on successful sendInput even when Codex supplies its previous completed state (OldKrab/codex-acp#29).
Retain the session-recovery patch unchanged, regenerate exact artifact digests, and advance the managed cache revision. Native Codex remains at its existing locked version.
Validation: adapter regression reproduced before the fix; 555 adapter tests and typecheck passed. Both OpenAIDE offline recovery suites passed. All 32 Rust provisioner/configuration/catalog tests passed. Target built-in Codex live verification passed: one child, replies 323 and 77, both parent markers, and no temporary custom Codex agent. Packaged provisioning, resume/load, and real native policy recovery smoke passed. Browser verification confirmed both markers and replies. All six PR CI checks passed.