›_ Claude Code Issues
Claude Code Issues / #40178

[BUG] Dispatch: messages marked as read but responses never appear in UI (desktop or mobile)

Resolved 💬 40 comments Opened Mar 28, 2026 by korner1977 Closed Mar 29, 2026

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?

Description:

Dispatch receives and processes messages correctly (marked as "✓ Lettura / Read") but responses are never delivered to the chat thread — neither on the desktop app nor on the Claude mobile app.

Environment:

OS: Windows 10 Pro 10.0.19045
Claude Desktop version: 1.1.9310
Account: Pro
What happens:

User sends a message in the Dispatch tab
Message is marked as "✓ Read" (the desktop agent receives it)
No response ever appears in the Dispatch thread — on desktop or mobile
What the logs show:
The agent processes the message and generates a correct response (visible in audit.jsonl), but the response is never delivered to the UI. Example from logs:

result: "Tutto funziona! Sono qui e pronto. Dimmi pure cosa posso fare per te."
This text never appears in Dispatch.

In a previous session, ToolSearch for SendUserMessage returned "No matching deferred tools found" — suggesting the response delivery mechanism is broken.

Additional notes:

The Cowork VM starts correctly
Normal Chat and Cowork sessions work fine
The issue is isolated to Dispatch response delivery
Reinstalling the app did not fix the issue

What Should Happen?

Dispatch receives and processes messages correctly (marked as "✓ Read") but responses are never delivered to the chat thread — neither on the desktop app nor on the Claude mobile app.

Steps to reproduce:

Open Claude Desktop (Windows 10, v1.1.9310)
Go to Cowork → Dispatch tab
Send any message (e.g. "test")
Message is marked "✓ Read"
Wait — no response ever appears
Expected: Response appears in the Dispatch chat thread.

Actual: Message is processed internally (response visible in audit.jsonl), but never delivered to the UI. Example response generated but not shown: "Tutto funziona! Sono qui e pronto." — confirmed on mobile app too, no responses appear there either.

Additional context:

ToolSearch for SendUserMessage returns "No matching deferred tools found" — response delivery mechanism appears broken
VM starts correctly, normal Chat and Cowork work fine
Reinstalling did not fix the issue

Error Messages/Logs

Relevant log excerpts (cowork_vm_node.log):


[VM:start] Windows VM service configured
[VM:start] Startup complete, total time: 11304ms
[Spawn:vm] Spawn succeeded in 56ms
[CoworkVMProcess] kill called with signal: SIGTERM
[Process] Exited, code=0, duration=6440ms
From audit.jsonl (agent session):


{"type":"result","subtype":"success","result":"Tutto funziona! Sono qui e pronto. Dimmi pure cosa posso fare per te."}
Response is generated successfully but never reaches the UI.

From audit.jsonl (dispatch agent — previous session):


{"type":"user","content":[{"type":"tool_result","content":"No matching deferred tools found"}]}
ToolSearch for SendUserMessage fails — this appears to be the root cause: the agent cannot find the tool needed to deliver responses back to the Dispatch thread.

Log paths (Windows):

C:\Users\...\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\cowork_vm_node.log
C:\Users\...\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\local-agent-mode-sessions\...\agent\...\audit.jsonl

Steps to Reproduce

Open Claude Desktop (Windows 10, v1.1.9310)
Go to Cowork → Dispatch tab
Send any message (e.g. "test")
Message is marked "✓ Read" / "Lettura"
Wait — no response ever appears
Expected Behavior:
Claude processes the message and a response appears in the Dispatch chat thread (on desktop and/or mobile app).

Actual Behavior:
The message is received and processed internally (response visible in audit.jsonl log), but never delivered to the UI. Example response generated but not shown: "Tutto funziona! Sono qui e pronto." — also confirmed on Claude mobile app: no responses appear there either.

Additional context:
Internal logs show ToolSearch for SendUserMessage returning "No matching deferred tools found" — the response delivery mechanism appears broken. VM starts correctly, normal Chat/Cowork work fine. Reinstalling did not help.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

40 Comments

CannibalKush · 3 months ago

I was getting this error. I implored Claude to call the tool exactly by name, and it did. It gets an error, but the message actually does deliver.

driiiiiiip · 3 months ago

Yes, thank you for bringing this issue up! It has totally messed up my workflow since it appeared. It's basically made dispatch on mobile non-functional. And I just upgraded to $200 a month so I can use this. I can see Claude's responses if I go on my desktop app and click "See Background Tasks", but they never reach the chat. Here's what Claude said about it: The search for SendUserMessage returning "No matching deferred tools found" is the smoking gun — it's the same error I hit earlier in our conversation. The response delivery mechanism between the desktop and the cloud relay layer is broken.

support326 · 3 months ago

Experiencing the same issue. Sounds like its a bug and it's in Anthropic's hands to fix.

driiiiiiip · 3 months ago

Dispatch also couldn't access a folder, even when I was using it through "background tasks" (where I can see responses.) He said: Here's the simple reality: this Cowork sandbox can't see ~/.claude/projects/ on your Mac, and the folder-mounting flow isn't working right now (likely tied to the same Dispatch bug).

So I'm back on Claude Code in a terminal session until the Claude desktop app starts working again for working with files and communicating with me about them.

rperez030 · 3 months ago

Experiencing the issue right now, in my case with the Claude desktop app running on macOS. I'm glad not to be alone on this, but hoping it gets addressed soon. Happy to provide any additional detail if needed.

davidgbriand · 3 months ago

same.

catgirl91 · 3 months ago

ughh I been experiencing the same issue since yesterday afternoon. Im stuck and i cant get the dispatch to respond back to me. I tried to contact support but no response.

<img width="603" height="1311" alt="Image" src="https://github.com/user-attachments/assets/fd978f9c-b247-4f06-974c-23e4c126c06c" />

AwesomeD83 · 3 months ago

On the $200 plan running on Windows 11 and having the same issue. Stopped working yesterday.

moyvera · 3 months ago

Sad story, I just paid the max plan and this stopped working :(

catgirl91 · 3 months ago

Same, im in the Max 20X plan and im stuck on a project that i was running from the dispatch. Is anyone here on X? I ported about this and tagged them but maybe people should do this there too.

cosgrs · 3 months ago

Same issue. Glad I'm not alone. Also I wrote to "Fin AI Agent" - Anthropic's support. No response from that either.

Just subscribed the other day and not getting use of what I'm paying for.

Lug16 · 3 months ago

Same happening to me, is it there any work around?

SamAlshami · 3 months ago

Same Issue

brianbest · 3 months ago

same issue here i tried:

  • deleting convo history, memories
  • deleting everything and restarting
  • deleting everything, turning off dispatch, an restarting
michedapt · 3 months ago

Same here. oh well

kylegao91 · 3 months ago

Hi all, I'm an engineer working on dispatch, confirm that the degraded in Claude desktop app v1.9310, we are investigatiing.

davidgbriand · 3 months ago

Thx Kyle. Looking forward to hearing when it's fixed.

catgirl91 · 3 months ago

This hasn’t been resolved, I’m not sure why is marked as resolved.

kylegao91 · 3 months ago

We have identified the cause and are working on a fix. As a workaround, you can continue using standard Cowork sessions, which are unaffected.

catgirl91 · 3 months ago

Thank you for looking into this. However, I want to clarify that this isn't just about losing access to a chat feature. Dispatch was running an active agent that was orchestrating my entire workflow, it was autonomously breaking down tasks and sending them as individual Dispatch commands (dashboard readiness audits, API credential setup, GA4 investigation, file organization, etc.). When Dispatch went down, it wasn't just a conversation that stopped; my entire automated workflow manager went down mid-project. I've lost visibility into what tasks were completed, what was in progress, and what was still pending. Switching to standard Cowork sessions doesn't recover any of that context. Is there a way to recover or view the state of those Dispatch-initiated tasks so I can pick up where things left off?

kylegao91 · 3 months ago
Thank you for looking into this. However, I want to clarify that this isn't just about losing access to a chat feature. Dispatch was running an active agent that was orchestrating my entire workflow, it was autonomously breaking down tasks and sending them as individual Dispatch commands (dashboard readiness audits, API credential setup, GA4 investigation, file organization, etc.). When Dispatch went down, it wasn't just a conversation that stopped; my entire automated workflow manager went down mid-project. I've lost visibility into what tasks were completed, what was in progress, and what was still pending. Switching to standard Cowork sessions doesn't recover any of that context. Is there a way to recover or view the state of those Dispatch-initiated tasks so I can pick up where things left off?

@catgirl91 I'm sorry about the disruption. You can perhaps use the background session shown below on desktop since it has the same orchestration capabilities.

<img width="630" height="216" alt="Image" src="https://github.com/user-attachments/assets/8d30c157-c723-4ee2-b063-f8be135a8418" />

nanami-he · 3 months ago

Same issue here.

I can confirm the following after additional testing:

  • Dispatch foreground chat does not show replies.
  • The background task session continues to work normally.
  • Claude's replies and tool activity are visible in the background session.
  • Dispatch can still execute actions successfully.
  • I fully uninstalled and reinstalled Claude Desktop / Claude Code, then paired / signed in again.
  • Reinstalling and re-pairing did not fix the issue.

So at least in my case, this does not appear to be caused by a local install/cache problem.

getbignow · 3 months ago

!image

nanami-he · 3 months ago

Update from my side: after a system / app update, the issue appears to be resolved.

Dispatch foreground replies are now showing correctly again.

Important detail:

  • reinstalling and re-pairing alone did not fix it earlier
  • the recovery happened only after the later update

So this seems more consistent with a client / version-side issue than with a persistent local install/cache/account problem.

nickeyjiang-cpu · 3 months ago

Environment

  • Device: Mac Mini 2024 (Apple M4, 16GB RAM)
  • OS: macOS Sequoia 15.6
  • Claude Desktop: Latest version (as of March 29, 2026)
  • Mobile: iPhone, Claude iOS app (latest)
  • Plan: Pro/Max subscriber

Symptoms

Dispatch is one-way only: phone → desktop works, desktop → phone does not.

  • I can send messages from the Claude iOS app (Dispatch) to my Mac Mini — Claude receives and processes them correctly.
  • Claude generates responses and they appear in the desktop conversation window.
  • Responses are never delivered to the mobile Dispatch client. The phone only shows a "read" receipt, with no response content.
  • All task execution (web search, file generation, computer use) works correctly on the desktop side. The only failure is the response delivery back to mobile.

What I've tried

  • Restarted Claude Desktop (full quit + relaunch)
  • Enabled macOS Screen Recording permission for Claude
  • Enabled all notification settings for Claude (Banners, Lock Screen, Notification Center, Sound)
  • Enabled "Allow notifications when the display is sleeping"
  • Restarted Dispatch on the mobile app
  • Verified Energy settings (no sleep, wake for network access, auto-restart after power failure)

Additional context

  • This same account works perfectly on my MacBook — Dispatch is fully bidirectional on that machine.
  • Switching to the Mac Mini (same account, same network) breaks the return path only.
  • The Mac Mini is intended as a 24/7 always-on Dispatch host.

Expected behavior

Claude's responses should be delivered to the mobile Dispatch client in real time.

Actual behavior

Responses are generated but never reach the mobile client. Only "read" receipts appear.

kylegao91 · 3 months ago

The issue affecting Dispatch has been resolved. We fixed an underlying issue that prevent the agent from sending responses to user messages. Please update to Claude desktop app 1.1.9493. We apologize for any inconvenience caused.

moyvera · 3 months ago

is it me ? I updated my desktop app to such version but I still get the same issue

jjbaron · 3 months ago

Still same issue for me as well. Running Claude 1.1.9493 (b58a0b) 2026-03-29T03:33:07.000Z

odavidbrito · 3 months ago

Same here. Updated desktop to the new version and same behavior, phone app does not receive responses from background tasks

hunvee3 · 3 months ago

For me it kinda worked but still see weird behaviour.
Responses are not frequent but at least I get a result message back. files or snapshots get stuck in a loading cycle.

!Image

Topherhindman · 3 months ago

definitely not fixed. on Claude 1.1.9493 (b58a0b) 2026-03-29T03:33:07.000Z and not getting any replies still

sounddroid · 3 months ago

I had to delete the Dispatch conversation on Claude Desktop and start fresh in order for everything to work again. Since then, it's been solid

SamAlshami · 3 months ago

Working with no issues after the update. Thank you.

albert-cyber-dealer · 3 months ago

not sure why still seeing this issue

jjbaron · 3 months ago
I had to delete the Dispatch conversation on Claude Desktop and start fresh in order for everything to work again. Since then, it's been solid

This worked for me. Thanks!

albert-cyber-dealer · 3 months ago
not sure why still seeing this issue

<img width="333" height="188" alt="Image" src="https://github.com/user-attachments/assets/8608f313-8bde-47f8-8bcc-4b75f0a91acd" />

As sounddroid said, deleting the dispatch conversation worked for me too. A screenshot is attached in case u don't know where to do the deletion.

odavidbrito · 3 months ago

Working fine now while some hours ago the new version seemed to behave as the issue was still occurring. Thanks!

ubervincent · 3 months ago

Deleted conversation and it's working.

Lug16 · 3 months ago

Confirmed, as @ubervincent indicates, delete the conversation and start fresh will work

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.