claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

[BUG] "Open in CLI" feature isn't working as intended

Open welshofer opened this issue 4 months ago • 2 comments

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?

Environment

  • iPhone 17 Pro Max - iOS 26.2
  • macOS Tahoe 26.1 MacBook Pro 16-inch M4 Max

Steps to Reproduce

  1. Started session on Claude (Code) iPhone client
  2. Opened Claude for macOS, switched to Code tab. Continued session.
  3. Clicked on "Open in CLI".
  4. Command copied to clipboard
  5. Pasted command in terminal.
  6. Resulting Error: "Failed to fetch session metadata"

Attempted multiple times. Session ID verified.

What Should Happen?

Session continues in CLI

Error Messages/Logs


Steps to Reproduce

Steps to Reproduce

  1. Started session on Claude (Code) iPhone client
  2. Opened Claude for macOS, switched to Code tab. Continued session.
  3. Clicked on "Open in CLI".
  4. Command copied to clipboard
  5. Pasted command in terminal.
  6. Resulting Error: "Failed to fetch session metadata"

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.0.68 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

welshofer avatar Dec 13 '25 00:12 welshofer

I'm also having issues with "Open in CLI" feature. For me, the "Open In CLI" is just disabled (both in web and desktop app, tried different sessions). There are no indicators of why it's disabled.

joshling1919 avatar Dec 16 '25 14:12 joshling1919

I'm also having issues with "Open in CLI" feature. For me, the "Open In CLI" is just disabled (both in web and desktop app, tried different sessions). There are no indicators of why it's disabled.

@joshling1919 Seeing the same issue, I believe until the agent has pushed changes to the branch you can't use "Open in CLI". Makes sense for this to be the case when files have been written but not committed, but doesn't make sense for this to be disabled if no files have been written yet. Some sort of tooltip for why it's disabled would help a lot here.

sohil-kshirsagar avatar Jan 07 '26 22:01 sohil-kshirsagar