What is the exact message?
Error: Couldn't open Claude Desktop (`open` exited 1: LSOpenURLsWithRole() failed for the URL claude://resume?session=<session-id> with error -10814). Open Claude Desktop and try again.The brackets are the useful part. They name the command that failed, its exit status, and the first line of its error output when it produced one. On Windows the same line names rundll32 where this one names open, and everything else — the wording, the link, the fix — is identical.
What does it mean?
Claude Code does not open Claude Desktop itself. It hands the job to the operating system, with a claude://resume?session=… link, and this message means that hand-off failed.
You reach it from inside a session with /desktop or its alias /app, or from your shell with claude --desktop. The two behave differently afterwards: after /desktop the session stays in the terminal, while claude --desktop prints the message without the Error: prefix and exits with status 1.
What causes it
- The system command that opens apps failed. The brackets carry its exit status and the first line of its own error, which is why the text reads like a system message rather than a Claude Code one.
- The link is specific to an app. Claude Code asks the system to open a
claude://resume?session=…URL, so the system has to know which application answers that link. - It is not the missing-app case. Anthropic documents that when Claude Desktop is not installed, the command prints a download link and exits instead — so if you see this message, the app and the command were found.
The example above is from macOS, where the command is open. On Windows the same failure names rundll32.
How do I fix it?
- Open Claude Desktop yourself, then run
/desktoporclaude --desktopagain. That is Anthropic's first step, and it covers the plainest case: the app was not running, so the system had nothing to answer the link with. - If it still fails, get the full error. Turn on debug logging with
/debugand run/desktopagain, or runclaude --desktop --debug-file <path>, then read the debug log. - Work in the terminal instead if you only need the session. After
/desktopfails, the session is still in your terminal, so nothing is blocked while you sort the app out.
How do I know it is fixed?
- Running
/desktopopens Claude Desktop on the same conversation instead of printing the error. claude --desktop --resume <session-id>printsOpening session <session-id> in Claude Desktop, and the command exits.- Your terminal is back to a prompt box, with the session it carried still there.
Where these answers come from
- The message, the commands it comes from, the macOS and Windows commands, both fixes and the older wording: Anthropic's error reference, read November 18, 2026.
- Coming to the desktop app from the CLI: Anthropic's desktop app page, read November 18, 2026.
--desktopand--debug-fileflags: Anthropic's CLI reference, read November 18, 2026.
Common questions
What is the command named in brackets?
The system command Claude Code used to open the app, with its exit status and the first line of its error output. Anthropic documents open on macOS and rundll32 on Windows.
Did my session close?
No. After /desktop the session stays in the terminal. claude --desktop prints the message without the Error: prefix and exits with status 1.
How do I get the full error from the failed command?
Turn on debug logging with /debug and run /desktop again, or run claude --desktop --debug-file with a path, then read the debug log.
What did the older wording look like?
Before v2.1.285 the message ended Open Claude Desktop and run /desktop again. Before v2.1.275 it read Failed to open Claude Desktop. Please try opening it manually. and did not say what failed.