Evidence · DiggingBeagle record
Claude Code permission rules, modes and workspace trust
Official Claude Code documentation inspected October 9, 2026. It describes deny, ask and allow precedence; repository-scoped permission grants; workspace trust before use of project allow rules in interactive sessions; mode-specific limits; and Bash wildcard behavior. This is current documented semantics, not a runtime recreation or proof that all repositories in the September harness study ran the same client version.
- Publisher
- Anthropic / Claude Code documentation
- Source role
- vendor statement
Evidence record
Official Claude Code documentation inspected October 9, 2026. It describes deny, ask and allow precedence; repository-scoped permission grants; workspace trust before use of project allow rules in interactive sessions; mode-specific limits; and Bash wildcard behavior. This is current documented semantics, not a runtime recreation or proof that all repositories in the September harness study ran the same client version.
Claim-level citations (1)
- supportsRepository study finds unpinned MCP dependencies and broad agent execution preapprovals: Anthropic documents deny, then ask, then allow rule precedence and states that project .claude/settings.json allow grants require acceptance of workspace trust in interactive sessions. These current client rules show why a repository grant is not automatically proof of effective execution and cannot be presumed to describe every sampled historical client version.
Manage permissions, rule precedence, and Project allow rules and workspace trust sections