What
Setting a value with /config key=value now distinguishes a setting Claude Code refused to change from one it tried and failed to save. Refusals show their own message verbatim. On remote sessions, save failures are replaced with "Couldn't save this setting (detail withheld on this connection)." so local paths and error text do not leave the machine. Invalid keys and values are now escaped before being echoed back.
Details
- The withholding applies only to save failures, and only when the session is remote; locally the full detail is still shown.
Usage
/config editorMode=vimEvidence
Couldn't save this setting (detail withheld on this connection).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/config
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Telemetry and egress touched a line naming /config after this was published.
With `disableEssentialTelemetry`, `disableNonessentialTelemetry`, `disableNonessentialServices`, and `disableAutoUpdates` all set to `true`, the desktop application makes **no outbound connections to Anthropic-operated hosts at runtime**. …third-party/claude-desktop/telemetry see the edit
Confirmed since
Anthropic's documentation has since written up /config, on MCP, plugins, skills, and hooks.
| `.mcp.json` | MCP servers bundled with this plugin. A JSON object keyed by server name: `{"mcpServers": {"<name>": {"type": "http", "url": "...", "oauth": true}}}`. A remote entry uses `type` (`http` or `sse`), not `transport`, and suppo…third-party/claude-desktop/extensions see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /config, on MCP, plugins, skills, and hooks.