Feature request for product/service
Chat
Describe the request
It gets very hard to keep track of many chat sessions that were started from different branches (or had their results committed to a branch that I made to store changes after starting the chat from “main”). When switching back to old chats, myself and the agent often get confused when code that is supposed to be there from the chat session is not there.
There should be a way to associate a chat with a branch automatically, based on either where it started from or where the changes the agent made in the session were first committed to. When that association exists, I would love to see in the UI:
- visual element showing what branch the chat is associated with (the same as what we have for remote agents)
- warning / indication that I am not on the branch the session was a part of
- option to continue the chat session in a worktree that is based on the associated branch so that I can follow up on some changes without having to switch my actual checked out branch (even though the chat began as a local chat)
- keep track of whether a branch associated with a chat has been merged and automatically archive the chat (or have a separate category like “merged” for these) (would also like to see this for remote agent sessions)