Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Dispatch: messages marked Read but no response delivered (Windows, post-reinstall) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52330•Fetched 2026-04-24 06:10:01
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
HuguesDHuguesD
Participants
github-actions[bot]github-actions[bot]HuguesDHuguesD
Timeline (top)
labeled ×5commented ×1

Error Message

  • No error surfaced in the UI

Error Messages/Logs

Fix Action

Fix / Workaround

After a clean reinstall of Claude Desktop (Windows) and the Claude mobile app (Android), re-pairing Dispatch succeeds, but every message sent from the mobile app is marked ✓ Read on both the phone and the desktop Dispatch pane, then hangs indefinitely. No response ever renders on either client. This matches the symptom pattern of #40178, #40179, #40430 — and critically persisted through a full uninstall + reinstall on both ends, which rules out stale local state.

Response text (and any file writes) appear in the Dispatch thread on both desktop and mobile, and written files show up in the Outputs panel. Actual:

  • Messages marked ✓ Read on both ends
  • Thinking indicator spins indefinitely
  • No response text on either client
  • Outputs panel remains empty
  • No error surfaced in the UI
  1. Uninstall Claude Desktop (Windows) and Claude mobile app (Android). Reinstall both from scratch.
  2. Sign in to the same Anthropic account on both.
  3. On Desktop: Cowork → Dispatch → Get started → Finish setup. QR code displayed.
  4. On Android: Claude app → Dispatch tab → scan QR. Pairing confirmed instantly.
  5. From the phone, send a trivial message: e.g. ok do you function? then write a test.txt file containing the word test.
  6. Observe on desktop Dispatch pane: both messages appear, each marked ✓ Read, with a thinking spinner that never resolves. Outputs panel stays empty.
RAW_BUFFERClick to expand / collapse

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?

After a clean reinstall of Claude Desktop (Windows) and the Claude mobile app (Android), re-pairing Dispatch succeeds, but every message sent from the mobile app is marked ✓ Read on both the phone and the desktop Dispatch pane, then hangs indefinitely. No response ever renders on either client. This matches the symptom pattern of #40178, #40179, #40430 — and critically persisted through a full uninstall + reinstall on both ends, which rules out stale local state.

What Should Happen?

Response text (and any file writes) appear in the Dispatch thread on both desktop and mobile, and written files show up in the Outputs panel. Actual:

  • Messages marked ✓ Read on both ends
  • Thinking indicator spins indefinitely
  • No response text on either client
  • Outputs panel remains empty
  • No error surfaced in the UI

Error Messages/Logs

Steps to Reproduce

  1. Uninstall Claude Desktop (Windows) and Claude mobile app (Android). Reinstall both from scratch.
  2. Sign in to the same Anthropic account on both.
  3. On Desktop: Cowork → Dispatch → Get started → Finish setup. QR code displayed.
  4. On Android: Claude app → Dispatch tab → scan QR. Pairing confirmed instantly.
  5. From the phone, send a trivial message: e.g. ok do you function? then write a test.txt file containing the word test.
  6. Observe on desktop Dispatch pane: both messages appear, each marked ✓ Read, with a thinking spinner that never resolves. Outputs panel stays empty.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Claude 1.3883.0.0 Claude_pzs8sxrjxfjjc

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

  • Performed full uninstall/reinstall of both Desktop and Android apps before this repro — local state is fresh.
  • Normal Chat and standard Cowork sessions work correctly; the failure is isolated to Dispatch response delivery.
  • Same symptom pattern as #40179's diagnosis: backend generates response, relay layer between CCR and clients fails to deliver.

extent analysis

TL;DR

The issue is likely related to a problem with the relay layer between the backend and clients, causing messages to be marked as read but not delivered, and a workaround may involve investigating the Anthropic API or the Claude Code version.

Guidance

  • Investigate the Anthropic API to see if there are any known issues or updates that could be causing the problem.
  • Check the Claude Code version (1.3883.0.0) to see if there are any known bugs or issues related to the Dispatch feature.
  • Since normal Chat and standard Cowork sessions work correctly, try to isolate the issue to the Dispatch response delivery process.
  • Review the symptom pattern of #40179's diagnosis, which suggests a backend-generated response failing to deliver through the relay layer.

Notes

The issue persists after a full uninstall and reinstall of both Desktop and Android apps, ruling out stale local state, and the same symptom pattern is observed as in previous issues (#40178, #40179, #40430).

Recommendation

Apply workaround: Investigate the Anthropic API and the Claude Code version to identify potential issues with the relay layer, as the problem seems to be isolated to the Dispatch response delivery process.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING