Answer: In 3.x, 2.x's toolsSettings with per-tool allow and deny lists are replaced by Unified permissions.rules with capability, match, and effect, and regex patterns in permissions become Glob patterns only (no regex). Status: Confirmed Entry: tool/kiro/permissions-and-security/permission-behavior-changes-from-2x Revision: 2 Digest: sha256:098e4e230a9c8f76 (changes whenever the content changes) Timeline: Created: 2026-11-13T13:08:01Z Last changed: 2026-11-20T13:21:06Z (Wildcard change: — → Not supported for shell or URL patterns) Last verified: 2026-11-20T13:21:06Z Next check: 2026-11-21T13:21:06Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of 2.x behavior | toolsSettings with per-tool allow and deny lists | [1] | 2026-11-20 V3 behavior | Unified permissions.rules with capability , match , and effect | [1] | 2026-11-20 Regex change | Glob patterns only (no regex) | [1] | 2026-11-20 Wildcard change | Not supported for shell or URL patterns | [1] | 2026-11-20 Deny precedence | Deny always wins across all scopes | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Permissions migration - Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/permissions/ Role: primary. Accessed: 2026-11-20T13:21:06Z Quote: "toolsSettings with per-tool allow and deny lists" (Supports: 2.x behavior) Quote: "Unified permissions.rules with capability , match , and effect" (Supports: V3 behavior) Quote: "Glob patterns only (no regex)" (Supports: Regex change) Quote: "Not supported for shell or URL patterns" (Supports: Wildcard change) Quote: "Deny always wins across all scopes" (Supports: Deny precedence) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 8aec03482b16606b5a6bdac535a8bf9c09fea0be7ac5296cc310232d4149507e (captured 2026-11-20T13:21:07Z) 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:06Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:06Z Last attempt: 2026-11-20T13:21:06Z Notes and limitations: Extracted automatically from a single official source (section "Behavioral changes from 2.x"). Related: https://latestn.com/tool/kiro/permissions-and-security/permission-modes-approval-flow What are the permission modes in Kiro and how does the interactive approval flow work? https://latestn.com/tool/kiro/permissions-and-security/permission-modes-overview What are the permission modes in Kiro and how do they differ? https://latestn.com/tool/kiro/permissions-and-security/permission-policy-rule-format What is the rule format for Kiro permission policies? https://latestn.com/tool/kiro/permissions-and-security/migrate-permissions-from-0x How do I migrate my Kiro permissions from 0.x to 1.0? https://latestn.com/tool/kiro/permissions-and-security/mobile-app-lock How do I enable or disable app lock in the Kiro mobile app? https://latestn.com/tool/kiro/permissions-and-security/oauth-remote-registry-servers How do I set up OAuth for remote registry MCP servers in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:21:06Z | changed | Wildcard change: — → Not supported for shell or URL patterns | [1] 2026-11-20T13:21:06Z | changed | Regex change: — → Glob patterns only (no regex) | [1] 2026-11-20T13:21:06Z | changed | Sub-agent behavior: A sub-agent's tool call runs without a prompt only when the parent session's policy also allows it → — | [1] 2026-11-20T13:21:06Z | changed | Pattern support: Glob patterns only (no regex) → — | [1] 2026-11-13T13:08:01Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/permission-behavior-changes-from-2x/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/permissions-and-security/permission-behavior-changes-from-2x POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/permission-behavior-changes-from-2x with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/permission-behavior-changes-from-2x?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do Kiro CLI 3.x permission rules differ from 2.x? Revision 2, last verified 2026-11-20T13:21:06Z. https://latestn.com/tool/kiro/permissions-and-security/permission-behavior-changes-from-2x (accessed 2026-11-21T10:07:24Z). @misc{LatestN_tool_kiro_permissions_and_security_permission_behavior_changes_from_2x_r2, title = {How do Kiro CLI 3.x permission rules differ from 2.x?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/permission-behavior-changes-from-2x}}, note = {Revision 2; digest sha256:098e4e230a9c8f76; last verified 2026-11-20T13:21:06Z; accessed 2026-11-21T10:07:24Z} } 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/permissions-and-security/permission-behavior-changes-from-2x