[BUG] Claude Dispatch permanently showing "desktop appears offline" for multiple weeks

having same issue on claude desktop 'windows'

<img width="780" height="257" alt="Image" src="https://github.com/user-attachments/assets/545a41eb-0051-4263-b66a-c06f8300cb34" />

having this issue too!

Same here

For anyone landing here with the same "Desktop appears offline" symptom: I just filed #53266 with a root-cause investigation that may overlap with this thread. On my account the failure is a hard-coded 10 s timeout in the desktop's [transport:sdk] adapter (POST /worker/register, functions hqr / vVr in the bundled app.asar), which is exceeded whenever the SDK bootstrap takes longer than 10 s — and on power-user setups with many CLI-installed Code plugins + the bundled official skills, it routinely takes 20–90 s.

If you can grep your ~/Library/Logs/Claude/main.log for transport:sdk and you see timeout of 10000ms exceeded retrying every ~10 s, you're hitting the same root cause as #53266. If your logs show a different signature (server-side 503/404, environment ghosting, etc.) it's likely a different root cause and #45937 / #48754 / #49545 capture that better.

+1

Cowork tasks execute normally, but the main Dispatch thread reports desktop offline.

This happens consistently with all steps like update and reinstall not working

Only solve I have been able to experience to fix this is to run the install boot up program again to connect like initial set up, but I cannot locate this once it's been configured or logged in. This should be an option to be able to run from a prompt inside the system until this can be fixed.

fix this pls, so annoying

Claude Code version: 2.1.116
OS: Windows
Plan: (fill in your plan tier)
Date observed: 2026-04-28

Cowork Dispatch shows "Desktop appears offline. Will run when it reconnects" indefinitely. When the bridge briefly connects, message send fails with "Message couldn't be sent. You can try again." Regular Cowork tasks (non-Dispatch) work normally.
Steps to reproduce:

Open Claude desktop app, sign in
Navigate to Dispatch (Beta)
Send any message (e.g., "test")
Receive "Desktop appears offline" response

Verified troubleshooting completed:

Signed out and back in on desktop and mobile
Started multiple fresh Dispatch threads
Fully quit and restarted desktop app
Deleted %USERPROFILE%.claude\bridge-state.json
Deleted %USERPROFILE%.claude.credentials.json and re-authed
Verified virtualization: HvHost was Stopped, started it; vmcompute running; "Virtualization is not available" banner cleared
Set HvHost startup to Automatic
Uninstalled, Reinstalled
Reboot Computer
Force Close
Change Security Settings on the PC boot screen
Completely disabled VPN
Tested off-VPN on phone hotspot, with and without VPN no change
Tested with NordVPN protocol switched and Threat Protection disabled, no change, tested with VPN tunneling
Verified Cowork settings: Keep awake ON, Computer use enabled, Code permissions set to Bypass

Expected behavior: Dispatch desktop should register as online and process messages.
Actual behavior: Persistent offline status; messages either fail silently or return "Message couldn't be sent."
Related issues: https://github.com/anthropics/claude-code/issues/45962, https://github.com/anthropics/claude-code/issues/49545, https://github.com/anthropics/claude-code/issues/45937
Attachments: screenshots of offline state and Dispatch settings panel

Description:
Dispatch on my iPhone shows the desktop as offline even though Claude Desktop is running and online.

Steps already taken:

Logged out and back in on both devices (desktop first, then mobile)
Toggled Dispatch off → toggled back on
Confirmed bridge-state.json does not exist on my machine
Claude Desktop is running and awake

Environment:

Mac: 26.4.1
Claude Desktop version: 1.5354.0
iPhone iOS version: 26.3.1
Plan: Max

+1 on macOS 26.3 (arm64), Claude Desktop 1.5354.0
codesign confirms missing com.apple.vm.networking entitlement
Renderer feature flags show "operon": {"status": "unavailable"}
Cowork local works, Dispatch permanently offline

having same issue on claude desktop 'windows'

<img width="670" height="213" alt="Image" src="https://github.com/user-attachments/assets/74442e05-26ee-4180-8648-8a30fc8cf2a5" />

i delete .claude config and uninstall pc desktop,then reinstall desktop again, solve this problem

Update: in #53266 I posted evidence that Dispatch is now working on my end without any config change (last transport:sdk timeout of 10000ms exceeded failure on 2026-05-02; clean since, with bundled claude-code 2.1.128 + Claude.app 1.6608.0). The 10 s timeout literal is still in app.asar, so the fix appears to be server-side / bootstrap-decoupling rather than a client-side timeout bump.

If your "Desktop appears offline" happens to share the same root cause, you should also see it resolved on the latest desktop build. If it's still broken for you and the log signature is different (server-side 503/404, ghost env, etc.), this is likely a different bug and the discussion in this thread / #48754 still applies.

Same issue here, adding a data point.

Environment

• OS: Windows 11 Pro
• Plan: Pro
• Product: Claude Desktop → Cowork → Dispatch (Beta)

Symptom
Dispatch messages are marked "Read" on both desktop and mobile, but Claude never delivers a response on either device. Initially showed "Desktop appears offline / Asleep"; after re-pairing the offline status cleared and messages now show "Read," but replies still never appear. Matches #54378, #45937, #40178, #49545.

Key diagnostic (rules out local/VM)
Regular non-Dispatch Cowork tasks work perfectly — I asked Claude to list my desktop files and it executed via computer use and returned the correct result. So the VM and execution layer are healthy; only the Dispatch persistent thread is dead.

Already tried (none resolved it):

• Restarted CoworkVMService via PowerShell
• Deleted %USERPROFILE%\\.claude\\bridge-state.json and restarted
• Verified services Running: CoworkVMService (Automatic), HvHost (Automatic), vmcompute (Manual)
• Verified Microsoft-Hyper-V-All = Enabled
• Re-paired phone + desktop (sign out/in both, desktop first)
• Deleted the Dispatch conversation to force a fresh thread
• Confirmed Keep awake ON, Mobile notifications ON, Computer use enabled

This points to a stuck server-side Dispatch relay/session, not a local config problem. A backend session reset seems to be the only thing that could fix it. Happy to provide logs or version numbers.

Closing for now — inactive for too long. Please open a new issue if this is still relevant.