How do I open the current project in Claude Desktop with `claude --desktop`?

Q: What’s the difference between /desktop and claude --desktop?

/desktop moves an active CLI session into Desktop and exits the CLI. claude --desktop opens Desktop from the shell without starting a terminal session.

Q: Is this the same as Claude Code Channels?

No. Tag “Channels Claude can search” and MCP --channels are different products — see Channels Spec.

Q: Does HEAD 2.1.286 change --desktop?

The feature landed in 2.1.285. HEAD 2.1.286 is additive elsewhere; it does not redefine this flag (checked 2026-10-01).

From Claude Code CLI v2.1.285+, `claude --desktop` opens the Claude desktop app on your current directory (or with `--continue` / `--resume` on an existing session). Requirements, `/desktop` vs shell flag, and fences vs full Desktop docs and the Channels Spec.

Run claude --desktop from a project folder (Claude Code ≥2.1.285) to open Claude Desktop on that directory without starting a terminal session. Add --continue for the latest conversation in the folder, or --resume <session-id> (ID from /status — not a session name). In an active CLI session, /desktop saves and moves that session into Desktop. Needs macOS or x64 Windows and a Claude subscription sign-in — not API-key / Bedrock / Agent Platform / Foundry. This Spec is the CLI→Desktop bridge — not a full Desktop tour, and not the Claude Tag Channels Spec (Channels).

TL;DR: claude --desktop opens Desktop on cwd; --continue / --resume <id> attach an existing conversation; /desktop moves an active CLI session. Version floor 2.1.285+. Labs claude code desktop 8100 / KD 50 is mostly navigational toward Desktop as a product — fence that intent. Checked 2026-10-01.

What `claude --desktop` does

CHANGELOG 2.1.285 (anthropics/claude-code):

Added claude --desktop to open the Claude desktop app on the current directory, or on a session with --continue / --resume <id>

Same-day docs (Desktop application · “Coming from the CLI?”): with no other args, the flag opens Desktop on the current directory. Claude Code prints Opening session in Claude Desktop, the session opens in the app, and the command exits. If Claude Desktop isn’t installed, the command prints a download link and exits (claude.com/download).

Version floor: Claude Code v2.1.285 or later. CHANGELOG HEAD on 2026-10-01 is 2.1.286 (additive UX/fixes elsewhere — bookmarks, Tag spend Add-channel, etc.). It does not redefine --desktop; this Spec stays on the 2.1.285 landing.

`--desktop` vs `/desktop`

Entry	When to use	Session behavior
`claude --desktop`	From the shell	Opens Desktop on cwd without starting a terminal session
`/desktop`	Inside a running CLI session	Saves the session, opens it in Desktop, exits the CLI
`claude --desktop --continue`	From the shell	Most recent conversation in this directory
`claude --desktop --resume <session-id>`	From the shell	Session ID from `/status` (session name does not work)

Shared requirements (official docs): available on macOS and x64 Windows when signed in with a Claude subscription. Not available with API key authentication or on Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry.

claude --desktop
claude --desktop --continue
claude --desktop --resume <session-id>

Continue and resume

--continue → most recent conversation in this directory.
--resume <session-id> → ID from /status. A session name is not accepted.
Claude Code does not move a session that is open in another terminal or still running in the background.
Soft note: inside Desktop (local sessions only — not SSH/WSL/cloud), /resume can pick up a CLI-started session. No invented Desktop admin click-paths beyond that.

Not these “Desktop / Channels”

Thing	Role	Where
Full Claude Desktop product	Code tab panes, computer use, Dispatch, etc.	Soft context only — desktop · desktop-quickstart · download
Claude Tag “Channels Claude can search”	Slack search admin	Channels Spec
MCP `claude --channels`	Push events into a local session	Different product — not this page
Permissions / auto mode / memory / doctor	Other Specs	Live bridges below

Do not invent Linux support for this CLI→Desktop bridge: official “Coming from the CLI?” lists macOS and x64 Windows for /desktop and --desktop. [GAP] — do not claim Linux bridge support without docs.

Pitfalls

Expecting API-key or Bedrock / Agent Platform / Foundry support for /desktop / --desktop
Using a session name with --resume instead of the ID from /status
Trying to move a still-running or other-terminal session
Treating Labs claude code desktop (8100 / KD 50) as a full Desktop marketing-page brief
Inventing Desktop Settings click-paths not in official docs for this flag

Related Specs: permissions · stop auto mode · memory · doctor prompt-audit.

FAQ

Do I need Desktop installed first?

Yes — or follow the download link the command prints when the app is missing (claude.com/download).

What’s the difference between `/desktop` and `claude --desktop`?

/desktop moves an active CLI session into Desktop and exits the CLI. claude --desktop opens Desktop from the shell without starting a terminal session.

Can I use this on Bedrock / with an API key?

No. Official docs: Claude subscription sign-in only — not API key, Bedrock, Agent Platform, or Foundry.

Is this the same as Claude Code Channels?

No. Tag “Channels Claude can search” and MCP --channels are different products — see Channels Spec.

Does HEAD 2.1.286 change `--desktop`?

The feature landed in 2.1.285. HEAD 2.1.286 is additive elsewhere; it does not redefine this flag (checked 2026-10-01).

Sources

CHANGELOG 2.1.285 claude --desktop bullet · HEAD 2.1.286 noted — raw CHANGELOG (2026-10-01)
Desktop application — “Coming from the CLI?” (--desktop, /desktop, continue/resume, platform/auth)
Desktop quickstart — soft install context
claude.com/download — when the app is missing
Labs: claude code desktop 8100 / KD 50 — labs-kw-2026-10-01 (intent caution)