morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #8968] [Bug] setup/doctor target the pre-3.1623 MSIX path; Claude Desktop now reads %LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc #7869

New issue

Open

opened 2026-11-05 05:43:37 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-05 05:43:37 +00:00

Owner

Originally created by @gougeoncat on GitHub (Nov 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/8968

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Setup, packaging, or upgrade

Observed behavior

rea setup --client claude_desktop (rea-agents@6.8.0 via npx) wrote mcpServers.rea to
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json
(plan action: CREATE). rea doctor --client claude_desktop --json then reported
registration:claude_desktop ok/healthy, state "aligned".

Claude Desktop (MSIX, package family Claude_pzs8sxrjxfjjc, version 4.16336.0.0) did not load the server:
Settings > Developer showed "No servers added" after fully quitting and restarting the app (twice).

Observed on disk:

The package-private Roaming\Claude folder contained only the setup-created config and a marker
file .user-data-left.claude_pzs8sxrjxfjjc (timestamp ~10 min after setup).
%APPDATA%\Claude did not exist; no other Claude package under %LOCALAPPDATA%\Packages.
The config the app actually uses: %LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\claude_desktop_config.json
(pre-existing, last written earlier the same day).

Manually merging the same mcpServers.rea entry into the Claude-Data file made the server appear
in Settings > Developer; binary_session returned normally and tools ran (Ghidra availability, WABT inspection).

Reproduction

Windows, Claude Desktop MSIX (Claude_pzs8sxrjxfjjc, 4.16336.0.0) after its migration to %LOCALAPPDATA%\Claude-Data\.
Quit Claude Desktop fully; run: npx rea-agents@6.8.0 setup --client claude_desktop ; approve.
Run: rea doctor --client claude_desktop --json -> registration reported healthy/aligned.
Start Claude Desktop -> Settings > Developer lists no MCP servers.
Reproduced on 1 machine, consistently across 2 restarts.

Expected behavior

setup, doctor and uninstall should resolve the configuration file the installed Claude Desktop
actually reads (%LOCALAPPDATA%\Claude-Data\claude_{publisher}\claude_desktop_config.json after the
migration), or report the location as unresolved instead of reporting a healthy registration.
Reference (not REA documentation): anthropics/claude-code#103860 reports that Claude Desktop
3.1623.0.0 moved MSIX app data to %LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\.

Impact and scope

Silent failure: doctor reports a healthy registration the app never loads. Workaround is a manual
merge into the Claude-Data file, which must be repeated after each rea setup refresh.
No effect observed on evidence integrity or process isolation. Other Windows editions and
Claude Desktop versions untested.

REA version

rea-agents 6.8.0 (npx; doctor identity cli_package_version 6.8.0)

Runtime and platform

Node 26.13.0; Windows Server 2025 x64; Claude Desktop MSIX Claude_pzs8sxrjxfjjc 4.16336.0.0; Ghidra 12.1.4 (not relevant)

Target and artifact context

not applicable

Interface

Package or setup

Earliest failure stage

Setup or provider admission

Relevant output or evidence

setup plan: CREATE Claude Desktop %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json
doctor: {"name":"registration:claude_desktop","ok":true,"classification":"healthy"} ; registrations[claude_desktop].state = "aligned"
Package-private Roaming\Claude listing: .user-data-left.claude_pzs8sxrjxfjjc, claude_desktop_config.json
Search of %USERPROFILE%\AppData (excluding Packages) for claude_desktop_config.json:
%LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\claude_desktop_config.json

Typed outcome or recovery expected

No response

Analysis or suspected cause

Hypothesis (not verified in REA source): Claude Desktop resolution in ClaudeDesktopConfigLocation
predates the 3.1623 data move and does not probe %LOCALAPPDATA%\Claude-Data\. The marker file name
suggests the app records that user data left the package location (unverified). When no package-private
config exists, setup creates one there, which the migrated app ignores.

Additional context

Related but distinct: #4278 (writes %APPDATA%\Claude), #4432 (AnthropicPBC.Claude_* / Claude-3p).
Same migration reported by other projects, e.g. jacob-bd/gemini-notebook-mcp-cli#378, IEZhu/Agents#270.

Originally created by @gougeoncat on GitHub (Nov 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8968 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Setup, packaging, or upgrade ### Observed behavior `rea setup --client claude_desktop` (rea-agents@6.8.0 via npx) wrote mcpServers.rea to %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json (plan action: CREATE). `rea doctor --client claude_desktop --json` then reported registration:claude_desktop ok/healthy, state "aligned". Claude Desktop (MSIX, package family Claude_pzs8sxrjxfjjc, version 4.16336.0.0) did not load the server: Settings > Developer showed "No servers added" after fully quitting and restarting the app (twice). Observed on disk: - The package-private Roaming\Claude folder contained only the setup-created config and a marker file `.user-data-left.claude_pzs8sxrjxfjjc` (timestamp ~10 min after setup). - %APPDATA%\Claude did not exist; no other Claude package under %LOCALAPPDATA%\Packages. - The config the app actually uses: %LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\claude_desktop_config.json (pre-existing, last written earlier the same day). Manually merging the same mcpServers.rea entry into the Claude-Data file made the server appear in Settings > Developer; binary_session returned normally and tools ran (Ghidra availability, WABT inspection). ### Reproduction 1. Windows, Claude Desktop MSIX (Claude_pzs8sxrjxfjjc, 4.16336.0.0) after its migration to %LOCALAPPDATA%\Claude-Data\\. 2. Quit Claude Desktop fully; run: npx rea-agents@6.8.0 setup --client claude_desktop ; approve. 3. Run: rea doctor --client claude_desktop --json -> registration reported healthy/aligned. 4. Start Claude Desktop -> Settings > Developer lists no MCP servers. Reproduced on 1 machine, consistently across 2 restarts. ### Expected behavior setup, doctor and uninstall should resolve the configuration file the installed Claude Desktop actually reads (%LOCALAPPDATA%\Claude-Data\claude_{publisher}\claude_desktop_config.json after the migration), or report the location as unresolved instead of reporting a healthy registration. Reference (not REA documentation): anthropics/claude-code#103860 reports that Claude Desktop 3.1623.0.0 moved MSIX app data to %LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\\. ### Impact and scope Silent failure: doctor reports a healthy registration the app never loads. Workaround is a manual merge into the Claude-Data file, which must be repeated after each `rea setup` refresh. No effect observed on evidence integrity or process isolation. Other Windows editions and Claude Desktop versions untested. ### REA version rea-agents 6.8.0 (npx; doctor identity cli_package_version 6.8.0) ### Runtime and platform Node 26.13.0; Windows Server 2025 x64; Claude Desktop MSIX Claude_pzs8sxrjxfjjc 4.16336.0.0; Ghidra 12.1.4 (not relevant) ### Target and artifact context not applicable ### Interface Package or setup ### Earliest failure stage Setup or provider admission ### Relevant output or evidence setup plan: CREATE Claude Desktop %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json doctor: {"name":"registration:claude_desktop","ok":true,"classification":"healthy"} ; registrations[claude_desktop].state = "aligned" Package-private Roaming\Claude listing: .user-data-left.claude_pzs8sxrjxfjjc, claude_desktop_config.json Search of %USERPROFILE%\AppData (excluding Packages) for claude_desktop_config.json: %LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\claude_desktop_config.json ### Typed outcome or recovery expected _No response_ ### Analysis or suspected cause Hypothesis (not verified in REA source): Claude Desktop resolution in ClaudeDesktopConfigLocation predates the 3.1623 data move and does not probe %LOCALAPPDATA%\Claude-Data\\. The marker file name suggests the app records that user data left the package location (unverified). When no package-private config exists, setup creates one there, which the migrated app ignores. ### Additional context Related but distinct: #4278 (writes %APPDATA%\Claude), #4432 (AnthropicPBC.Claude_* / Claude-3p). Same migration reported by other projects, e.g. jacob-bd/gemini-notebook-mcp-cli#378, IEZhu/Agents#270.

bsakaguchi added the

bug

triage

labels

2026-11-05 05:43:37 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#7869

No description provided.

Rows
Columns