[Feature request] Expose --channels flag from Claude Code Desktop app launch (UI / config / URL scheme)

Feature request: Expose --channels flag from Claude Code Desktop app launch (UI / config / URL scheme)

Context

Channels (research preview, v2.1.80+) is a powerful feature for two-way phone notifications + Permission Relay (v2.1.81+). The iMessage channel plugin specifically enables Apple Watch / iPhone to approve Bash etc. via "yes <code>" replies while the user is away from their Mac.

However: the Channels feature is currently only accessible from Terminal launch (claude --channels plugin:imessage@claude-plugins-official), and is not exposed in the Claude Code Desktop app on Mac in any documented way.

What we tried (all dead ends)

• GUI Settings: No channels toggle / config field in Settings/Preferences pane (verified Desktop app v1.7196.0)
• Config files: ~/Library/Application Support/Claude/config.json and claude_desktop_config.json have no channels key documented
• CLI env var: No CLAUDE_CHANNELS env var read by the Desktop app at session spawn
• URL scheme: Verified claude:// exposes only claude.ai/new / code/new / cowork/new with q/prompt/folder/file params, no channels
• In-session slash command: No runtime enable command exists (e.g. /channels enable plugin:...)
• MCP-only bypass: Verified per channels.md verbatim — "Being in .mcp.json isn't enough to push messages: a server also has to be named in --channels." MCP tools work, but Permission Relay doesn't.
• /desktop handoff: Hits transcript-not-found bug (separate issue, see filed companion). Even if fixed, the CLI launch step is a barrier.

Related closed-as-duplicate issues

• #53218 — Desktop CLI flag passthrough, CLOSED dup of #52743
• #52743 — --desktop CLI flag, CLOSED dup of #50345
• #50345 — Original feature request, CLOSED no resolution
• #58211 (OPEN) — Same architectural gap for Telegram channel
• #46742 (OPEN) — Custom channel plugin allowlist
• #51845 (OPEN) — --channels matching broken even when correct

Why this matters

Many Desktop-app users (myself included) cannot switch entirely to Terminal launching because:

1. Conversations tab does not show Terminal-launched session history (Issue #56038 / #61967)
2. Many Desktop-app UX features (Cowork, integrated terminal, etc.) are not available in pure CLI
3. Users want the convenience of Desktop launch and the Channels feature

I have personally verified the iMessage channel works fully end-to-end (outbound, inbound free-text, Permission Relay with iPhone/Apple Watch yes/no replies) when launched from Terminal. The only blocker is that this can't be combined with Desktop-app convenience.

Proposed solutions (any one would unblock)

1. Settings UI: Channels list in Settings/Preferences, with marketplace plugin discovery and per-plugin enable toggle
2. Config file: Documented channels array key in claude_desktop_config.json that's passed to spawned sessions
3. URL scheme parameter: claude://code/new?folder=...&channels=plugin:imessage@claude-plugins-official
4. Env var: CLAUDE_CHANNELS=plugin:imessage@claude-plugins-official honored by Desktop-app-spawned sessions
5. Slash command runtime enable: /channels add plugin:imessage@claude-plugins-official followed by session reload — provided plugins MCP server can be hot-attached

Any one of these would close the gap. Given the closed-as-duplicate chain on this feature, would appreciate any Anthropic staff guidance on whether a path is on the roadmap.

Companion bugs filed

• /desktop handoff transcript-not-found bug (separate issue)
• iMessage plugin self-chat detection incomplete on email-only account rows (separate issue)