Currently in Chat we can go back and modify any request, and it will effectively branch off into a different conversation from there.
It doesn’t seem to be possible in Composer at the moment.
Please consider adding this, as Composer becomes more and more used, this feature would be extremely helpful and it avoids having to start a new Composer flow and losing the context
I like these type of ideas that deal with the dynamic involved in the chat end/transition phase, the ‘branching’ notion is interesting.
It made me think of this post where the user was also thinking of ways to transition from one chat to the next:
So I wonder if such a ‘branching’ feature could include a ‘summarise and transfer context’ feature.
It would be interesting to see if Cursor’s understanding of the important ‘realisation’/‘breakthrough’/‘aha!’ moments in a chat were the same as the users.
Maybe we need an ‘aha!’ button to tag/add/highlight moments such as these in a chat. (Or perhaps we could use canned prompts to achieve the same outcome). Then Cursor would have a better understanding of what was important to us in the chat, which we wanted to persist into the next chat.