Claude Desktop VM Issues: Automatic VM Spawning and Resource Consumption

Claude Desktop has come under scrutiny following reports that the application automatically spawns a virtual machine (VM) on user machines without an explicit opt-in or a mechanism to disable the process. This behavior is primarily linked to the "Cowork" feature, which utilizes a sandboxed environment to execute tasks.

Automatic VM Deployment and Resource Impact

Claude Desktop deploys a VM to provide a secure sandbox for the Cowork feature. However, users have reported that this VM is spun up immediately and consumes significant system resources, regardless of whether the user intends to use the feature.

  • Storage Consumption: Users have reported the installation of a VM bundle approximately 10GB in size, which some claim is difficult or impossible to remove.
  • Memory Usage: The VM contributes to high virtual memory usage, with some users noting that the application feels slow and unresponsive as a result.

User Experience and Implementation Flaws

Community discussion highlights several perceived flaws in the implementation of the Claude Desktop environment, suggesting a rush to market over software craft.

Cross-Platform Inconsistencies

Users have noted critical UI bugs on Windows, specifically regarding permissions. One user reported that clicking permission buttons within the Claude Desktop app on Windows leads to broken links that point to macOS system preferences, indicating a lack of proper platform-specific testing.

Lack of User Control

There is a significant amount of frustration regarding the lack of an opt-in mechanism for the VM. Critics argue that the current design removes user agency, contrasting it with earlier eras of software where customization and personalization were prioritized.

Technical Perspectives on Sandboxing

While the resource overhead is high, some technical users argue that per-app virtualization is a necessary evolution for AI agents.

"I actually think per-app + agent virtualization is the future. Next version of an app is: 1. micro VM 2. agent on the VM 3. software bundled into the VM... It's self-modifying apps that are sealed off from touching parts of the computer they shouldn't."

Conversely, other users suggest that the VM could be implemented more efficiently, such as spinning up on-demand rather than at startup, or implementing a cooldown period to free RAM back to the host system.

Workarounds and Alternatives

For users experiencing issues with the VM, community members have suggested several alternatives:

  • Web-based Access: Using the browser version of Claude via Safari's "Add to Dock" feature to avoid the desktop application entirely.
  • Hyper-V Disabling: Some users found that disabling the "Virtual Machine Platform" feature in Windows prevents the VM from spawning, which in turn disables the Cowork tab in the application.
  • Isolated VMs: Running Claude Desktop inside a separate, isolated VM (such as Windows Sandbox) to prevent it from accessing the host machine's resources directly.

Sources