Bash tool sandbox resolves script path to its pre-reorg location (stale bind mount)

Status Open
Reported on v2.1.220
Maintainer reply None cached
Activity 0 comments · opened Aug 6, 2026

Running a script via the Bash tool with an absolute path fails inside the sandbox, resolving to a path that hasn't existed on disk for over a week (moved via mv/git mv days earlier).

Repro:

bash "/home/calin/Desktop/scripts/sync/vault-git-push.sh"

Sandboxed → bash: /home/calin/.claude/scripts/vault-git-push.sh: No such file or directory (old pre-move path)
Same command with dangerouslyDisableSandbox: true → runs clean, exit 0.

Ruled out: the script itself (no self-reference to the old path), the Read/ls tools (see the real filesystem fine — only bash <path>-style exec is affected), shell aliases/functions (none set).

Looks like the sandbox's bind-mount view is caching a path mapping from before a folder move and never invalidating it. Affects any interactive script execution under the moved directory; cron/launchd jobs outside the harness are unaffected.

Claude Code version: 2.1.220
OS: Linux 7.0.0-28-generic

View original on GitHub ↗