Its theme's rank, 14 days: 17 on the Claude Code sheet
3 people reported
All time, since Oct 23.
Eval sandbox blocks workspace writes
“Sandboxed Bash can write to the run's working directory, as the docs say ("Writes are confined to the run's workspace"), wherever TMPDIR points.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/20653/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Plugin eval sandbox denies Bash writes in its own workspace on Linux. Each run's workspace sits under /tmp (default TMPDIR) and writes fail, while the sandbox denyWrite list covers /tmp; Write and Edit still work.
Is this your bug?
File my report- Where
- plugin eval sandbox
- Error text
/bin/bash: line 1: out.txt: Read-only file system- Versions
- 2.1.309 to 2.1.316
- Platforms
- Linux
- How bad
- Breaks a normal workflow. Some reports say it used to work.
Part of: Linux sandbox fails every command3 bugs
Original reports3, newest first
- plugin eval on Linux: run sandbox denies writes to its own working directory when TMPDIR is under /tmp#106687
- plugin eval: sandboxed Bash cannot write the run workspace when TMPDIR is under /tmp ("Read-only file system")#104797
- plugin eval (Linux, 2.1.304–2.1.309): sandbox denies every write in the agent's workspace — //tmp denyWrite covers the /tmp/claude-eval-* root#104631