[BUG] Dispatch stuck on "Asleep" despite desktop awake and Desktop app open (Windows 11)

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 mobile app shows my desktop as "Asleep" even though the machine is awake, online, and the Claude Desktop app is open with Cowork/Dispatch visible. The status never recovers, so I cannot send tasks from mobile. In some states the mobile Send button is also non-functional.

What Should Happen?

When the desktop is awake and the Desktop app is open, mobile Dispatch should show the desktop as online and accept tasks. If pairing is broken, clearing local state should return desktop Dispatch to the "Get started" / QR pairing screen so the devices can re-pair.

Error Messages/Logs

Mobile Dispatch shows "Asleep" persistently, regardless of desktop state.
Desktop is confirmed awake with Dispatch open in Cowork.
Desktop Dispatch never resets to the QR / "Get started" pairing screen, so re-pairing is not possible from the client.

Steps to Reproduce

Confirmed desktop is awake and online.
Confirmed Claude Desktop is open with Dispatch visible in Cowork.
Pull-to-refresh on the mobile Dispatch screen.
Fully quit Claude Desktop from the system tray (not just closing the window) and relaunched.
Confirmed both apps are on the latest version.
Confirmed "keep awake" / prevent-sleep toggle is on.
Logged out of both desktop and mobile, then back in (desktop first, then mobile).
Deleted the Dispatch conversation via the three-dot menu.
Deleted bridge-state.json at %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude and relaunched. Desktop Dispatch still did not return to the QR pairing screen.

Local troubleshooting, including deleting bridge-state.json, does not clear the state, and desktop Dispatch never returns to the QR pairing screen. That points to pairing/relay state held server-side that the client cannot reset. This is consistent with other reports (#44225, #45937, #51389, #58097, #67682, #70471).

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.19367.0 (1a5be1)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Local troubleshooting, including deleting bridge-state.json, does not clear the state, and desktop Dispatch never returns to the QR pairing screen. That points to pairing/relay state held server-side that the client cannot reset. This is consistent with other reports (#44225, #45937, #51389, #58097, #67682, #70471).