claude-code - 💡(How to fix) Fix Dispatch (Claude.ai desktop + iPhone) should surface existing local Claude Code sessions [1 comments, 2 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#57754Fetched 2026-05-11 03:26:18
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Fix Action

Fix / Workaround

The Dispatch feature in the Claude.ai desktop and iPhone apps lets me drive my computer remotely from my phone, but it has no awareness of my existing local Claude Code sessions.

  • Dispatch (iPhone + desktop) shows only sessions spawned from within Dispatch itself — in my case, a single long-running session.
  • My local Claude Code sessions — both CLI-launched (claude in terminal) and desktop-app-launched — are completely invisible from Dispatch.
  • Those local sessions number in the thousands, all stored at ~/.claude/projects/<encoded-cwd>/<uuid>.jsonl, and the CLI's claude --resume picker (with Ctrl+A) can list both kinds without issue.

From Dispatch on my iPhone I'd like to either:

  1. See and resume any existing local Claude Code session (CLI or desktop), or
  2. At minimum, send a prompt into a specific local session by ID/name.
RAW_BUFFERClick to expand / collapse

Feature request

The Dispatch feature in the Claude.ai desktop and iPhone apps lets me drive my computer remotely from my phone, but it has no awareness of my existing local Claude Code sessions.

Current behavior

  • Dispatch (iPhone + desktop) shows only sessions spawned from within Dispatch itself — in my case, a single long-running session.
  • My local Claude Code sessions — both CLI-launched (claude in terminal) and desktop-app-launched — are completely invisible from Dispatch.
  • Those local sessions number in the thousands, all stored at ~/.claude/projects/<encoded-cwd>/<uuid>.jsonl, and the CLI's claude --resume picker (with Ctrl+A) can list both kinds without issue.

Expected behavior

From Dispatch on my iPhone I'd like to either:

  1. See and resume any existing local Claude Code session (CLI or desktop), or
  2. At minimum, send a prompt into a specific local session by ID/name.

Use case: I'm away from my Mac and want to check in on or continue a specific in-flight session. Today the only path is "start a new Dispatch session," which can't see the work already running.

Related

  • #57345 — Desktop app sidebar filters out CLI sessions; same family of cross-product session-visibility gap. The fix there (treat ~/.claude/projects/ as the unified store) would presumably extend here.

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…

FAQ

Expected behavior

From Dispatch on my iPhone I'd like to either:

  1. See and resume any existing local Claude Code session (CLI or desktop), or
  2. At minimum, send a prompt into a specific local session by ID/name.

Use case: I'm away from my Mac and want to check in on or continue a specific in-flight session. Today the only path is "start a new Dispatch session," which can't see the work already running.

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 Dispatch (Claude.ai desktop + iPhone) should surface existing local Claude Code sessions [1 comments, 2 participants]