Rank, 14 days: 78 on the Claude Code sheet
5 people reported

All time, since Oct 20, including 3 thumbs-up on GitHub.

Excluded commands stay sandboxed

“There is no setting that makes an excluded tool run unsandboxed in every call shape.”

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/19848/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

Excluded commands still run sandboxed in chained or compound Bash calls. Only a single plain command leaves the sandbox; with cd, &&, a pipe, a heredoc, or flags like -C, the excluded tool still runs sandboxed.

Is this your bug?

File my report
Where
Bash tool sandbox
Error text
deny network-outbound github.com:443
Versions
2.1.286 to 2.1.310
Platforms
macOS
How bad
Breaks a normal workflow.

Not quite your bug?

  1. excludedCommands ignored by sandbox9 people
  2. Redirected excluded command sandboxed9 people
  3. excludedCommands glob stops matching single git commands with a flag before the subcommand9 people

Original reports2, newest first

  1. update-config: say that sandbox.excludedCommands matches only a single plain command#105115
  2. sandbox.excludedCommands can't unsandbox an excluded tool in chained or cd calls, so git breaks under the sandbox#103677

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.