Allow configuring LocalCache/Cowork VM data location on Windows (MSIX install)

Resolved 💬 3 comments Opened May 22, 2026 by DiegooTez Closed Jun 21, 2026

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

On Windows, Claude Desktop installed via MSIX/Microsoft Store stores all Cowork VM data
in C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache

This folder grows to 10-12GB with normal Cowork usage (creating apps, running tasks)
and cannot be moved to another drive. Attempts to use symbolic links or junctions
break the app entirely.

Users with small C: drives (117GB with Windows + other apps) run out of space quickly.
The "Move" button in Windows Settings only moves the executable, not LocalCache.

Users with limited C: drives run out of space quickly with no official workaround.

Proposed Solution

Add a setting in Claude Desktop to configure the data/cache directory location,
similar to how other Electron apps (VS Code, etc.) allow custom data paths.

Alternatively, document an official supported method to move LocalCache to another drive.

Alternative Solutions

  • OS: Windows 11
  • Install method: MSIX / Microsoft Store
  • LocalCache grew to 12GB in 2 days of Cowork usage
  • C: drive: 117GB total, leaving only ~30GB free after Claude
  • Symbolic links and junctions to D: break the app on startup
  • Related issues: #29792, #28892

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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