claude-code - 💡(How to fix) Fix [BUG] Failed to start Claude's workspace VM connection timeout after 60 seconds [1 comments, 2 participants]

In Cowork - "Failed to start Claude's workspace VM connection timeout after 60 seconds Restarting Claude or your computer sometimes resolves this. If it persists, you can reinstall the workspace."

Logs in the cowork_vm_node.log file in the Packages folder -

2026-04-14 23:06:31 [info] [VM:start] Still waiting for guest connection... 10259ms elapsed, 21 polls 2026-04-14 23:06:41 [info] [VM:start] Still waiting for guest connection... 20531ms elapsed, 41 polls 2026-04-14 23:06:51 [info] [VM:start] Still waiting for guest connection... 30799ms elapsed, 61 polls 2026-04-14 23:07:02 [info] [VM:start] Still waiting for guest connection... 41066ms elapsed, 81 polls 2026-04-14 23:07:12 [info] [VM:start] Still waiting for guest connection... 51321ms elapsed, 101 polls 2026-04-14 23:07:21 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares 2026-04-14 23:07:21 [info] Dispatching startup error: VM connection timeout after 60 seconds 2026-04-14 23:07:21 [error] [VM:start] Startup failed: Error: VM connection timeout after 60 seconds

TL;DR

The issue is likely related to a VM connection timeout, and restarting Claude or the computer may resolve it temporarily, but a more permanent solution is needed.

Guidance

• The error message "VM connection timeout after 60 seconds" suggests that the connection to the virtual machine is not being established within the given time frame.
• The logs indicate that the last completed step was "add_plan9_shares", which may be a point of investigation.
• Restarting Claude or the computer sometimes resolves this issue, but it's not a reliable solution.
• Reinstalling the workspace has not changed the error message, so it's likely not a configuration issue.

Example

No code snippet is provided as the issue seems to be related to the VM connection and not a specific code error.

Notes

The issue is specific to the user's setup, and more information about the environment and configuration may be needed to provide a definitive solution. The fact that restarting sometimes resolves the issue suggests that it may be related to a transient problem.

Recommendation

Apply workaround: Since the issue is intermittent and restarting sometimes resolves it, it may be worth exploring other workarounds such as increasing the timeout value or investigating the "add_plan9_shares" step to see if it's causing the delay.