[FEATURE] Allow configuring VM bundle (vhdx) storage location

Open 💬 6 comments Opened May 4, 2026 by byu111

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Claude Cowork's VM bundle (rootfs.vhdx, sessiondata.vhdx, etc.) is stored in a hardcoded location under %LocalAppData%\...\claudevm.bundle\

The bundle is already ~12 GB after initial setup, and sessiondata.vhdx grows over time as the VM accumulates state. On systems where C: is with limited capacity, this footprint is significant and unavoidable — there is currently no way to relocate it to a secondary drive. NTFS junctions (mklink /J) fail. There is no reliable user-side workaround.

For me, it's quite unconvenient. I have to move other files to D: to continue use Cowork.

  • OS: Windows 11
  • Latest Claude Desktop

Proposed Solution

Add a setting in Claude Desktop (Settings → Cowork) that lets users specify a custom storage location for the VM. When changed, the app should either migrate the existing bundle to the new location or download it fresh there on next startup.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗