[BUG] There is no indication to the user when Claude sets `dangerouslyDisableSandbox: true`

Open 💬 0 comments Opened Jul 1, 2026 by dvg-p4

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

The permissions prompt for bash commands gives no indication when Claude has set the dangerouslyDisableSandbox: true flag on the tool call. "Claude is attempting to bypass sandboxing" is eminently relevant information that a user ought to know before granting Claude permission to run a command.

What Should Happen?

The permissions prompt should indicate something to the effect of "Warning: Claude is requesting to run this command outside the sandbox". Ideally, the tool would require Claude to explain why it needs to run outside the sandbox.

Error Messages/Logs

Steps to Reproduce

  1. Ask Claude to run a bash command with dangerouslyDisableSandbox: true
  2. Observe the lack of any indication thereof in the permissions prompt (unless Claude proactively decides to note it in its description)

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

v2.1.198

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗