[BUG] Dispatch stuck on "Asleep" / "Can't reach your desktop" — all local troubleshooting exhausted

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Dispatch on the Claude iOS app shows the computer as "Asleep" / offline despite the desktop being awake, Claude Desktop running, and all troubleshooting steps completed. The issue persists and appears to be server-side.

Environment:

• macOS, MacBook Pro
• Claude Desktop: latest version
• Claude iOS app: latest version
• Plan: Pro

Steps Already Taken (all failed):

• Confirmed Mac is awake and online
• Claude Desktop app is open with Cowork visible
• Force quit (Cmd+Q) and restarted Claude Desktop
• Restarted Mac
• Force closed and reopened iOS app
• Logged out and back in on both devices
• Checked that ~/.claude/bridge-state.json does not exist (file is absent, ruling out local state corruption)
• Toggled keep-awake and file access in Dispatch settings

What Should Happen?

Dispatch should show the desktop as online and accept tasks from the mobile app.

Error Messages/Logs

Mobile app shows: "Can't reach your desktop. Check that your computer is online and desktop app is open."
Status icon shows: "Asleep"
This persists regardless of desktop state.

Steps to Reproduce

1. Open Claude iOS app
2. Navigate to Dispatch
3. Observe status icon shows "Asleep" / "Can't reach your desktop"
4. Verify Mac is awake, Claude Desktop is open — status still shows offline
5. Force quit and restart Claude Desktop — no change
6. Restart Mac — no change
7. Log out and back in on both devices — no change

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

latest (Claude Desktop app)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Related Issues:

• #44225
• #51389
• #45937
• #46391
• #40958

These issues document the same pattern: pairing/session state stuck server-side after an incident, not resolvable by local troubleshooting.

Request: Backend session/pairing state reset for account camzenger@gmail.com (Pro plan).