You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GitHub ActionsArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release
What
When Claude Code runs in GitHub Actions, it uses a sandbox (a fenced-off space that limits what commands can change) that blocks writes to the .claude settings folder. It used to protect one .claude folder path. It now works that path out from three different starting locations and protects every one it finds.
Why
Before, a .claude folder reached through a different starting point, such as a worktree (a second checkout of the same repository) or the repository root, could still be written from inside the sandbox.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which three starting locations are used.
