Debug your configuration changeddebug-your-config
Nearest release: v2.1.240, published 4 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+1added
Lines−1removed
From line
79
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits22to this page, all time
The whole hunk
from line 79, old and new numbered
/
from line 79
7979
8080The clean session has no user or project settings, hooks, MCP servers, plugins, or memory. On the first launch, expect the first-run setup screens, starting with theme selection. If you see them, the clean configuration directory is in effect. Later launches with the same directory skip these screens because Claude Code saves onboarding state there.
8181
82* Managed settings still apply if your organization deploys them, since they live at a system path outside `~/.claude`
82* Managed settings still apply if your organization deploys them. Claude Code reads MDM profiles, registry policy, and `managed-settings.json` from locations outside the configuration directory, and [fetches server-managed settings](/docs/en/server-managed-settings#fetch-and-caching-behavior) again for the clean session once it has credentials
8383* On Linux and Windows, you'll be prompted to log in again because credentials are stored under the configuration directory
8484* On macOS, credentials are in the Keychain and carry over to the clean session
8585
No line in this hunk matches that.