[BUG] Dispatch shows desktop "Asleep"/offline then hangs indefinitely on a fresh thread, despite healthy local setup (macOS, Max)

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 shows the desktop as "Asleep" / "Desktop appears offline. Will run when it reconnects" on both desktop and mobile, despite a fully healthy local setup. Starting a fresh Dispatch thread changed the failure mode: the new thread accepts the message and shows the typing/thinking indicator, but then spins indefinitely with no response ever landing. Regular (non-Dispatch) Cowork tasks work normally.

Local state verified (all healthy):

• Desktop app open and actively in use (typing in it live)
• Laptop restarted — not actually asleep
• Mobile app restarted
• Claude Code CLI v2.1.161 running and authenticated (greets by name, correct Max org)
• Regular Cowork tasks work normally
• No active incident on the Claude status page
• Keep awake: ON, Computer use: enabled

Troubleshooting already done (none fixed it):

• Restarted laptop
• Restarted mobile app
• Started and authenticated the CLI in a terminal
• Started a fresh Dispatch thread (changed offline → spinning/hang)

This appears to match #46093 (Dispatch hangs on send then shows desktop offline) and the backend pairing/session issues in #45937, #49545, and #52367, where a per-account/per-conversation Dispatch pairing state gets stuck server-side and no client-side step recovers it.

Request: please force-reset / re-initialize my account's Dispatch pairing/session state server-side, since there is no user-facing toggle to trigger re-pairing and all local troubleshooting has been exhausted.

What Should Happen?

Dispatch should recognize the active desktop as online and run the dispatched task. The desktop should not show as "Asleep"/offline while the app is open and the CLI is authenticated, and a sent message should produce a response rather than spinning indefinitely.

Error Messages/Logs

Desktop (main thread): "Desktop appears offline. Will run when it reconnects."
Mobile: desktop shown as "Asleep" — "Can't reach your desktop. Check that your computer is online and desktop app is open."
Fresh thread: message accepted, typing indicator shows, then spins indefinitely with no response.
No console error or stack trace surfaced.

Steps to Reproduce

1. Open the Claude Desktop app and sign in (macOS).
2. Confirm the Claude Code CLI is running and authenticated in a terminal.
3. Go to the Dispatch tab.
4. Send any message (e.g. "test").
5. Observe: desktop returns "Desktop appears offline. Will run when it reconnects"; mobile shows the desktop as "Asleep" with "Can't reach your desktop."
6. Start a new Dispatch thread and send a message.
7. Observe: the message is accepted and a typing/thinking indicator appears, but it spins indefinitely with no response.
8. Open a regular (non-Dispatch) Cowork task and send a message — it works normally.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.161 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_