claude-code - 💡(How to fix) Fix [BUG] Cowork VM boot time [2 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#48894Fetched 2026-04-16 06:48:04
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×5commented ×2

Error Message

Error Messages/Logs

Code Example

Time	Event
11:50:50	VM starts (new sessiondata.img created)
11:51:50	60s timeout fires — Claude triggers quit cleanup (isAppQuit: true)
11:51:59	You click the dock icon (mid-typing)
11:52:50	VM force-killed after another 60s (won't stop gracefully, still booting)
11:53:04	VM starts again… same cycle repeats
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?

Cowork VM boot time (~4 min) exceeds connection timeout (60s), causing infinite restart loop. Each timeout fires isAppQuit: true, which kills the still-booting VM (another 60s force-kill), then immediately restarts it. UI becomes briefly responsive mid-cycle, causing sessions to be cut off while typing. Affects Apple Silicon Mac, Claude v1.2773.0.

What Should Happen?

Cowork VM boot time (~4 min) exceeds connection timeout (60s), causing infinite restart loop. Each timeout fires isAppQuit: true, which kills the still-booting VM (another 60s force-kill), then immediately restarts it. UI becomes briefly responsive mid-cycle, causing sessions to be cut off while typing. Affects Apple Silicon Mac, Claude v1.2773.0.

Error Messages/Logs

Time	Event
11:50:50	VM starts (new sessiondata.img created)
11:51:50	60s timeout fires — Claude triggers quit cleanup (isAppQuit: true)
11:51:59	You click the dock icon (mid-typing)
11:52:50	VM force-killed after another 60s (won't stop gracefully, still booting)
11:53:04	VM starts again… same cycle repeats

Steps to Reproduce

Cowork VM boot time (~4 min) exceeds connection timeout (60s), causing infinite restart loop. Each timeout fires isAppQuit: true, which kills the still-booting VM (another 60s force-kill), then immediately restarts it. UI becomes briefly responsive mid-cycle, causing sessions to be cut off while typing. Affects Apple Silicon Mac, Claude v1.2773.0.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.2773.0 (884b37) 2026-04-15T14:32:09.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Increase the connection timeout to a value greater than the Cowork VM boot time to prevent the infinite restart loop.

Guidance

  • Identify the current connection timeout value (60s) and consider increasing it to at least 4 minutes to accommodate the Cowork VM boot time.
  • Verify that the issue is resolved by checking the VM boot time and ensuring that the infinite restart loop no longer occurs.
  • If increasing the connection timeout is not feasible, consider implementing a more robust timeout handling mechanism that takes into account the VM boot time.
  • Investigate why the Cowork VM boot time has increased, as this may be a separate issue that needs to be addressed.

Example

No code snippet is provided as the issue does not specify any specific code changes.

Notes

The issue may be specific to Apple Silicon Macs and Claude version 1.2773.0, so the solution may not apply to other platforms or versions.

Recommendation

Apply a workaround by increasing the connection timeout value, as the root cause of the issue is not explicitly stated and may require further investigation.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork VM boot time [2 comments, 2 participants]