[BUG] unable to connect desktop and app via Cowork - Dispatch

[vj2377]

Preflight Checklist

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

What's Wrong?

issue #45937 and #51389
Windows desktop, Claude mobile app
• Same account (vlad.jotic@gmail.com) on both devices
• Same Wi-Fi network
• Fresh reinstall done
• Keep-awake enabled
• No QR code or “Get Started” option appearing in Dispatch
• Phone shows “Asleep / Can’t reach your desktop”

What Should Happen?

Anthropic to force-reset the Dispatch pairing state server-side

Error Messages/Logs

No QR code or “Get Started” option appearing in Dispatch

Phone shows “Asleep / Can’t reach your desktop”

Steps to Reproduce

Anthropic to force-reset the Dispatch pairing state server-side

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Claude for Windows 1.5354.0 9a9e3d

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Dispatch stuck "asleep" / "can't reach your desktop" since April 15 outage, Max plan #51389
2. Dispatch main conversation permanently offline despite working Cowork tasks #45937
3. [BUG] Cowork Dispatch persistently shows "Desktop appears offline" on Windows despite verified bridge and virtualization #54378

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

Closing for now — this doesn't appear to be about Claude Code. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.