Currently there’s basically a “runway” where I make great progress with cursor, until the context gets too large, and then the wheels fall off.
Often I want to ask a clarifying question or explore a sidepath, but I have to balance the “cost” of increasing my context window. What about an option to split the answer into a new chat, so it doesn’t clutter up our main context and use up our runway?
We get the best of both worlds - an answer using all our current context, and no clutter in our main chat.
4 Likes
I absolutely love this idea. Especially with ADHD being able to branch off of the main path. I think my preferred scenario would be for this to work like the restore function but instead you can backtrack to branch the context up that point to a new chat.
1 Like
I believe this could be solved with a chat branching feature. That also works with a lot more cases
1 Like
I also want this! Currently, after I finish a “side” discussion, I go back to my initial message that started the side discussion and edit it instead of sending a new message.
This will clear out all the messages after that point. Make sure to click “keep current changes” if prompted if you only want to clear the chat history.
However, this comes with the caveat that you can no longer access that side chat discussion.
Platforms like ChatGPT solve this nicely, when you edit a message it will show arrows underneath that message so you can go between different chat edit branches and still access all the discussions.
1 Like
So glad to hear I’m not the only one in this boat - and you explained it perfectly.
ChatGPT and those websites does in some way solve it, but I think it could be way better. It’s impossible at scale to manage due to complexity. You end up with first message with 5 variants that have another 2 inside, which can have 5, then you go back and fourth and you don’t know where you’re at.
I think it’d be a better approach to select messages (from and to) in the chat, click “create new chat” and you have a whole new chat that you can name. Though honestly, I think this approach is too much for small things (like a quick edit > go back thing).
Offering both approaches will actually be the most valuable because they serve entirely different purposes.
I had the exact same idea a bunch of times while using it - this would be amazing! Sometimes there’s a small side-fix that you want to do but it takes a lot of tokens and by the time you’re done the context is way too long to resume the main task, and you can’t rollback/restore because then you loose all existing work/context about what was added. Branching and perhaps the option to just summarize what happened in the branch when going back to the “main” task would be amazing!
1 Like
Hey, cool idea. In our latest version we have just added the ability to use existing composer conversations as context for new ones, which may get you halfway, but I like the idea of splitting off an answer into a new conversation entirely!
1 Like