Learn one feature at a time
Know which setting
you are changing.
Find Claude Code controls for models, permissions, display preferences, and project configuration.
First, identify the application
This page explains Claude Code, not this guide’s Settings page. Web, Desktop, IDE, and terminal sessions do not expose identical controls. Start with the interface you are using.
| Where you work | Where to look |
|---|---|
| Terminal | Use /config for preferences; /model, /permissions, and /mcp address specific controls. |
| Claude Desktop, Code tab | Use the session’s mode and model controls and the app’s Claude Code settings. |
| Claude Code on the web | Use session controls and the selected cloud environment. Local machine settings do not automatically transfer. |
| VS Code | Check extension settings and the active session indicator. |
Settings worth understanding first
| Control | Why it helps | What to check |
|---|---|---|
| Permission mode | Decide how actions are approved. | Inspect the active mode before each unfamiliar task. |
| Model and effort | Match the task’s complexity and workload. | Read the picker and usage notices. |
| Display and response preferences | Make sessions easier to follow. | Change one setting, then compare the result. |
| MCP and connectors | Use authorized project information. | Check read and write permissions. |
| Environment and network | Provide the tools a cloud task needs. | Use narrow access and protect credentials. |
User, project, or local project?
~/.claude/settings.json contains user settings on that machine. .claude/settings.json is project configuration that travels when committed. .claude/settings.local.json holds personal project overrides and should stay out of Git. Organization-managed settings can take precedence.
Do not replace a settings file with an example. Inspect and merge the relevant change, keep a recovery copy, and validate the JSON. Use the interface where possible.
Inspect the settings relevant to this Claude Code project. Explain their scope and which values take precedence. Do not reveal secret values or edit anything. Propose the smallest change needed to make future project sessions start in Plan, and explain how I can verify and undo it.Verify one change
- Write down the previous value and scope.
- Apply only the intended change.
- Start a new session if the setting affects startup.
- Check the visible mode or setting.
- Restore the old value if the result is unexpected.
For reusable behavioral guidance, use the Instruction Wizard. Text instructions do not change actual permission settings.
References
- Anthropic. (n.d.-k). Commands. Retrieved September 24, 2026, from https://code.claude.com/docs/en/commands
- Anthropic. (n.d.-q). Desktop application. Retrieved September 24, 2026, from https://code.claude.com/docs/en/desktop
- Anthropic. (n.d.-am). Settings files and precedence. Retrieved September 24, 2026, from https://code.claude.com/docs/en/settings
Was this chapter useful?
Report an errorVotes are shared only if you enable optional measurement in Privacy & Preferences.