# Can I get an agent to start using another existing conversation as a basis for a subagent (and follow up with the same subagent)?

**URL:** <https://forum.cursor.com/t/can-i-get-an-agent-to-start-using-another-existing-conversation-as-a-basis-for-a-subagent-and-follow-up-with-the-same-subagent/165233>\
**Category:** Help\
**Tags:** context, subagents\
**Created:** [July 9, 2026, 3:01am UTC](https://forum.cursor.com/t/can-i-get-an-agent-to-start-using-another-existing-conversation-as-a-basis-for-a-subagent-and-follow-up-with-the-same-subagent/165233 "2026-07-09T03:01:13Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [July 9, 2026, 8:37am UTC](https://forum.cursor.com/t/can-i-get-an-agent-to-start-using-another-existing-conversation-as-a-basis-for-a-subagent-and-follow-up-with-the-same-subagent/165233/6 "2026-07-09T08:37:06Z")

</div>

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:

1. 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.
2. @ Past Chats: pull a previous conversation into a new chat as context instead of copy-pasting prompts.
3. 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](https://cursor.com/docs/context/subagents).
4. 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.

The “use another existing chat as the basis and keep following up with it” piece is a genuine gap. Two open requests capture it if you’d like to add your vote: [Having fork of the main agent as subagent](https://forum.cursor.com/t/162694) and [Agent-spawned side sessions](https://forum.cursor.com/t/163000).

---

_[View the full topic](https://forum.cursor.com/t/can-i-get-an-agent-to-start-using-another-existing-conversation-as-a-basis-for-a-subagent-and-follow-up-with-the-same-subagent/165233)._