[DOCS] `/config key=value` docs conflict on shorthand-key discovery and omit `/config --help`

Documentation Type

Unclear/confusing documentation

Documentation Location

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

Section/Topic

The /config [key=value ...] row in Commands, plus the parallel direct-setting notes in Settings, Headless, and Remote Control.

Current Documentation

The commands page currently says:

From v2.1.181, pass one or more key=value pairs to set a setting directly without opening the interface, for example /config thinking=false. The key=value form also works in non-interactive mode (-p) and from Remote Control. Run /config help to list the keys you can set. Alias: /settings

The Remote Control page says:

/config, from v2.1.181: pass key=value to set a setting, or run it with no argument to list the keys you can set.

The Settings page says:

From v2.1.181, you can change a single option without opening the interface by passing key=value to /config, for example /config verbose=true.

The Headless page says:

To change a setting from a -p invocation, pass key=value to /config, for example /config thinking=false.

What's Wrong or Missing?

A. The v2.1.183 --help discovery path is not documented on the pages that teach /config key=value

The v2.1.183 changelog says Claude Code added /config --help to list all available shorthand keys for the key=value form. None of the pages above mention /config --help, so the released key-discovery path is currently only visible in the changelog.

B. The current pages give conflicting instructions about how to list valid keys

Commands says to run /config help, Remote Control says to run /config with no argument, and Settings/Headless show key=value examples without any discovery step. Users cannot tell whether these are equivalent aliases, surface-specific behaviors, or stale guidance.

C. The docs never explain how shorthand keys relate to the settings reference

The release note calls these /config key=value names "shorthand keys", but the main settings reference lists full setting names. The current docs do not explain how readers should discover the accepted shorthand forms before using direct assignments like /config verbose=true or /config thinking=false.

Suggested Improvement

Update the Commands row to explicitly document the new discovery flow, for example:

To see the available shorthand keys for /config key=value, run /config --help.

Then make the related pages consistent:

1. Settings and Headless should link to the same /config --help discovery step before their key=value examples.
2. Remote Control should clarify whether bare /config still lists keys there, or whether /config --help is the canonical cross-surface form.
3. If /config help remains supported, document it as an alias instead of leaving it as the only instruction on one page.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/commands | 63 | /config [key=value ...] row tells readers to run /config help |
| https://code.claude.com/docs/en/remote-control | 204 | Remote Control says to run /config with no argument to list keys |
| https://code.claude.com/docs/en/settings | 9 | Introduces direct key=value settings without showing how to list shorthand keys |
| https://code.claude.com/docs/en/headless | 215 | Shows /config thinking=false in -p mode without pointing to key-discovery help |

Total scope: 4 pages affected

Version: Claude Code v2.1.183

Changelog cross-reference: https://code.claude.com/docs/en/changelog documents the release note "Added /config --help to list all available shorthand keys for /config key=value."