Dispatch tab not showing responses — TypeError: Cannot read properties of undefined (reading 'includes')
Resolved 💬 3 comments Opened Apr 4, 2026 by Fednand-B Closed Apr 7, 2026
Summary
The Dispatch (Cowork) tab in Claude Desktop is not displaying any responses from the agent, even though the backend is processing messages and generating responses correctly.
Environment
- OS: Windows 11
- Claude Desktop version: 1.569.0
- Claude Code (VM): 2.1.87
What's Happening
The Dispatch agent is receiving messages and generating responses successfully (confirmed via audit logs and cycle health logs). However, responses never appear in the Dispatch chat UI.
Confirmed working (backend):
- Audit log shows successful responses:
"result": "Hey Fed! You're connected...",stop_reason: end_turn - Cycle health reports:
had_first_response: true,seconds_to_outcome: 8,cycle_health: healthy - Messages show
✓ Readstatus in the UI
Confirmed broken (frontend):
claude.ai-web.logshows repeated JS crash:
````
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'includes')
[REACT_QUERY_CLIENT] QueryClient error: Error: Not foundon every Dispatch tab load[LocalAgentModeSessionManager] Bridge session: disabling renderer-dependent tools[spa] chunk preload failed, reloading TypeError: Failed to fetch dynamically imported module: https://assets-proxy.anthropic.com/...
Steps to Reproduce
- Open Claude Desktop on Windows
- Click the Cowork tab
- Send any message (e.g. "Hello")
- Message shows
✓ Readbut no response ever appears - Check
claude.ai-web.log—TypeError: Cannot read properties of undefined (reading 'includes')fires on every render
What Was Tried
- ✅ Restarted Claude Desktop multiple times
- ✅ Rebooted machine
- ✅ Cleared 211MB renderer cache (
Cache/Cache_Data/) - ✅ Disabled VPN (Surfshark) — CDN returns 200 after disabling
- ✅ Force hard-reloaded renderer (Ctrl+Shift+R)
- ✅ Confirmed winget shows 1.569.0 is the latest version — no update available
Impact
Dispatch is completely unusable. The Code tab works fine as a workaround, but persistent background agent sessions via Dispatch are inaccessible.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗