iOS Dispatch sessions from mobile fail to spawn reliably

Summary

Dispatch sessions started from the Claude iOS app (mobile) are consistently unreliable. Sessions frequently fail to spawn on the desktop, never report back, or never appear in the Desktop Code tab. This has been the experience since the feature shipped, not a recent regression.

Environment

• Claude iOS app, latest version
• Claude Desktop on Windows
• Dispatch into multiple local repos (varies by attempt)

Observed

• Trigger Dispatch from iOS with a coding task
• Sometimes the session spawns on Desktop, sometimes it does not
• When it does not spawn, there is no clear error on either side
• When it does spawn, output can stop mid-run with no notification
• The "remote coding from phone" workflow is effectively non-functional for any real work

Expected

• Reliable spawn of a Code session on Desktop for every Dispatch trigger
• Clear, surfaced error when spawn fails (network, desktop offline, auth, queue, etc.)
• Status visible from iOS so the user knows whether Dispatch is in flight or stalled

Impact

The "code from your phone" promise of Dispatch does not survive day-to-day use. Users abandon the feature after a few failed attempts.

Ask

• Investigate spawn reliability between iOS and Desktop
• Surface concrete error states when spawn fails
• Add observability so the user can see whether a Dispatch is queued, spawning, running, or dead