claude-code - 💡(How to fix) Fix [BUG] System prompt cites non-existent AppData\Roaming\Claude paths in Cowork mode on MSIX-packaged Windows desktop app

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?

This bug is in the Windows Claude Desktop app running in Cowork mode (not the Claude Code CLI — filing here because Cowork and Windows-MSIX bugs are tracked in this repo per existing precedent).

In every chat in Cowork mode, the system prompt tells Claude that auto-memory, outputs, uploads, skills, and other app data live at paths like:

C:\Users\<user>\AppData\Roaming\Claude\local-agent-mode-sessions\<session-guid>\<account-guid>\spaces\<space-guid>\memory\

These paths do not exist on disk and cannot be opened in File Explorer. Pasting one returns: "Windows can't find 'C:\Users<user>\AppData\Roaming\Claude...'. Check the spelling and try again."

Cause: the Windows Claude Desktop app is installed as an MSIX (Microsoft Store) package. Windows redirects writes from %APPDATA%\Claude... to a virtualized per-package location under:

C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\...

Everything after \Claude\ is identical between the two paths. The code that builds the system prompt does not account for this MSIX virtualization, so it advertises the un-virtualized form, which doesn't exist on disk.

Impact: when users ask Claude where their files are stored, Claude (correctly, given the system prompt) returns a path the user cannot navigate to. Users conclude that auto-memory or outputs don't exist when they actually do — they're just at a different physical location. Affects every cited path: auto-memory, outputs, uploads, skills, plugins, sessions.

What Should Happen?

The path-string generator that produces these references in the system prompt should detect MSIX packaging on Windows and emit:

C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\...

instead of:

C:\Users\<user>\AppData\Roaming\Claude\...

Users would then be able to paste any path Claude cites directly into File Explorer and open the folder.

Error Messages/Logs

No app-level error or log entry. The bug manifests in File Explorer:

    Windows can't find 'C:\Users\<user>\AppData\Roaming\Claude\local-agent-mode-sessions\<session-guid>\<account-guid>\spaces\<space-guid>\memory'. Check the spelling and try again.

Confirmation that the real data is under AppData\Local\Packages: inside the Cowork workspace sandbox, `cat /proc/mounts` shows every FUSE mount source begins with:

    /mnt/.virtiofs-root/shared/c/Users/<user>/AppData/Local/Packages/Claude_pzs8sxrjxfjjc/LocalCache/Roaming/Claude/...

Steps to Reproduce

1. Install the Claude desktop app on Windows from the Microsoft Store (MSIX-packaged).
2. Open a new chat in Cowork mode.
3. Ask Claude: "Where on disk are my auto-memory files stored?"
4. Claude responds with a path like: C:\Users<user>\AppData\Roaming\Claude\local-agent-mode-sessions<session-guid><account-guid>\spaces<space-guid>\memory\
5. Copy that path. Open File Explorer. Paste into the address bar. Press Enter.
6. Observe: "Windows can't find ..." error.
7. To verify the data does exist, navigate manually to: C:\Users<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\local-agent-mode-sessions<session-guid><account-guid>\spaces<space-guid>\memory
   The auto-memory files (MEMORY.md and the individual memory files) will be present.

Note: AppData is hidden by default in Windows; enabling "Show hidden items" in File Explorer (or using %LOCALAPPDATA% in the address bar) is required to browse to either path. The "Windows can't find" error happens regardless of hidden-file visibility — the AppData\Roaming\Claude folder simply does not exist on MSIX installs.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

1.6608.2 (ebf1a1) — this is the Claude Desktop app version (Help > About), not Claude Code CLI. Cowork mode runs in the desktop app and does not expose a claude --version equivalent.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

This bug is in the Claude Desktop app's Cowork mode on Windows, not the Claude Code CLI. Filing under this form because Cowork and Windows-MSIX bugs are already tracked in this repo — see prior reports #37712, #43573, #24859, #26073, #55465.

App version (from Help > About in Claude Desktop): 1.6608.2 (ebf1a1), built 2026-05-08T23:17:27.000Z OS: Windows 11 Home, version 25H2, OS build 26200.8246, Windows Feature Experience Pack 1000.26100.297.0 Install source: Microsoft Store (MSIX-packaged); package family name: Claude_pzs8sxrjxfjjc

The Terminal/Shell field above is not applicable — Claude Desktop is a GUI app, not a CLI. The "I am using the latest version of Claude Code" preflight checkbox was ticked on the basis that the user is on the latest Claude Desktop build (this report is for Claude Desktop, not Claude Code CLI).

Suggested locations to fix:

• Wherever the app constructs base paths like C:\Users\<user>\AppData\Roaming\Claude\local-agent-mode-sessions\... for inclusion in the system prompt. On MSIX-packaged installs on Windows, the base should resolve to C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\....
• All system-prompt references affected: auto-memory directory, outputs directory, uploads directory, skills directory (.claude\skills), plugins, sessions, spaces.

Workaround for users in the meantime: manually translate any cited path by replacing AppData\Roaming\Claude with AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude — everything after \Claude\ stays the same.