Restore V2 agent identities on root thread resume#32837
Merged
copyberry[bot] merged 1 commit intoJul 13, 2026
Merged
Conversation
## Why After a cold resume, a Multi-Agent V2 root thread must still be able to address its persisted descendants even though their runtimes are not reopened eagerly. ## What changed - Restore metadata for open descendant agents when resuming a V2 root thread. - Preserve each descendant's path, nickname, and role while leaving its runtime unloaded until a message targets it. - Reuse the spawn metadata preparation path so restored identities retain the same reservation and naming checks as newly spawned agents. ## Testing Added an end-to-end cold-resume test that follows up with a persisted agent by name and verifies that the original agent thread is loaded on demand. GitOrigin-RevId: a1663c1ae60eefadb948cd39f933cd3bbb49a492
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/a1663c1ae60eefadb948cd39f933cd3bbb49a492
branch
from
July 13, 2026 17:25
c0cb238 to
0882392
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/a1663c1ae60eefadb948cd39f933cd3bbb49a492
branch
July 13, 2026 17:26
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Restore V2 agent identities on root thread resume
Why
After a cold resume, a Multi-Agent V2 root thread must still be able to
address its persisted descendants even though their runtimes are not reopened
eagerly.
What changed
unloaded until a message targets it.
same reservation and naming checks as newly spawned agents.
Testing
Added an end-to-end cold-resume test that follows up with a persisted agent by
name and verifies that the original agent thread is loaded on demand.