Agent chat as a tree instead of Linear

Feature request for product/service

Chat

Describe the request

When using Cursor chat during development, the conversation often branches to several “sub-conversation” dealing with issues that are eventually resolved, leading back to the main conversation.
The linear structure of the chat window means that
a. The context often contains a lot of information which is no longer relevant to the conversation.
b. The user often has to scroll back up throguh many sub-conversations to pick up where they left off

It could be ver useful if the chat window could support a tree structure where you can choose to branch out into sub conversations that could be minimized or closed when needed, and have them also cleared from the context

Hey, thanks for the detailed request!

Cursor currently has a “Duplicate Chat” feature that partially solves this. It lets you fork a conversation from any point:

How to use it:

  1. Find the message you want to branch from
  2. Click the three dots on that message
  3. Select “Duplicate Chat”

Each fork keeps the context up to that point and has its own separate history. This lets you try different directions without losing the main conversation.