Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.181 Home All releases olderv2.1.179 v2.1.182newer
Claude Code v2.1.181

/config key=value — Set Settings from the Command Line

What

/config now accepts key=value pairs as arguments, letting you set configuration settings without opening the interactive panel.

Usage
/config theme=dark
/config model=claude-opus-4-5 theme=dark
/config key=value key2=value2
Details
  • Works in both interactive mode and non-interactive (--print) mode.
  • Invalid keys produce: "<key> isn't a /config setting. Run /config to see what's available." and "can't be set with key=value — open /config to change it from the panel." for panel-only settings.
  • Running /config with no arguments still opens the interactive settings panel.
  • Some settings (like model and theme) have dedicated slash commands (/model, /theme) that are also surfaced in the error hint.
Evidence

/config handler (search for "Usage: /config key=value [key=value ...]") — xqp handler at line ~570976; key→command map (search for "outputStyle") — Cqp map at line ~570945

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.181 →