Dispatch foreground chat shows no replies in Cowork mode while background session works

Status Fixed / completed
Maintainer reply ✓ Yes — ashwin-ant
Activity 6 comments · opened Mar 28, 2026 · closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator) responded on this thread — see the highlighted reply below.

Summary

In Claude Desktop's Cowork/Dispatch mode, the foreground Dispatch chat UI shows no replies, while the background task session (the "Claude thinks here" workspace) continues to work normally and displays Claude's responses correctly.

The likely cause is that the SendUserMessage tool is not being injected correctly into the background session, so replies never get pushed back to the Dispatch foreground UI.

Symptoms

  • In Cowork mode, the Dispatch foreground chat receives no visible reply.
  • The background session still works normally.
  • Claude replies are visible inside the background session.
  • Claude can still execute actions successfully.
  • Restarting Claude Desktop does not resolve the issue.

Likely cause

SendUserMessage is not correctly injected / available in the background session, so the background session can think, act, and respond internally, but cannot deliver those replies back to the Dispatch foreground UI.

Reproduction steps

  1. Use Claude Desktop in Cowork / Dispatch mode.
  2. Start a task in Dispatch.
  3. After switching networks, observe that the issue begins to occur.
  4. Claude continues to operate normally in the background session.
  5. The Dispatch foreground chat shows no reply.
  6. Restart Claude Desktop.
  7. The issue still persists.

Actual result

  • No reply appears in the Dispatch foreground chat UI.
  • Replies remain visible only in the background session.

Expected result

  • Replies generated in the background session should be delivered and displayed in the Dispatch foreground chat UI.

Japanese summary

Claude Desktop の Cowork / Dispatch モードで、Dispatch 前面チャット画面に返信が表示されません。一方で、バックグラウンドセッション(「Claude が思考を行う場所」)では Claude の返信が正常に表示され、動作実行も成功します。

原因としては、SendUserMessage ツールがバックグラウンドセッションに正しく注入されておらず、そのため返信を Dispatch 前面 UI に戻せていない可能性が高いです。

再現条件としては、ネットワーク切替後に発生し、その後 Claude Desktop を再起動しても解消しません。

View original on GitHub ↗

6 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/40281
  2. https://github.com/anthropics/claude-code/issues/40255
  3. https://github.com/anthropics/claude-code/issues/40178

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

nanami-he · 6 months ago

Additional confirmation after further testing:

  • I fully uninstalled and reinstalled Claude Desktop / Claude Code, then paired / signed in again.
  • The issue still persists after reinstall.
  • Dispatch can still execute actions correctly.
  • I can see Claude's replies and tool activity in the background task session.
  • The foreground Dispatch chat still does not receive those replies.

This makes it look much more like the same known Dispatch/background-session delivery issue discussed in #40178, rather than a local install/cache problem.

In my case, reinstalling and re-pairing did not fix it.

nanami-he · 6 months ago

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

Foreground Dispatch replies are now showing correctly again.

For context:

  • reinstalling and re-pairing alone did not fix it earlier
  • but after updating, the problem appears to be gone

So this does seem consistent with a client / version-side issue rather than a persistent account or local cache problem.

Matjay007 · 6 months ago

I am dealing with it and its frustrating. It seems they are not taking this seriously

ashwin-ant collaborator · 6 months ago

This was fixed in v2.1.88 — Dispatch foreground chat in Cowork mode now shows agent replies. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.

github-actions[bot] · 5 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.