Add local-project-setup.sh for cross-repo sandbox access - #39
Merged
technicalpickles merged 2 commits intoSep 14, 2026
Merged
Conversation
…d-project-setup.sh A cq audit of a week of unsandboxed Bash commands found cross-repo git writes (a pickleclaw session cd-ing into picklehome, etc.) as the single biggest cause of dangerouslyDisableSandbox usage: the sandbox only grants write access to a session's own working directory, so a git command against a sibling repo fails with Operation not permitted and falls back to unsandboxed every time. local-project-setup.sh writes permissions.additionalDirectories into a repo's gitignored .claude/settings.local.json, driven by a new claude/cross-repo-access.jsonc manifest. It's the local counterpart to the existing claude-project-setup.sh, renamed to cloud-project-setup.sh to make the split legible: cloud writes what a Claude Code web session needs (must be committed), local writes what only this machine needs (must not be). See ADR 0057, and the note added to ADR 0041. Already run against pickleclaw and picklehome to fix the actual problem. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Got renamed via git mv but the internal --help/error text edits were staged before the rename landed, so they never made it into the first commit. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
technicalpickles
deleted the
claude/unsandboxed-sessions-review-303862
branch
September 14, 2026 13:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
local-project-setup.sh+claude/cross-repo-access.jsonc: grants a repo's Claude Code sessions filesystem access to sibling repos it routinely reaches into directly (e.g.pickleclawrunning git/deploy commands againstpicklehome), viapermissions.additionalDirectoriesin the target's gitignored.claude/settings.local.json. See ADR 0057 for the audit that motivated this (cross-repo git writes were the single biggest cause ofdangerouslyDisableSandboxusage over a week of sessions).claude-project-setup.shtocloud-project-setup.shso the split is legible: cloud writes what a Claude Code web session needs (committed settings), local writes what only this machine needs (gitignored settings). ADR 0041 gets a short note pointing at the rename, decision unchanged.pickleclawandpicklehometo fix the actual problem those repos were hitting.Test plan
npm run lintpasses../local-project-setup.sh <dir> --dry-runverified against a repo with entries, a repo without, and--help.pickleclaw/.claude/settings.local.jsonandpicklehome/.claude/settings.local.jsonnow carrypermissions.additionalDirectoriespointing at each other (andpickleclawatopenclaw-workspace).