[BUG] Dispatch stuck "asleep" / "can't reach your desktop" since April 15 outage, Max plan

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?

Summary

Claude Dispatch has been non-functional on my mobile device since the Anthropic outage on Wednesday, April 15, 2026 (5 days ago). Dispatch was working normally that morning until approximately 10:00 AM, when the outage began. After Anthropic services came back online, Dispatch never recovered for my account. I am on an active Max plan, emailed support, received an unhelpful response, escalated to a live agent, and have not received a follow-up.

Environment

• Plan: Max (active, billed through Anthropic)
• Account email: ajeevbhatia@gmail.com (same account on both devices)
• Computer: MacBook, macOS Tahoe 26.2
• Claude Desktop version: 1.3561.0 (fbc74b), build 2026-04-20T14:59:51.000Z
• Phone: iPhone 16 Pro
• Claude mobile app version: 1.260416.0

Expected behavior

Per the Help Center article on assigning tasks from anywhere in Cowork, Dispatch should be accessible from the mobile app when paired with a running Claude Desktop session on a Max plan. It was working normally for me until April 15.

Actual behavior

In the mobile app, when I open Dispatch:

• The screen displays: "Can't reach your desktop. Check that your computer is online and desktop app is open."
• The status icon under the Dispatch header shows "Asleep"
• This persists regardless of desktop state. Claude Desktop is running and in the foreground, the Mac is awake and plugged in, same Wi-Fi, same account.

Timeline

• Wed, April 15, 2026, ~10:00 AM: Using Dispatch normally
• Wed, April 15, 2026: Anthropic outage begins
• After outage resolved: All other Claude services came back online; Dispatch never recovered on my account
• 5 days since the incident: Dispatch has remained in "Asleep" / "can't reach your desktop" state. Support emailed, escalated to a live agent, no resolution.

Troubleshooting already attempted

• Confirmed Max subscription is active
• Updated Claude Desktop to the latest version (1.3561.0), fully quit and relaunched
• Updated Claude mobile app from the App Store (1.260416.0), fully quit and relaunched
• Logged out and back in on both devices
• Verified both devices are on the same account and same Wi-Fi network
• VPN disabled, firewall not blocking
• Claude Desktop running and foregrounded, Mac awake, not on battery saver

None of the above resolved the issue. State appears to be stuck server-side from the April 15 incident.

Related issues

This matches the pattern in #40958 (Dispatch non-functional after a "Resolved" incident, Max plan, no support response), as well as #49545 and #45937 where desktop shows permanently offline to mobile. Appears to be a pairing/session state on the backend that did not recover for affected accounts when the incident was closed.

Impact

I use Claude every day as a core part of my workflow and Dispatch is a primary reason I am on the Max tier.

Requested action

Please force-reset my Dispatch pairing state server-side, or advise on a client-side step that would trigger a re-registration. Happy to provide account ID, request IDs, or logs on request.

What Should Happen?

i should be able to use Dispatch through my mobile while my laptop is awake.

Error Messages/Logs

Steps to Reproduce

1. open dispatch on my mobile device
2. insert prompt
3. click send (to my laptop)

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.260416.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_