All settings changedsettings-reference
Nearest release: v2.1.239, published 9 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+9added
Lines−22removed
From line
560
where the diff opens
First seen
21 Aug 2026
this site's first read of the page
Recorded edits147to this page, all time
## Scopes
The whole hunk
from line 560, old and new numbered
/
This page is larger than the 256 KiB this site keeps, so one side of the diff below stops where the stored text does.
from line 560
560560
561561<BackToIndex href="#all-settings" label="Back to index" />
562562
563This reference page lists each key Claude Code reads from a settings file, plus the [short group of keys](#global-config-settings) it keeps in `~/.claude.json` instead.
563This reference page lists each key Claude Code reads from a settings file, plus the [short group of keys](#global-config-settings) it keeps in `~/.claude.json` instead. To pick a file, or check precedence, start with [Claude Code settings](/docs/en/settings).
564564
565Use the [index](#all-settings) to find a key by name or purpose and to see its topic and scope, then open the key's linked entry for what it lets you do, where Claude Code reads it from, its type and default, and a minimal example to paste.
566
567For how to apply these settings, which settings file to use, and which value Claude Code uses when a key is set in more than one place, see [Claude Code settings](/docs/en/settings).
568
569## Scopes
570
571Claude Code reads settings from four files, and not every key works in every file. The **Scope** of a key names the files that can set it.
572
573* **User**: `~/.claude/settings.json`. Yours, in every project.
574* **Project**: `.claude/settings.json`. Checked into the repository, so everyone who clones it gets these settings.
575* **Local**: `.claude/settings.local.json`. Yours, in this project only. Claude Code keeps it out of git when it creates the file.
576* **Managed**: settings your organization deploys; see [Managed settings](/docs/en/managed-settings).
577
578`Any file` means all four. The `--settings` flag isn't a scope: it's a command line override that sits above the user, project, and local files and below managed settings in [settings precedence](/docs/en/settings#settings-precedence), and an entry says so when the flag is treated differently for its key. `Global config` keys aren't in a settings file at all: Claude Code keeps them in `~/.claude.json` and writes them when you change one in `/config`.
579
580565<span id="available-settings" />
581566
567<span id="scopes" />
568
582569## All settings
583570
584Every key, grouped by topic below and listed here in one table. Filter the table by a key name or a word from its purpose, read the Scope column for which files can set the key, then follow the link to its entry.
571Every key below links to its entry. Scope lists the [files](/docs/en/settings#settings-files-and-who-they-affect) it can go in: `User` is `~/.claude/settings.json`, `Project` is `.claude/settings.json`, `Local` is `.claude/settings.local.json`, and `Managed` is [what your organization deploys](/docs/en/managed-settings). `Any file` means all four, and `Global config` means [`~/.claude.json`](#global-config-settings).
585572
586573<ReferenceFilter
587574 noun="settings"
from line 2805
28182805}
28192806```
28202807
2821See [Make Ctrl+W delete back to whitespace](/docs/en/interactive-mode#make-ctrl-w-delete-back-to-whitespace). Requires Claude Code v2.1.238 or later.
2808See [Make editing keys follow readline conventions](/docs/en/interactive-mode#make-ctrl-w-delete-back-to-whitespace) for the per-key behavior.
28222809
28232810### `prefersReducedMotion`
28242811
from line 3103
31163103* **Type**: string, one of:
31173104 * `"default"`: the classic main-screen renderer
31183105 * `"fullscreen"`: the flicker-free alt-screen renderer with virtualized scrollback
3119* **Default**: unset, so Claude Code picks the renderer by rollout: fullscreen if you first used Claude Code on or after May 6, 2026, otherwise the classic renderer
3106* **Default**: unset, so Claude Code [picks the renderer for you](/docs/en/fullscreen#fullscreen-by-default)
31203107* **Per-session overrides**: [`CLAUDE_CODE_NO_FLICKER`](/docs/en/env-vars) and [`CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN`](/docs/en/env-vars) take precedence over this key for one session: `CLAUDE_CODE_NO_FLICKER=1` turns fullscreen on, and `CLAUDE_CODE_NO_FLICKER=0` or `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1` turns it off; when both are set, Claude Code turns it off
31213108
31223109```json settings.json theme={null}
from line 3662
36753662
36763663### `allowedChannelPlugins`
36773664
3678Choose which
3665Choose which [channel](/docs/en/channels) plugins can push messages into sessions in your organization. When you set it, Claude Code uses your list in place of the default Anthropic allowlist; each entry names a plugin and the marketplace it comes from.
3666
3667* **Scope**: [`Managed`](#scopes)
3668* **Type**: array of objects, each with `marketplace` and `plugin` strings
3669* **Default**: unset, so Claude Code uses the default Anthropic allowlist
3670
3671This example turns channels on and allows only the Telegram plugin from the official Anthropic marketplace:
3672
3673```json managed-settings.json theme={null}
3674{
3675 "channelsEnabled": true,
3676 "allowedChannelPlugins": [
3677 { "marketplace": "claude-plugins-official", "plugin": "telegram" }
3678 ]
3679}
3680```
3681
3682An empty array blocks every channel plugin. This key takes effect once channels pass the [`channelsEnabled`](#channelsenabled) gate for the account: on Team and Enterprise plans, and on Console accounts with managed settings, that means `channelsEnabled: true`. See [Restrict which channel plugins can run](/docs/en/channels#restrict-which-channel-plugins-can-run).
3683
3684### `blockedMarketplaces`
3685
3686Block plugin marketplace sources for your organization. Claude Code checks t
No line in this hunk matches that.