Convos get forked when opening agents after resuming the convo and using left arrow to get to agents.

Status Open
Maintainer reply None cached
Activity 2 comments · opened Sep 28, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I start a conversation. I may or may not rename it. I press the left arrow to track it in agents, then go back into the convo.

Now, any of the following happens: computer crashes, computer updates and restarts; my terminal crashes; my terminal updates and restarts

So I want to continue my conversation.
I use claude —resume <guid> or claude —resume “my custom name” to resume the convo.

When I click the left arrow to go back to agents, my convo is forked and I now have a duplicate convo and it appears twice in agents.

What Should Happen?

It should recognise that I already have that convo tracked in agents. It’s all one and the same convo. It should only appear once. It should not be forked or duplicated.

Error Messages/Logs

No error log. Just duplicated convo. Freaking annoying.

Steps to Reproduce

Start a Claude convo in the terminal.
Optionally name it.
Click left to get to agents.

Either close and reopen the terminal app, or restart your computer and open the terminal app.

Resume the conversation either using the guid or custom name.
Click left to get to agents.

You now have a forked conversation and two entries in the agents list.

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

All the versions

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

if I wanted the convo forked I would explicitly fork it.
This is implicit fork behavior.
If there is a reason for this behavior, I would suggest asking the user if they want to fork or continue using the same convo.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗