Answer: Zed resolves conflicts by rule precedence, from highest to lowest priority: built-in security rules, then always_deny, always_confirm, always_allow, tool-specific default, and finally global default. Status: Overdue (check was due 2026-11-20T13:38:59Z and has not succeeded) Entry: tool/zed/permissions-and-security/rule-precedence Revision: 1 Digest: sha256:e753bd7ecb9d349a (changes whenever the content changes) Timeline: Created: 2026-11-13T04:00:35Z Last changed: 2026-11-13T04:00:35Z Last verified: 2026-11-19T13:38:59Z Next check: 2026-11-20T13:38:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Highest priority rule | Built-in security rules | [1] | 2026-11-19 Second priority rule | always_deny | [1] | 2026-11-19 Third priority rule | always_confirm | [1] | 2026-11-19 Fourth priority rule | always_allow | [1] | 2026-11-19 Fifth priority rule | Tool-specific `default` | [1] | 2026-11-19 Lowest priority rule | Global `default` | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/ai/tool-permissions.md". https://zed.dev/docs/ai/tool-permissions.md Role: primary. Accessed: 2026-11-19T13:38:59Z Quote: "**Built-in security rules**: Hardcoded protections (e.g., `rm -rf /`). Cannot be overridden." (Supports: Highest priority rule) Quote: "**`always_deny`**: Blocks matching actions" (Supports: Second priority rule) Quote: "**`always_confirm`**: Requires confirmation for matching actions" (Supports: Third priority rule) Quote: "**`always_allow`**: Auto-approves matching actions" (Supports: Fourth priority rule) Quote: "**Tool-specific `default`**: Per-tool fallback when no patterns match (e.g., `tools.terminal.default`)" (Supports: Fifth priority rule) Quote: "**Global `default`**: Falls back to `tool_permissions.default` when no tool-specific default is set" (Supports: Lowest priority rule) Snapshot SHA-256: c27fe015ce56aff723892b75234677a529db3b3061d7bff8789285c39227b2f3 (captured 2026-11-19T13:38:59Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-19T13:38:59Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:38:59Z Last attempt: 2026-11-19T13:38:59Z Notes and limitations: Extracted automatically from a single official source (section "Rule Precedence"). Human-readable page: https://zed.dev/docs/ai/tool-permissions.html Related: https://latestn.com/tool/zed/permissions-and-security/sandbox-requirements What are the requirements to use sandboxing in Zed? https://latestn.com/tool/zed/permissions-and-security/trust-worktree-restricted-mode How do I trust a worktree in Zed so it leaves Restricted Mode? https://latestn.com/tool/zed/permissions-and-security/what-is-restricted-untrusted-worktree What is restricted in Zed when a worktree is not trusted? https://latestn.com/tool/zed/permissions-and-security/process-exec-capability What does the process:exec capability allow a Zed extension to do? https://latestn.com/tool/zed/permissions-and-security/profiles-vs-tool-permissions What is the difference between Zed agent profiles and tool permissions? https://latestn.com/tool/zed/permissions-and-security/restrict-extension-capabilities How do I restrict which capabilities Zed extensions are granted? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:00:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/permissions-and-security/rule-precedence/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/permissions-and-security/rule-precedence POST: https://latestn.com/dispute/tool/zed/permissions-and-security/rule-precedence with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/permissions-and-security/rule-precedence?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Zed decide which tool permission rule wins when multiple patterns match? Revision 1, last verified 2026-11-19T13:38:59Z. https://latestn.com/tool/zed/permissions-and-security/rule-precedence (accessed 2026-11-21T10:03:13Z). @misc{LatestN_tool_zed_permissions_and_security_rule_precedence_r1, title = {How does Zed decide which tool permission rule wins when multiple patterns match?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/permissions-and-security/rule-precedence}}, note = {Revision 1; digest sha256:e753bd7ecb9d349a; last verified 2026-11-19T13:38:59Z; accessed 2026-11-21T10:03:13Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/permissions-and-security/rule-precedence