Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] `claude://` deeplink skips specified files when Claude Desktop is not already opened on macOS [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56261•Fetched 2026-05-06 06:32:52
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
StrusStrus
Participants
StrusStrus
Timeline (top)
labeled ×5

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Running claude://cowork/new?file=<file_path> when Claude Desktop app is not running only opens Claude Desktop but does not add the specified file/files to context.

What Should Happen?

Specified file/files should be added to context in a new session after Claude Desktop app starts.

Error Messages/Logs

Steps to Reproduce

  1. Make sure Claude Desktop app is not running.
  2. Launch open claude://cowork/new?file=<file_path> in the terminal (replace <file_path> with an absolute path to a file)

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.5354.0 (9a9e9d) Claude Desktop

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

The issue can be potentially resolved by modifying the claude://cowork/new?file=<file_path> launch command to properly handle the case when the Claude Desktop app is not running.

Guidance

  • Verify that the claude:// protocol is correctly registered and associated with the Claude Desktop app on the macOS system.
  • Check the Claude Desktop app's documentation to see if there are any specific requirements or limitations for launching the app with a file path parameter.
  • Test the launch command with a different file path to ensure the issue is not specific to a particular file or directory.
  • Consider adding additional logging or debugging statements to the launch command to capture more information about the issue.

Notes

The issue may be related to the way the claude:// protocol is handled by the operating system or the Claude Desktop app, and further investigation may be needed to determine the root cause.

Recommendation

Apply workaround: Modify the launch command to use a different approach, such as using a script to start the Claude Desktop app and then add the file to context, until a more permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] `claude://` deeplink skips specified files when Claude Desktop is not already opened on macOS [1 participants]