Chat History Search & Branching Conversations

Feature Requests
1

Hey Cursor team,

I’ve got a couple of ideas that I think could make the chat experience in Cursor even better:

  1. Cross-Chat History Search
    It would be super handy if chats could search through other chats to reference past info without having to copy and paste. This would make it way easier to keep track of conversations across different topics without repeating the same questions or instructions.
  2. Branching Conversations with Selective History Inheritance
    It would be awesome to have branching conversations. If I start a new branch from an existing chat, the new branch should inherit the history of the parent chat — but anything in the branch would stay separate from the original chat. This way, I could explore different ideas without messing up the main thread or losing context.It would be great if there were options to:
  • Choose whether the branch gets all the history or just part of it.
  • Decide if the branch should be able to search through parent chat history dynamically or just inherit a snapshot.

These features would make Cursor feel more like a collaborative workspace, especially for experimenting with multiple ideas at the same time. It would make it easier to try out different solutions without losing track of how each one evolved.

Looking forward to hearing your thoughts!

2 Likes
2

I would really like to have branching conversations. Let me pick any point in the conversation and fork it out into a new chat.

I find that I often have a really good context built, with the agent being very productive, and I have to go down a bit of a rabbit hole to fix a bug or look into an edge case. When I’m finished with that rabbit hole, the context is often ruined - the agent is confused because it has too much in context. I really want to be able to go back to the point right before I started down the rabbit hole in order to retain the high-quality context I was working in. Additionally, the added context of the rabbit hole is usually not relevant to the main thread I’m working on.

I suggest adding a fork button on each agent message (next to “restore checkpoint” and “copy message”). This will create a new chat, with an exact copy of the chat context up to that point. This would allow me to branch any chat or agent session as needed.

1 Like