[DOCS] Ambiguous value type documentation for `disableBypassPermissionsMode`

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

The "Permission settings" table under the Settings files section.

Current Documentation

In the table row for disableBypassPermissionsMode:

Description: Set to "disable" to prevent bypassPermissions mode from being activated. This disables the --dangerously-skip-permissions command-line flag. See managed settings Example: "disable"

What's Wrong or Missing?

The documentation is ambiguous regarding the data type expected for this setting.

1. The setting name disableBypassPermissionsMode implies a Boolean flag (where one would typically set it to true to enable the restriction).
2. The description explicitly says 'Set to "disable"'.
3. The example shows the string literal "disable".

It is counter-intuitive for a variable named "disable..." to accept the value "disable". Users may be confused whether they should provide the boolean true or the string "disable". If this is an enum, it is unclear what other values might exist (e.g., is there an "enable" value?).

Since this is a security-critical setting for enterprise administrators, ambiguity here could result in misconfiguration (e.g., an admin sets it to true assuming standard JSON boolean logic, but the system ignores it because it expects a string).

Suggested Improvement

Please clarify the expected data type.

If the setting requires a Boolean:

Description: Set to true to prevent bypassPermissions mode from being activated... Example: true

If the setting strictly requires the string "disable":

Description: Set to the string "disable" to prevent bypassPermissions mode... (Note: This setting expects a string value, not a boolean).

Impact

High - Prevents users from using a feature

Additional Context

This ambiguity appears in the "Permission settings" table row. Clarifying this ensures that administrators deploying managed policies do not accidentally leave the --dangerously-skip-permissions flag enabled due to type errors in their managed-settings.json.