settings.json
A configuration file for Claude Code used to declare hooks, permissions and other settings, supporting JSON structures that define shell commands to run before and after lifecycle events.
Timeline (last 90 days)
The four project instruction modes are controlled by a single settings key rather than switched via command-line arguments, and the configuration can be written into project-level or user-level settings files.
Claude Code's .claude/settings.json stores team permissions, hooks, and plugins, and agents can add allow rules here to expand the executable range.
Claude Code's permission mechanism consists of three mutually independent yet combinable parts: the mode determines how actions are approved, rules specify which tool calls are allowed/asked about/denied, and the sandbox restricts the files and network that commands can actually access
All Facts (3)
The four project instruction modes are controlled by a single settings key rather than switched via command-line arguments, and the configuration can be written into project-level or user-level settings files.
50%UnverifiedClaude Code's .claude/settings.json stores team permissions, hooks, and plugins, and agents can add allow rules here to expand the executable range.
50%UnverifiedClaude Code's permission mechanism consists of three mutually independent yet combinable parts: the mode determines how actions are approved, rules specify which tool calls are allowed/asked about/denied, and the sandbox restricts the files and network that commands can actually access
50%