Having fork of the main agent as subagent

[Avigad_Shmuel]

Feature request for product/service

– Other –

Describe the request

It can be (sometimes) very convenient to have the option to use fork of your main agent as subagent, so it will have all context of the mission already in it.
The main use case i can think of is when a task need all knowledge of the conversation but we don’t want to get our context dirty with this specific task.

[Colin]

Hey @Avigad_Shmuel!

Thanks for the suggestion. Just want to check that you’re aware that you can already fork a chat in Cursor.

This would not spawn a subagent, but it would allow you to continue a conversation with all the existing context.

Are you mostly looking at this to ask quick questions to the agent without polluting the agent (having a “sidecar”), or something else?