Answer: When the same configuration exists in multiple scopes, the scope closest to your current context wins. Permissions use a deny-overrides algorithm, so a deny rule in any scope blocks the action regardless of allow rules elsewhere. Status: Confirmed Entry: tool/kiro/settings/resolve-config-conflicts Revision: 1 Digest: sha256:06da488e5ea22d83 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:29Z Last changed: 2026-11-13T03:37:29Z Last verified: 2026-11-20T13:21:30Z Next check: 2026-11-21T13:21:30Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of General rule | the scope closest to your current context wins | [1] | 2026-11-20 Permissions | deny wins regardless of scope (deny-overrides algorithm) | [1] | 2026-11-20 MCP servers priority | Agent > Project > Global | [1] | 2026-11-20 Custom agents priority | Project > Global (same-name: project wins with warning) | [1] | 2026-11-20 Steering | All scopes merged (not overridden) | [1] | 2026-11-20 Workflows priority | Project > Global > synchronized account recipes > bundled recipes | [1] | 2026-11-20 Local command sandbox | An active global policy is the floor; a project can turn it on or tighten it, but cannot weaken it | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Configuration scopes - Features - Docs - Kiro". https://kiro.dev/docs/configuration/ Role: primary. Accessed: 2026-11-20T13:21:30Z Quote: "When the same configuration exists in multiple scopes, the scope closest to your current context wins" (Supports: General rule) Quote: "Permissions deny wins regardless of scope (deny-overrides algorithm)" (Supports: Permissions) Quote: "MCP servers Agent > Project > Global" (Supports: MCP servers priority) Quote: "Custom agents Project > Global (same-name: project wins with warning)" (Supports: Custom agents priority) Quote: "Steering All scopes merged (not overridden)" (Supports: Steering) Quote: "Workflows Project > Global > synchronized account recipes > bundled recipes" (Supports: Workflows priority) Quote: "Local command sandbox An active global policy is the floor; a project can turn it on or tighten it, but cannot weaken it" (Supports: Local command sandbox) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 38036717461e702fc249ddf52dcfded311aebf837a7c1657f397fb3991d0288e (captured 2026-11-20T13:21:29Z) 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-20T13:21:30Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:30Z Last attempt: 2026-11-20T13:21:30Z Notes and limitations: Extracted automatically from a single official source (section "Resolving conflicts"). Related: https://latestn.com/tool/kiro/settings/return-to-v2-harness How do I return Kiro CLI to the V2 agent harness? https://latestn.com/tool/kiro/settings/sandbox-configuration-keys What configuration keys does the Kiro sandbox support and how do global and project settings combine? https://latestn.com/tool/kiro/settings/sandbox-environment-variables How do I set environment variables in a Kiro web sandbox? https://latestn.com/tool/kiro/settings/proxy-configuration How do I configure a proxy for Kiro? https://latestn.com/tool/kiro/settings/proxy-configuration-2 How do I configure a proxy server for Kiro? https://latestn.com/tool/kiro/settings/python-custom-steering-files How do I create custom steering files for Python code style and framework guidelines in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:37:29Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/settings/resolve-config-conflicts/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/kiro/settings/resolve-config-conflicts POST: https://latestn.com/dispute/tool/kiro/settings/resolve-config-conflicts with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/settings/resolve-config-conflicts?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Kiro resolve conflicts between configuration scopes? Revision 1, last verified 2026-11-20T13:21:30Z. https://latestn.com/tool/kiro/settings/resolve-config-conflicts (accessed 2026-11-21T10:00:42Z). @misc{LatestN_tool_kiro_settings_resolve_config_conflicts_r1, title = {How does Kiro resolve conflicts between configuration scopes?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/settings/resolve-config-conflicts}}, note = {Revision 1; digest sha256:06da488e5ea22d83; last verified 2026-11-20T13:21:30Z; accessed 2026-11-21T10:00:42Z} } 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/kiro/settings/resolve-config-conflicts