Skip to content

Claude Code Settings: All 46 /config Options, Tested

Claude Code's /config screen has 46 options. About half are about how the terminal looks. Eight change what it costs and what Claude does while you're not watching. I tested the ones that surprised me.

"Claude Code settings: 46 options, tested" beside a terminal running /config key=value commands: verbose=true is saved, thinking=false is refused because thinking can't be turned off for Opus 5.5, and autoContinueAtUsageLimit=true is refused.
Table of Contents8 sections

Get my next blog post first

Real tests on Claude and SEO tools, with the numbers and what failed. About once a week.

Unsubscribe anytime. Privacy

On 24 October I typed /config in Claude Code to change one thing. The list ran off the bottom of the screen, and I didn't know what half of it did.

So I went through all 46 options in Claude Code 2.1.311.

The short version: about half of the 46 change how the terminal looks or feels. Eight change what you pay, or what Claude does while you're away.

I checked each against Anthropic's docs and tested the odd ones.

And one, Thinking mode, does nothing at all on Opus 5.5.

Short on time? Jump to the eight that matter, or look one up in the full table.

Key Takeaways

  • Eight options change cost or unattended work: auto-compact, continue at usage limit, permission mode, auto mode during plan, workflows, Chrome, Remote Control and the question timeout.
  • Thinking mode can't be switched off on Opus 5.5. I tried from the command line and Claude Code refused.
  • /config key=value works without opening the menu, but not for every setting.
  • Some values are per folder. The same option showed true in one project and false in another.
  • A project file can't put you in auto or bypass mode. The menu showed Bypass, and the session still started in manual mode.

How to open it, and where it saves

Type /config in a Claude Code session and open the Config tab, the third of five: Settings, Status, Config, Usage and Stats.

Arrow down, Enter or Space to change a row, Esc to close.

The Config tab in Claude Code 2.1.311 on 5 November 2026, the first 23 of 46 options with my values, from Auto-compact true down to Use auto mode during plan true.

Changing a row writes a file for you. Which file depends on the option, and it matters when a value seems to ignore you:

FileWhat lands thereExamples from the list
~/.claude/settings.jsonMost options, for every projectAuto-compact, Editor mode, Default permission mode
~/.claude.jsonOptions Claude Code calls global configCopy on select, Workflow size, Claude in Chrome
.claude/settings.local.jsonA few options, only for the folder you're inOutput style; Reduce motion landed here for me

Anthropic's settings page has the full order of which file wins.

You can also skip the menu. Pass key=value and Claude Code saves it straight away, even from a script:

$ claude -p "/config verbose=true"
Set Verbose output to true
$ claude -p "/config alwaysThinkingEnabled=false"
alwaysThinkingEnabled isn't a /config setting. Run /config to see what's available.

It took about 4 seconds. It takes the menu's own option names, and refuses a few changes on purpose, like the one below.

The eight that matter

These are the ones I'd read before touching anything else. Each one changes what you pay or what happens when you aren't looking.

OptionDefaultMineWhat it really does
Auto-compactononSummarises the chat near the context limit. Turn it off and idle compaction goes off too
Continue automatically at usage limitononWhen a claude.ai plan limit stops an open session, waits for the reset and carries on by itself
Default permission modedepends on where you run itAutoWhich mode a new session starts in, from asking every time to approving everything
Use auto mode during planononIn plan mode, a classifier can approve shell commands without asking you
Dynamic workflows and Ultracode triggerononLets Claude run many agents at once; typing "ultracode" starts one
Claude in Chrome enabled by defaultoffonEvery interactive session starts with the browser tools loaded
Enable Remote Control for all sessionsoffonEvery interactive session can be driven from the Claude app on your phone
Question auto-continue timeoutneverneverAfter 60 seconds to 10 minutes, an unanswered question goes ahead with whatever you'd ticked

Continue at usage limit is the one to know about. Anthropic's docs say the setting "grants unattended execution". That's why the shortcut refuses to switch it on:

$ claude -p "/config autoContinueAtUsageLimit=true"
Continue automatically at usage limit can't be enabled with key=value
open /config to change it from the panel.

I keep it on, because I leave long jobs running while I'm out.

Dynamic workflows cost more than they look. One run "can use meaningfully more tokens" than the same task in a normal chat, the docs say.

And the size option next to it is only "advice, not an enforced cap".

Chrome by default has a price too: it "increases context usage", because the browser tools always load. Mine stays on. I read Keyword Planner in the browser for most posts, like this Semrush comparison.

Remote Control is how I follow a long session from my phone. It only connects your own account. Both push options need it.

What I found when I tested them

Thinking mode shows "true", and you can't change it on Opus 5.5. The row has a note under it, and the shortcut says the same:

$ claude -p "/config thinking=false"
Couldn't save Thinking mode: Thinking can't be turned off for Opus 5.5

Anthropic's own cost page still suggests "disabling thinking in /config" to spend less. On Opus 5.5, Sonnet 5.5 and Haiku 5.5, it does nothing.

Use /effort for that.

Some values are per folder. Reduce motion read true in saeedseo.com and false in mersa.biz, same Mac, same day.

The permission row can show a mode you aren't in. In mersa.biz the menu read "Bypass Permissions", from the project file. The footer said "manual mode on".

The documented rule: auto and bypass only take effect from your own user settings, never a project file.

Why it fell back to manual and not to my Auto, the docs don't say. I don't know either.

One more trap: Rewind code doesn't track files that only Bash changed. A file Claude already edited is covered, even if Bash touches it later.

All 46 options

Here's every row on the Config tab in 2.1.311, top to bottom, as a normal terminal shows it, with my value and the default:

#OptionMineDefaultWhat it does
1Auto-compacttruetrueSummarises the conversation when context gets close to the limit
2Idle compactiontruetrueCompacts a long chat you've left idle for about an hour
3Continue automatically at usage limittruetrueCarries on with the task once a plan limit resets
4Switch models when a message is flaggedSwitch automaticallySwitch automaticallyMoves to a fallback model when a safety check flags a request, or asks you first
5Show tipstruetrueFeature tips in the spinner line
6Claude-drafted feedbacknotifynotifyClaude can queue bug reports about Claude Code for you to review; shows only where the feature is on
7Reduce motiontruefalseTurns off the spinner, shimmer and flash effects
8Thinking modetruetrueExtended thinking; locked on for Opus 5.5
9Prompt suggestionstruetrueGrey guesses of your next prompt (each counts toward your usage)
10Session recaptruetrueA one-line recap when you come back after a few minutes
11Rewind code (checkpoints)truetrueSnapshots files before each edit so /rewind can undo it
12Dynamic workflowstrueon (off on Pro)Lets Claude run many agents from one script
13Ultracode keyword triggertruetrueTyping "ultracode" in a prompt starts a workflow
14Dynamic workflow sizemediummedium (small on Pro)Agents per workflow: small under 5, medium under 10, large under 50
15Artifactstrueyour account's settingLets Claude publish output as a private web page on claude.ai
16Verbose outputfalsefalseShows every tool call's full input and output
17Terminal progress bartruetrueA busy indicator on the tab, in iTerm2, Ghostty and ConEmu
18Show turn durationtruetrueThe "Cooked for 1m 6s" line after each answer
19Time formatautoauto12-hour, 24-hour or UTC
20Default permission modeAutodepends on where you run itThe mode new sessions start in
21Worktree base reffreshfreshNew worktrees branch from the remote's main, or from your local HEAD
22Use auto mode during plantruetrueAuto-approves shell commands while planning
23Respect .gitignore in file pickertruetrueLeaves ignored files out of the @ picker
24Skip the /copy pickerfalsefalse/copy takes the whole answer without asking which block
25Copy on selectfalsetrueCopies text as soon as you select it (fullscreen mode)
26Auto-scrolltruetrueFollows new output to the bottom (fullscreen mode)
27Open agents view by defaultfalsefalseclaude with no arguments opens agent view
28← opens agentstruetrueLeft arrow on an empty prompt opens agent view
29Auto-update channellatestlatestlatest, or stable (about a week behind)
30ThemeAuto (match terminal)darkColours; auto follows your terminal
31Local notificationsTerminal BellautoHow it alerts you on this computer
32Push when actions requiredtruefalsePhone alert when a prompt waits (needs Remote Control)
33Push when Claude decidestruefalsePhone alert when Claude thinks it's worth one, like a long task ending
34Output styledefaultdefaultChanges tone and format, such as Explanatory or Learning
35LanguageDefault (English)EnglishThe language Claude answers in (not in the docs as a menu row)
36Editor modevimnormalVim keys in the prompt box
37Question auto-continue timeoutneverneverLets an unanswered question go ahead after a set time
38Show last response in external editorfalsefalseCtrl+G opens your editor with Claude's last answer as comments
39Show PR status footertruetrueThe open pull request's badge in the footer
40ModelDefault (recommended)your account's defaultThe model new sessions start with
41Auto-connect to IDE (external terminal)falsefalseJoins a running VS Code or JetBrains on start
42Claude in Chrome enabled by defaulttruefalseBrowser tools in every session
43Enable Remote Control for all sessionstrueoffEvery session reachable from the Claude app
44Dialog expirydefault5 minutesHow long a dialog sent to your phone waits
45Messages from your other sessionsdefaultdecides per messageAccept, hold or refuse messages from your other sessions
46Project instructionsclaude-md-or-agents-mdclaude-md-or-agents-mdReads CLAUDE.md, or AGENTS.md when there's no CLAUDE.md

Each row's key and file is in Anthropic's settings reference.

Two rows aren't in the docs as menu rows: Language, and Worktree base ref. I matched that one to its key through my own settings.json.

The other four tabs

/status opens the same screen on the Status tab: version, model, account, and every settings file loaded. Which file set which value, it doesn't say.

Usage is /usage: plan limits, session cost and activity. On a subscription, the cost figure isn't your bill, the docs say. Stats is where /stats lands, and Settings is the first tab.

What I'd change first

  1. Check Default permission mode in ~/.claude/settings.json. It decides how often you get asked, though an ask rule on an MCP tool still prompts in auto mode.
  2. Decide on Continue at usage limit before you leave a long job running.
  3. Turn off Claude in Chrome by default if you don't use the browser most days. It costs context in every session.
  4. Leave Rewind code on, and still commit before anything risky. Files only Bash touched aren't in it.
  5. Skip Thinking mode on Opus 5.5. Use /effort instead.

Once it's set up, test it on a job you already know the answer to, like my Claude Code vs Codex run on five SEO jobs.

Common Questions

Where does Claude Code save the settings I change in /config?

Mostly in ~/.claude/settings.json, for every project. Options Claude Code calls global config, such as Copy on select, go to ~/.claude.json, and a few, such as Output style, go to the project's .claude/settings.local.json.

Can I change a Claude Code setting without opening the /config menu?

Yes. Type /config verbose=true, or run claude -p "/config verbose=true" from a script. It saved in about 4 seconds in my test, but Claude Code refuses settings that would let it run unattended.

Can I turn off thinking in Claude Code to save money on Opus 5.5?

No. Claude Code 2.1.311 answered "Thinking can't be turned off for Opus 5.5". On Opus 5.5, Sonnet 5.5 and Haiku 5.5, lower the effort level with /effort instead.

Why does my Claude Code permission mode not match what /config shows?

A project's settings file can't start a session in auto or bypass mode. In my mersa.biz folder, /config showed Bypass Permissions while the session ran in manual mode. Set those two modes in ~/.claude/settings.json.

Want my next blog post before anyone else?

I run real tests on Claude and SEO tools, like 10 voice models on one Mac or 25 audits of a site with 20 planted problems. You get the numbers, including what failed. One email per post, about once a week.

Unsubscribe anytime. Privacy

Hiring for AI search? Let’s talk.

Email me the job description, or book thirty minutes now. You’ll hear back within one working day.

Put your email and confirm it from your inbox. The file comes straight after.

You'll also get new posts, about once a week. Unsubscribe anytime. Privacy