Subagents follow their conversation

Makes archiving, restoring, and deleting a conversation reach the subagents it started. They were hidden from navigation but never touched, so an archived or deleted conversation left its subagents active, still running and still holding their provider sessions. Archiving now stops and archives them, unarchiving brings them back, and deleting removes them, through nested subagents and never across a fork, which is a conversation of its own. The archive lists the conversation once rather than once per subagent.

Branch: GitHubfix/subagent-lifecycle-cascade
PR: None…

Comments

This fork

Migrate the uploads manager to the new schema. Rewrite the Convex schema, port the upload tests, and check every call site before we switch.

16:40

Splitting this three ways: one agent rewrites the schema, one ports the tests, and one checks the call sites.

Working

Ask anything...

3Agents

Direct spawns

Rewrite the Convex schemaimplementer3m 40s▸ Editgpt-5.4 · high · 42.3k tok · 17 toolsWorking

Port the upload testsimplementer2m 10s▸ Bashgpt-5.4 · medium · 18.7k tok · 9 toolsWorking

Check the upload call sitesresearcher50sReading uploads/server.tsgpt-5.4 · medium · 5.1k tok · 2 toolsWorking

Rewrite the Convex schemaWorking · 3m 40s
Port the upload testsWorking · 2m 10s
Check the upload call sitesWorking · 50s

3 subagents working for the conversation.

Original