Multiple open anthropics/claude-code GitHub issues (#26073, #29100, #38830) report that on Windows MSIX installs, edits to the normal %APPDATA% config path are silently ignored because the running app reads from a virtualized path:
Users edit the file BCC points at, restart, and nothing changes — with no error. Uniquely frustrating failure mode.
Proposed solution
On Windows, detect an MSIX install by checking for %LOCALAPPDATA%\Packages\Claude_*. If found:
Either point discovery directly at the virtualized path, OR
If both paths exist, show an explicit warning that there are two candidate config files and only one is live.
Note: Cannot be tested locally on macOS. The detection logic should be unit-tested by mocking the filesystem; add a note to the PR that manual Windows verification is needed before merge.
Acceptance criteria
On an MSIX install, BCC edits the path Claude actually reads.
On a non-MSIX install, behavior is unchanged.
Detection logic has unit tests (filesystem-mocked, cross-platform runnable).
PR notes that Windows smoke-test is needed.
Relevant code
bcc_core.py::app_support_base (line 74)
bcc_core.py::discover_profiles (line 83)
## Problem
Multiple open anthropics/claude-code GitHub issues (#26073, #29100, #38830) report that on Windows MSIX installs, edits to the normal `%APPDATA%` config path are silently ignored because the running app reads from a virtualized path:
```
%LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude\
```
Users edit the file BCC points at, restart, and nothing changes — with no error. Uniquely frustrating failure mode.
## Proposed solution
On Windows, detect an MSIX install by checking for `%LOCALAPPDATA%\Packages\Claude_*`. If found:
- Either point discovery directly at the virtualized path, OR
- If both paths exist, show an explicit warning that there are two candidate config files and only one is live.
**Note:** Cannot be tested locally on macOS. The detection logic should be unit-tested by mocking the filesystem; add a note to the PR that manual Windows verification is needed before merge.
## Acceptance criteria
- On an MSIX install, BCC edits the path Claude actually reads.
- On a non-MSIX install, behavior is unchanged.
- Detection logic has unit tests (filesystem-mocked, cross-platform runnable).
- PR notes that Windows smoke-test is needed.
## Relevant code
- `bcc_core.py::app_support_base` (line 74)
- `bcc_core.py::discover_profiles` (line 83)
the_og
added the P1 label 2026-07-02 00:50:35 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Multiple open anthropics/claude-code GitHub issues (#26073, #29100, #38830) report that on Windows MSIX installs, edits to the normal
%APPDATA%config path are silently ignored because the running app reads from a virtualized path:Users edit the file BCC points at, restart, and nothing changes — with no error. Uniquely frustrating failure mode.
Proposed solution
On Windows, detect an MSIX install by checking for
%LOCALAPPDATA%\Packages\Claude_*. If found:Note: Cannot be tested locally on macOS. The detection logic should be unit-tested by mocking the filesystem; add a note to the PR that manual Windows verification is needed before merge.
Acceptance criteria
Relevant code
bcc_core.py::app_support_base(line 74)bcc_core.py::discover_profiles(line 83)the_og referenced this issue2026-08-12 02:34:47 -04:00