Unclear Nothing shows any part of Claude Code currently asking for sandboxed git runs, so it is unclear whether this affects anyone yet.
When Claude Code runs git through its hardened git runner (a stricter way of launching git), it can now run it inside an operating-system sandbox. A sandbox is a restricted environment that limits what a program is allowed to touch. Before this change, hardened git always ran directly, with no sandbox.
Sandboxing can only be requested for a hardened run. If it is requested for a run that is not hardened, Claude Code refuses the run and reports run_not_hardened. When sandboxing is requested, git ends up in one of three states:
- Sandboxed: git runs inside the sandbox.
- Unsandboxed: git runs without the sandbox.
- Refused: git does not run at all.
When a sandboxed run fails, Claude Code returns exit code 126 and gives one of these reasons:
- Refused: the run was not allowed to start.
- Stopped: the run went over its time limit or its output limit.
- Output dropped: the run's output was thrown away.
There is now also an upper limit on how much output a hardened git run may produce.
This lets Claude Code put tighter limits on the git commands it runs for you. If git fails with exit code 126, the reason Claude Code gives tells you whether the sandbox refused the run, stopped it, or dropped its output.
Nothing shows any part of Claude Code currently asking for sandboxed git runs, so it is unclear whether this affects anyone yet.