Cmd. /config
Open settings or apply direct key/value settings (/settings).
Written and reviewed by Eric Han · Co-founder & CTO, reopt
Key takeaways
- Open settings or apply direct key/value settings (
/settings). - Check the input surface and availability before using the examples below.
Purpose
Open settings or apply direct key/value settings (/settings).
/config [key=value ...]Availability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | /settings |
| Documented minimum | Not specified |
| Reviewed against | 2026-10-23 · Claude Code 2.1.308 |
The installed command menu and account or organization settings determine availability.
Examples
/configEffects and persistence
Changes the selected settings at their supported scope. Options requiring confirmation must be handled in the settings interface.
Recent settings: maxProseWidth (v2.1.282+) caps the width of Claude's prose in wide terminals while tables and code blocks keep the full width. "attribution": false (v2.1.281+) hides all commit and PR attribution; older CLI versions skip a settings file that contains it, so keep the object form in files shared across versions.
From v2.1.302, use the Idle compaction row to disable or re-enable idle compaction; the persisted setting is idleCompaction.
Cautions
Use /config --help for supported inline settings. Options requiring confirmation must be changed through Settings. From v2.1.285, /config chrome=true directs you to the /config panel instead of enabling Claude in Chrome by default; /config chrome=false still turns it off. From v2.1.287, settings that cycle show ‹ › and step both ways with ←/→.