[DOCS] Inconsistent casing: prose uses snake_case `allow_unsandboxed_commands` but setting key is camelCase

Resolved 💬 4 comments Opened Jan 24, 2026 by coygeek Closed Feb 27, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://platform.claude.com/docs/en/agent-sdk/python

Section/Topic

"Permissions Fallback for Unsandboxed Commands" warning section (near the end of the Sandbox Configuration section)

Current Documentation

The warning text uses snake_case:

If permission_mode is set to bypassPermissions and allow_unsandboxed_commands is enabled, the model can autonomously execute commands outside the sandbox without any approval prompts.

But the actual setting key (documented in settings.json and the sandboxing page) uses camelCase:

"allowUnsandboxedCommands": false

What's Wrong or Missing?

The documentation mixes camelCase (the actual setting key) with snake_case (in the warning prose). This creates ambiguity:

  • Users reading the warning may try to use allow_unsandboxed_commands as the setting key
  • The actual key is allowUnsandboxedCommands (camelCase)
  • Using the wrong key in settings.json will silently fail (the setting won't be recognized)

This is particularly confusing because:

  1. Python conventions favor snake_case
  2. The SDK Python parameters use snake_case (e.g., permission_mode)
  3. But JSON settings use camelCase (matching the underlying configuration format)

Suggested Improvement

Standardize the prose to match the actual setting key:

If permission_mode is set to bypassPermissions and allowUnsandboxedCommands is enabled, the model can autonomously execute commands outside the sandbox without any approval prompts.

Or add a clarifying note:

Note: Sandbox settings keys use camelCase (e.g., allowUnsandboxedCommands) to match the JSON configuration format, even when referenced in Python documentation.

Impact

High - Prevents users from using a feature

Additional Context

View original on GitHub ↗

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