Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 22 Oct 2026
One change · claude-code

Debug your configuration changeddebug-your-config

Nearest release: v2.1.307, published 3 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 22 Oct 2026 00:14 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 30 Oct 2026 18:07 UTC.

Upstream edited
Recorded here
Lines+26added
Lines−26removed
From line 91 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits26to this page, all time

The whole hunk

from line 91, old and new numbered
/
lines
from line 91
9191 
9292In your shell, with no Claude Code session running, create the directory and move into it:
9393 
94**Bash or Zsh**
94> [tab] Bash or Zsh
95>
96> ```bash theme={null}
97> mkdir -p ~/claude-clean/empty && cd ~/claude-clean/empty
98> ```
9599 
96```bash theme={null}
97mkdir -p ~/claude-clean/empty && cd ~/claude-clean/empty
98```
100> [tab] PowerShell
101>
102> ```powershell theme={null}
103> New-Item -ItemType Directory -Force "$HOME/claude-clean/empty" | Out-Null
104> Set-Location "$HOME/claude-clean/empty"
105> ```
99106 
100**PowerShell**
101 
102```powershell theme={null}
103New-Item -ItemType Directory -Force "$HOME/claude-clean/empty" | Out-Null
104Set-Location "$HOME/claude-clean/empty"
105```
106 
107107**2. Start Claude Code with a clean configuration directory**
108108 
109109From the same shell, set [`CLAUDE_CONFIG_DIR`](https://code.claude.com/docs/en/env-vars) to a fresh directory in place of `~/.claude`, and pass [`--setting-sources user`](https://code.claude.com/docs/en/cli-reference#cli-flags) to turn off project configuration such as `.claude/settings.json`, `CLAUDE.md`, and `.mcp.json`:
110110 
111**Bash or Zsh**
111> [tab] Bash or Zsh
112>
113> The variable applies to this one launch.
114>
115> ```bash theme={null}
116> CLAUDE_CONFIG_DIR=~/claude-clean/config claude --setting-sources user
117> ```
112118 
113The variable applies to this one launch.
114 
115```bash theme={null}
116CLAUDE_CONFIG_DIR=~/claude-clean/config claude --setting-sources user
117```
118 
119**PowerShell**
120 
121The variable stays set for the rest of this PowerShell session, so later `claude` launches in the same window keep using the clean directory. To return to your usual directory, run `Remove-Item Env:CLAUDE_CONFIG_DIR` before the next launch.
122 
123```powershell theme={null}
124$env:CLAUDE_CONFIG_DIR = "$HOME/claude-clean/config"
125claude --setting-sources user
126```
119> [tab] PowerShell
120>
121> The variable stays set for the rest of this PowerShell session, so later `claude` launches in the same window keep using the clean directory. To return to your usual directory, run `Remove-Item Env:CLAUDE_CONFIG_DIR` before the next launch.
122>
123> ```powershell theme={null}
124> $env:CLAUDE_CONFIG_DIR = "$HOME/claude-clean/config"
125> claude --setting-sources user
126> ```
127127 
128128On the first launch, you go through the first-run setup screens again, a sign that the clean configuration directory is in effect. Managed settings still apply, and [connectors](https://code.claude.com/docs/en/mcp.md#use-mcp-servers-from-claude-ai) still load if you log in with a claude.ai account.
129129 
Feedback