[BUG] Dispatch non-functional since 29 March incident — messages marked "Read" but no response delivered, reproducible on desktop directly (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?
Title: Dispatch non-functional since 29 March incident — messages marked "Read" but no response delivered, reproducible on desktop directly (Max plan)
Body:
Summary
Dispatch has been non-functional on my account since 29 March, following the incident on 28–29 March (ref q5qk1234v205). One single message successfully returned a response on 4 April; every message before and since has failed. The fix shipped in Claude Desktop 1.1.9493 did not resolve the issue for my account. Behaviour matches existing issues #40178, #40958, and #45937.
Notable:
- The failure reproduces when typing into Dispatch directly on the macOS app, not only from the paired iOS device — suggests the broken state is at the Dispatch session/agent layer rather than the device pairing bridge.
- One brief recovery on 4 April (a single successful response, then back to broken) suggests the failure state is transient/recoverable server-side rather than permanently wedged.
Timeline
- 29 March: Dispatch stopped responding (following 28–29 March incident
q5qk1234v205) - 4 April: One single message returned a response, then the failure resumed immediately
- 4 April – present: 100% failure rate across all subsequent messages, ~2 weeks
Environment
- Plan: Max
- Hardware: MacBook Pro 14-inch, Apple M5, 16 GB
- macOS: Tahoe 26.3.1 (a)
- Claude for Mac: 1.3109.0 (35cbf6)
- Paired mobile device: iOS Claude app 1.260409.1
- Pairing status: iOS app shows green "Online" indicator at top of Dispatch thread
Expected behaviour
Messages sent into a Dispatch thread (from either the iOS app or the macOS app directly) should be received by the Dispatch agent, processed, and a response delivered back to the conversation thread on both devices.
Actual behaviour
- Messages sent from iOS are delivered to the desktop agent and marked as "Read"
- Messages typed directly into the Dispatch thread on the macOS app produce the same result: no response, stuck on "Read"
- No response is ever generated or delivered, on either device
- Thread remains stuck on "Read" indefinitely
- Behaviour is 100% reproducible on every message attempt, from both devices (with the single exception of one successful message on 4 April)
- iOS app continues to show green "Online" connection indicator throughout
- Standard (non-Dispatch) Cowork sessions and Claude Code sessions function normally on the same account, same machine, same network
Steps to reproduce
- Open paired Dispatch thread
- Send any message — either from iOS app or typed directly into Dispatch on the macOS app
- Observe: message shows "Read"; connection indicator remains green
- Wait: no response ever arrives
Troubleshooting already completed
- Updated Claude for Mac to latest version (1.3109.0)
- Force-quit and relaunched Claude for Mac multiple times
- Toggled Dispatch off, hard refresh, toggled back on
- Full logout on both desktop and mobile, re-paired via QR code
- Confirmed Mac remains awake (lid open, no display sleep) and Claude for Mac stays running throughout
- Confirmed non-Dispatch Cowork sessions work normally on the same setup — rules out VM provisioning, API reachability, and auth
- Confirmed the failure reproduces when sending from the macOS Dispatch UI directly — rules out iOS client and device pairing
Related issues
- #40178
- #40958
- #45937
- #40070 (session collision loop analysis)
- #40179 (cloud relay layer)
Impact
Max plan subscriber, Dispatch is a core daily workflow dependency, broken for 3 weeks.
---
File at: https://github.com/anthropics/claude-code/issues/new
What Should Happen?
Expected behaviour
Messages sent into a Dispatch thread (from either the iOS app or the macOS app directly) should be received by the Dispatch agent, processed, and a response delivered back to the conversation thread on both devices.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce
- Open paired Dispatch thread
- Send any message — either from iOS app or typed directly into Dispatch on the macOS app
- Observe: message shows "Read"; connection indicator remains green
- Wait: no response ever arrives
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude Cowork 1.3109.0 (35cbf6) 2026-04-16T20:32:01.000Z
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
<img width="148" height="320" alt="Image" src="https://github.com/user-attachments/assets/9e079e7c-3069-442d-8fa5-d4fffc983cd1" />
<img width="148" height="320" alt="Image" src="https://github.com/user-attachments/assets/6e155928-eecf-4347-b546-52f1ee11ae94" />
<img width="148" height="320" alt="Image" src="https://github.com/user-attachments/assets/35d28705-8e91-43e7-9626-79fdff237f3c" />
<img width="148" height="320" alt="Image" src="https://github.com/user-attachments/assets/f800623e-3c44-4647-8097-4c094369f0b3" />
<img width="148" height="320" alt="Image" src="https://github.com/user-attachments/assets/fe23ed28-5348-4f6e-8b50-55af10dbf07b" />
This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗