{"version":"2.1.282","anchor":"github-actions-scrub-sandbox-write-protects-several-canonica","canonical_anchor":"github-actions-scrub-sandbox-write-protects-several-canonica","heading":"GitHub Actions sandbox now protects the .claude folder from every root","tier":"notice","area":"GitHub Actions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/github-actions-scrub-sandbox-write-protects-several-canonica","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### GitHub Actions sandbox now protects the .claude folder from every root\n\nIn GitHub Actions, the sandbox now works out the `.claude` folder from three starting locations and write-protects each copy it finds\n\n**Unclear.** It is not clear which three starting locations are used.\n\n**What**\n\nWhen 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.\n\n**Why**\n\nBefore, 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.\n\n- Area: GitHub Actions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}