/branch command replaces original conversation instead of keeping both
Resolved 💬 2 comments Opened Mar 24, 2026 by dr-ayush Closed Apr 21, 2026
Description
When using the /branch command on an existing conversation, the original conversation disappears from the session resume list and only the new branch appears. The expected behavior is that both the original conversation and the new branch should be listed.
Steps to Reproduce
- Have an existing conversation (e.g., named "main blog s3 agent")
- Run
/branchwithin that conversation - A new branch is created (e.g., "main blog s3 agent (git pr review) (Branch)")
- Go back to the session resume list
Expected Behavior
Both conversations should appear in the resume list:
- "main blog s3 agent" (original)
- "main blog s3 agent (git pr review) (Branch)" (the new branch)
Actual Behavior
Only the branch appears:
- "main blog s3 agent (git pr review) (Branch)"
The original "main blog s3 agent" conversation is no longer listed and cannot be resumed.
Environment
- OS: macOS (Darwin 25.3.0)
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗