Repository navigation
feat(coding-agent): persist subagent lifecycle state - #115
Merged
Issacboy123 merged 2 commits intoAug 28, 2026
Merged
Conversation
Pepps233
force-pushed
the
feat/persist-subagent-lifecycle
branch
from
August 25, 2026 14:36
228eacb to
b941e78
Compare
Pepps233
self-requested a review
August 25, 2026 14:55
Pepps233
approved these changes
Aug 25, 2026
Issacboy123
force-pushed
the
feat/persist-subagent-lifecycle
branch
from
August 27, 2026 10:54
b941e78 to
29d33e0
Compare
Issacboy123
force-pushed
the
feat/persist-subagent-lifecycle
branch
from
August 27, 2026 23:11
29d33e0 to
2877a2e
Compare
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.
Summary
This PR makes newly started subagent work durable in saved parent sessions. Before a child begins provider work, Diffex now saves enough information to find that child and understand how it was configured after a restart. Later status and history updates are also recorded, while in-memory and unsaved sessions continue to behave as temporary sessions.
Reasoning
The root-local factory and existing controller lifecycle are the narrowest ownership boundaries for choosing durable storage and recording state. Requiring the child header and queued roster before spawn acceptance prevents accepted work from becoming undiscoverable after restart. Later transitions remain best effort so a persistence failure does not make live controller state untruthful or halt already accepted work; strict admission failures instead restore the prior parent leaf.
Changes
Testing
node ../../node_modules/vitest/dist/cli.js --run test/suite/subagent-persistence.test.ts test/suite/subagent-services.test.ts test/suite/subagent-registration.test.ts test/suite/agent-session-harness-version.test.ts test/session-manager/fork-branch.test.ts test/session-selector-path-delete.test.tsnpm run check