Dokumentationerreichbar
Anthropic, Settings files and precedence
code.claude.com (externe Seite)
Die Dokumentation zu den Einstellungsdateien von Claude Code: welche Ebenen es gibt, in welche Ebene ein Schlüssel gehört, wie man eine Änderung prüft und welcher Wert gilt, wenn ein Schlüssel an mehreren Stellen steht.
geprüft 10.11.2026
Worauf sich diese Seite beruft, wörtlich, abgerufen am 12.10.2026:
the file it reads a setting from decides who the setting applies to
bestätigt 10.11.2026Claude Code reads settings from four files, and an organization can also deliver managed settings from the claude.ai console.
bestätigt 10.11.2026Installing Claude Code doesn’t create any settings file.
bestätigt 10.11.2026the first time you give a standing approval on a permission prompt
bestätigt 10.11.2026that it writes for itself; you don’t need to edit it
bestätigt 10.11.2026When the same key appears in more than one place, Claude Code uses the value from the highest level that sets it.
bestätigt 10.11.2026Claude Code combines the lists instead of picking one, so each file can add entries without removing another file’s.
bestätigt 10.11.2026Managed is the top level.
bestätigt 10.11.2026For a few security-sensitive keys, Claude Code honors a stricter value from a lower level over a managed value
bestätigt 10.11.2026so everyone who clones the repository gets the same permissions, hooks, and plugins
steht dort nicht mehrUntil then they still see prompts and don’t get plugins from a marketplace the file declares.
bestätigt 10.11.2026don’t take effect from project or local settings
bestätigt 10.11.2026so the file stays out of your commits in every repository
bestätigt 10.11.2026It lists a short set of personal options such as theme, editor mode, and verbose output, not every settings key.
bestätigt 10.11.2026change settings there by editing a settings file or through those apps’ own settings
bestätigt 10.11.2026Settings files are strict JSON
bestätigt 10.11.2026which gives you autocomplete and inline validation
bestätigt 10.11.2026Claude Code watches your settings files and reloads them when they change
bestätigt 10.11.2026Claude Code reads some keys only once, at session start
bestätigt 10.11.2026The value applies to that session and your settings files stay as they were.
bestätigt 10.11.2026The line confirms which files Claude Code read; it doesn’t show which file supplied each key.
bestätigt 10.11.2026Environment variables aren’t a level in this stack.
bestätigt 10.11.2026which one applies is decided per pair, not by level
bestätigt 10.11.2026Only server-managed settings reach the cloud session
bestätigt 10.11.2026Claude Code then stores your settings, session history, and plugins there instead.
bestätigt 10.11.2026Before v2.1.211, Claude Code kept the file in the starting directory.
bestätigt 10.11.2026Its allow rules don’t wait for trust while the file stays untracked.
bestätigt 10.11.2026asks whether to exit and fix it or reset to the default configuration
bestätigt 10.11.2026Those keys never apply from the shared file
bestätigt 10.11.2026took effect from any file
bestätigt 10.11.2026is an ordered chain where position carries meaning
bestätigt 10.11.2026For a few keys whose values restrict a session, Claude Code honors a restrictive value from a scope that otherwise couldn’t override managed settings.
bestätigt 10.11.2026Something else is setting the same key, the file can’t set that value, or the file didn’t load
bestätigt 10.11.2026At the start of an interactive session Claude Code shows a dialog that lets you fix the file with Claude’s help, exit, or continue without the broken settings.
bestätigt 10.11.2026Claude Code skips those values and keeps the rest of the file in effect.
bestätigt 10.11.2026Claude Code skips a broken user, project, or local file or its broken values and continues with the rest
bestätigt 10.11.2026the change applies to the current session and is gone in the next one
bestätigt 10.11.2026a session with several repositories starts above the clones
bestätigt 10.11.2026opens your claude.ai Code or Claude Code settings page instead of changing a value
bestätigt 10.11.2026not for managed settings that arrive from MDM or the claude.ai console
bestätigt 10.11.2026system prompt isn’t published
bestätigt 10.11.2026The schema can lag behind the newest CLI releases
bestätigt 10.11.2026when the repository root is your home directory
bestätigt 10.11.2026unless an app that embeds Claude Code supplies its own model list
bestätigt 10.11.2026the locks are available
bestätigt 10.11.2026Models and denied Models still don’t load in a cloud session
bestätigt 10.11.2026A self-hosted environment also reads the managed settings file in its runner image.
bestätigt 10.11.2026not permission rules, hooks
bestätigt 10.11.2026Both stay on your machine, and the local file isn’t in the clone.
bestätigt 10.11.2026Some of what you commit waits until each teammate trusts the folder, and a few keys never take effect from a repository file
bestätigt 10.11.2026After you move the session with /
bestätigt 10.11.2026cd, Claude Code reads both project files from the new directory instead Unless a managed settings document can’t be parsed
bestätigt 10.11.2026in a cloud thread in a project, none of a repository’s .claude/settings.json permission rules, hooks, or env apply
bestätigt 10.11.2026read in a session with one repository outside a project’s threads, because the file is part of the clone and the session starts inside it.
bestätigt 10.11.2026In a session with one repository outside a project’s threads, you can instead commit the key to that repository’s .claude/settings.json.
bestätigt 10.11.2026when the repository root or its .git or .claude entry isn’t owned by your user
bestätigt 10.11.2026
11 Eine Wissensbasis aufbauen15 Einstellungen und Ebenen31 Der Harness