Repository navigation
fix: show a Codex subagent's follow-up turn in a new subagent session - #634
Merged
Merged
Conversation
Codex reports a follow-up to a finished subagent only as an `interacted` activity and a new child turn, so the child stayed terminal and its turn was dropped. Reopen a finished child when it starts a new turn. Fixes IJAI-3527
Codex records a follow-up to a finished subagent as an `interacted` activity, but history replay opened a new child generation only on `started`, so the child's later turns were not replayed. Open the next generation on `interacted` when the child thread has that turn. Refs IJAI-3527
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.
Fixes IJAI-3527.
Codex reports a follow-up to a finished subagent only as a
subAgentActivityof kindinteractedplus a new child turn, not as acollabAgentToolCall. The finished child stayed closed, so its follow-up turn was dropped live and skipped on session load.<thread>:generation:N) when it starts a new turn.interactedwhen the child thread has that turn.