Repository navigation
feat(web): retain finished subagents across hydration - #922
Conversation
📝 WalkthroughWalkthroughTool-call lifecycle timestamps are now persisted during narrative storage. The web Subagents roster reconciles live calls with hydrated records into active and finished rows, renders terminal statuses, and remembers the selected roster tab independently for each thread. ChangesSubagent lifecycle and roster
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Keep settled delegated work inspectable in the Subagents panel after completion, thread switching, and hydration.
Why
Finished subagents disappeared when volatile narrative state settled. This completes the second tracer-bullet slice of #916 and unblocks #919.
Key Changes
Verification
bun run verify: passed all typecheck, lint, unit-test, and agent-script gates.Visual Evidence
Active roster before settlement:
Finished roster after settlement:
Thread isolation with an empty Finished roster:
Hydrated restoration after a full reload:
Closes #918