Claude Code: Change Any Setting Inline With /config key=value

A faster way to configure Claude Code

Claude Code 2.1.181 introduces the /config key=value inline syntax. Until now, changing a setting meant leaving the conversation, opening the right settings.json, editing it, and reloading. That friction discouraged quick, ad-hoc adjustments and pushed people toward fixed global configs.

With the new syntax, any valid settings key can be set straight from the prompt. The headline example is /config thinking=false, a natural thing to toggle mid-session when you want faster responses without extended reasoning. The same mechanism applies to any configurable setting, so it doubles as a general-purpose escape hatch for changes that feel temporary or experimental.

Where it works

The syntax is available across all three execution contexts:

• Interactive mode, the standard terminal session
• Non-interactive -p mode, for headless prompts used in scripts
• Remote Control, for sessions driven by automation or another Claude instance

That consistency matters. Teams running Claude Code in automated pipelines can inject setting overrides at the prompt level instead of managing a separate config file per environment.

Why it matters

Settings in Claude Code influence everything from effort level to tool permissions to model selection. Adjusting one inline, in the same conversational flow, removes a context switch that power users have noted as the settings surface has grown. It also makes settings more discoverable: once you know you can type /config, you are more likely to explore what is configurable rather than treating the settings files as set and forget.