You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SandboxArea: what it touches
Internal ChangesKind: in v2.1.277,
Bug FixesSection of the release
What
When Claude Code builds a sandboxed shell command, if sandboxing is enabled and the command text references the literal string TMPDIR but no explicit sandbox tmp-dir override exists, it now computes a fallback tmp-dir value (called tmpDirBackstop) and passes it through when building the command.
That value is then used in the generated shell preamble: if tmpDirBackstop is set, the shell setup exports TMPDIR from it, but only if TMPDIR isn't already set in the environment.
Why
This prevents commands that rely on TMPDIR from breaking inside a sandbox where that variable might otherwise be unset, without overriding a TMPDIR the environment already provides.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up TMPDIR, on Explore the .claude directory.| `image-cache/<session>/` | Attached images saved by Claude Code v2.1.274 and earlier. Later versions save pasted and attached images outside `~/.claude`, in an `images/` directory for each session under the temp directory that [`CLAUDE_C…claude-directorysee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up TMPDIR, on Explore the .claude directory.
