Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Dispatch unresponsive on Windows, Cowork sandbox intermittently unavailable [1 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#51684•Fetched 2026-04-22 07:55:39
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
memorialmerits-progmemorialmerits-prog
Participants
memorialmerits-progmemorialmerits-prog
Timeline (top)
labeled ×2unlabeled ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Title: Dispatch unresponsive on Windows, Cowork sandbox intermittently unavailable OS: Windows 10 Claude Desktop version: [check Help → About in the app and fill this in] Dispatch issue: Messages sent via Dispatch receive no response. Claude appears active but no reply ever appears in the thread. Persists across multiple Claude Desktop updates. Related to issues #49545, #40178, #41703. Cowork issue: Sandbox intermittently unavailable. Claude reports "system is down" and falls back to producing HTML in chat instead of writing files. No corresponding incident on status.claude.com when it occurs. Same conversation in claude.ai web works correctly. Local state: %LOCALAPPDATA%\Claude contains only a Logs folder with chrome-native-host.log. No bridge or session state files present to reset.

I should be able to communicate on Dispatch and be able to created pdf's and other documents with Claude being able to access sandbox

Title: Dispatch unresponsive on Windows, Cowork sandbox intermittently unavailable OS: Windows 10 Claude Desktop version: [check Help → About in the app and fill this in] Dispatch issue: Messages sent via Dispatch receive no response. Claude appears active but no reply ever appears in the thread. Persists across multiple Claude Desktop updates. Related to issues #49545, #40178, #41703. Cowork issue: Sandbox intermittently unavailable. Claude reports "system is down" and falls back to producing HTML in chat instead of writing files. No corresponding incident on status.claude.com when it occurs. Same conversation in claude.ai web works correctly. Local state: %LOCALAPPDATA%\Claude contains only a Logs folder with chrome-native-host.log. No bridge or session state files present to reset.

Code Example

N/a
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?

Title: Dispatch unresponsive on Windows, Cowork sandbox intermittently unavailable OS: Windows 10 Claude Desktop version: [check Help → About in the app and fill this in] Dispatch issue: Messages sent via Dispatch receive no response. Claude appears active but no reply ever appears in the thread. Persists across multiple Claude Desktop updates. Related to issues #49545, #40178, #41703. Cowork issue: Sandbox intermittently unavailable. Claude reports "system is down" and falls back to producing HTML in chat instead of writing files. No corresponding incident on status.claude.com when it occurs. Same conversation in claude.ai web works correctly. Local state: %LOCALAPPDATA%\Claude contains only a Logs folder with chrome-native-host.log. No bridge or session state files present to reset.

What Should Happen?

I should be able to communicate on Dispatch and be able to created pdf's and other documents with Claude being able to access sandbox

Error Messages/Logs

N/a

Steps to Reproduce

Title: Dispatch unresponsive on Windows, Cowork sandbox intermittently unavailable OS: Windows 10 Claude Desktop version: [check Help → About in the app and fill this in] Dispatch issue: Messages sent via Dispatch receive no response. Claude appears active but no reply ever appears in the thread. Persists across multiple Claude Desktop updates. Related to issues #49545, #40178, #41703. Cowork issue: Sandbox intermittently unavailable. Claude reports "system is down" and falls back to producing HTML in chat instead of writing files. No corresponding incident on status.claude.com when it occurs. Same conversation in claude.ai web works correctly. Local state: %LOCALAPPDATA%\Claude contains only a Logs folder with chrome-native-host.log. No bridge or session state files present to reset.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Most recent desktop version

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

Check the Claude Desktop version and verify the system configuration to resolve the Dispatch unresponsiveness and Cowork sandbox intermittent unavailability issues.

Guidance

  • Verify the Claude Desktop version by checking Help → About in the app, as the version number is currently missing.
  • Investigate the chrome-native-host.log file in %LOCALAPPDATA%\Claude for any error messages or clues related to the Dispatch and Cowork issues.
  • Compare the behavior with the claude.ai web version to identify potential differences in configuration or environment.
  • Review the related issues #49545, #40178, and #41703 for potential connections to the current problems.

Example

No specific code snippet can be provided without more information about the underlying system or APIs.

Notes

The lack of error messages, logs, or specific version numbers limits the ability to provide a more detailed solution. The issues may be related to the Windows 10 environment, the Claude Desktop version, or the Anthropic API configuration.

Recommendation

Apply workaround: Given the intermittent nature of the Cowork sandbox issue and the unresponsiveness of Dispatch, it may be necessary to try alternative configurations or environments to isolate the problem, such as testing on a different Windows version or using a different API endpoint if available.

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#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

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

Back to top recommendations

TRENDING