[BUG] Enterprise Managed Settings - sandbox:true does not get picked up. But sandbox:true in ~/.claude/settings.json works to default sandbox on

Resolved 💬 4 comments Opened May 1, 2026 by markalanevans Closed May 5, 2026

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?

Version: 2.1.112

We are working on deploying a manage-settings.json file

Having this

"sandbox": {
    "enabled": true,
}

If we put that in managed-settings.json file, claude does not adhere to that rule.

Placing that same setting in the
~/.claude/settings.json

And claude correctly starts by default in sandbox mode.

What Should Happen?

Claude should always start in sandbox mode.

Error Messages/Logs

None. 
But I know the managed-settings.json file is being read because i can see the announcments that i have placed in it, displaying in claude.

Steps to Reproduce

In your managed-settings file

set sandbox.enabled = true

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Version: 2.1.112

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗