Configure the sandboxed Bash tool changedsandboxing
Nearest release: v2.1.322, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 10 Nov 2026 00:14 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 10 Nov 2026 00:37 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−0removed
From line
899
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits63to this page, all time
### A git command fails with `Unable to create '…/index.lock'`
The whole hunk
from line 899, old and new numbered
/
from line 899
899899
900900After the failure, Claude may [offer to rerun the command outside the sandbox](#the-unsandboxed-retry-escape-hatch). Approve that retry, or run the git command yourself in another terminal. If you've set `allowUnsandboxedCommands` to `false`, Claude can't offer the retry, so run the command yourself.
901901
902### A git command fails with `Unable to create '…/index.lock'`
903
904If you started Claude Code in a repository's subdirectory, this error can mean `.git` is outside [what sandboxed commands can write to](#filesystem-isolation). Start Claude Code from the repository root instead, or from the worktree's root in a [linked worktree](https://code.claude.com/docs/en/worktrees.md).
905
902906### A folder named `objects` or `refs` disappears after a command
903907
904908A top-level `objects` or `refs` folder that appeared during the session can be [deleted after a sandboxed command ends](#when-the-sandbox-deletes-head-objects-or-refs). It doesn't matter whether a command, Claude, or you created it. To keep a folder, leave something in it. If a `HEAD` file or symlink has been at the top level during the session, move it away, then restart every Claude Code session open there.
No line in this hunk matches that.