My typical workflow right now includes spinning an agent to get informed on a topic, then splitting the chat to a coordinator and implementor, with the coordinator helping me manage artifact files / instructions and create prompts, while I paste the prompts into the implementor so it does not lose any nuance with the current context. I currently have to do this manually as I do not know how to get an agent to continuously refer to the same agent without starting with a new context every time.
The specific thing you’re picturing, wiring one existing chat into another so it keeps driving the same subagent across chats, isn’t possible today. Subagents start with a clean context and belong to the one chat that launched them, so a second chat can’t take over the same session. You can still get most of that coordinator/implementor flow without the manual pasting:
Fork Chat (the ... menu on a message): branch your research chat into an implementation chat. The fork keeps all context up to that point with its own history, so you split off the build without re-priming or cluttering the original.
@ Past Chats: pull a previous conversation into a new chat as context instead of copy-pasting prompts.
Custom agents: define reusable “coordinator” and “implementor” personas as markdown files in .cursor/agents/ (this project) or ~/.cursor/agents/ (all projects). They show up in the / menu and your main agent can delegate to them by name. See the subagents docs.
AGENTS.md / rules: keep shared standing instructions there so both agents follow them automatically, no re-explaining each turn.
One heads up: a subagent your agent spawns starts fresh each time and doesn’t inherit the chat, so it isn’t a stateful implementor that remembers across turns. The parent seeds it with what it needs.
tho why is it that in some occasions a main agent can trigger an already existing subagents chat to continue a conversation? i cannot recreate it tho sometimes it uses the same chat sometimes creates a new subagent