[BUG] Desktop "Open in terminal" says "session resumed" but creates a new session

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?

In the Claude Desktop app, I have an active Claude Code session. When I click the 3-dots menu on the session and select "Open in terminal", it gives me a terminal command. When I run that command, the CLI output says the session was resumed — but it actually creates a brand-new session: a new session appears in the terminal AND a duplicate new session shows up in Claude Desktop, instead of attaching to the original session with its history.

Actual behavior: The CLI claims "session resumed" but a new session is created, visible both in the terminal and as an additional session in Claude Desktop. The original desktop session is not continued.

What Should Happen?

The terminal attaches to the existing desktop session and continues it with full history — no new session is created.

Error Messages/Logs

Steps to Reproduce

1. Start a Claude Code session in the Claude Desktop app
2. Click the 3-dots menu on the session -> "Open in terminal"
3. Copy the generated command and run it in a terminal
4. Observe the CLI message saying the session was resumed

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.215

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Claude Desktop version: Version 1.22209.3 (babe11)

Possibly related issues:

• #55406 (impossible to resume a session after desktop/CLI handoff)
• #10806 (--resume creates new session_id instead of preserving original)