Answer: The permission modes are Supervised, Accept file changes, and Approve for me. In the interactive approval flow, when a tool requires approval a prompt appears in chat with Allow and Deny for the current invocation, plus persistent choices (Always allow and Always deny) when Kiro can derive a working saved rule; selecting those lets you configure a Pattern and Apply to scope. Status: Confirmed Entry: tool/kiro/permissions-and-security/permission-modes-approval-flow Revision: 4 Digest: sha256:1e261b00862a14ab (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:03Z Last changed: 2026-11-20T13:31:18Z (chained commands: — → For chained commands (e.g., cd /path && cargo build ), each sub-command in the chain is presented separately for approval.) Last verified: 2026-11-20T13:31:18Z Next check: 2026-11-21T13:31:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of permission modes | Supervised , Accept file changes , or Approve for me | [1] | 2026-11-20 Supervised behavior | In Supervised, Kiro asks before actions regardless. | [1] | 2026-11-20 Accept file changes behavior | In Accept file changes, allowed operations run without prompting while your deny and ask rules still gate specific capabilities. | [1] | 2026-11-20 Approve for me behavior | In Approve for me, a model judges only the actions no rule settles. | [1] | 2026-11-20 approval prompt options | Allow and Deny are available for the current invocation. | [1] | 2026-11-20 persistent choices | Always allow Create a persistent allow rule (opens pattern/scope picker) | [1] | 2026-11-20 Always allow/deny configuration | Pattern - choose the match scope for the rule | [1] | 2026-11-20 chained commands | For chained commands (e.g., cd /path && cargo build ), each sub-command in the chain is presented separately for approval. | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Permissions - Features - Docs - Kiro". https://kiro.dev/docs/permissions/ Role: primary. Accessed: 2026-11-20T13:31:18Z Quote: "Supervised , Accept file changes , or Approve for me" (Supports: permission modes) Quote: "In Supervised, Kiro asks before actions regardless." (Supports: Supervised behavior) Quote: "In Accept file changes, allowed operations run without prompting while your deny and ask rules still gate specific capabilities." (Supports: Accept file changes behavior) Quote: "In Approve for me, a model judges only the actions no rule settles." (Supports: Approve for me behavior) Quote: "Allow and Deny are available for the current invocation." (Supports: approval prompt options) Quote: "Always allow Create a persistent allow rule (opens pattern/scope picker)" (Supports: persistent choices) Quote: "Pattern - choose the match scope for the rule" (Supports: Always allow/deny configuration) Quote: "For chained commands (e.g., cd /path && cargo build ), each sub-command in the chain is presented separately for approval." (Supports: chained commands) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 6cc7b2a366b346341b3d7e5ad4b14e1ec81d9f79961e25a7b25c1348892b1a5f (captured 2026-11-20T13:31:17Z) 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:31:18Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:18Z Last attempt: 2026-11-20T13:31:18Z Notes and limitations: Extracted automatically from a single official source (section "Managing permissions by surface"). Related: 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/persistent-permission-rules How do I set up persistent permission rules in Kiro CLI? 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/kiro/permissions-and-security/permission-behavior-changes-from-2x How do Kiro CLI 3.x permission rules differ from 2.x? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:31:18Z | changed | chained commands: — → For chained commands (e.g., cd /path && cargo build ), each sub-command in the chain is presented separately for approval. | [1] 2026-11-20T13:31:18Z | changed | Always allow/deny configuration: — → Pattern - choose the match scope for the rule | [1] 2026-11-20T13:31:18Z | changed | persistent choices: — → Always allow Create a persistent allow rule (opens pattern/scope picker) | [1] 2026-11-20T13:31:18Z | changed | approval prompt options: — → Allow and Deny are available for the current invocation. | [1] 2026-11-20T13:31:18Z | changed | Approve for me behavior: — → In Approve for me, a model judges only the actions no rule settles. | [1] 2026-11-20T13:31:18Z | changed | Accept file changes behavior: — → In Accept file changes, allowed operations run without prompting while your deny and ask rules still gate specific capabilities. | [1] 2026-11-20T13:31:18Z | changed | Supervised behavior: — → In Supervised, Kiro asks before actions regardless. | [1] 2026-11-20T13:31:18Z | changed | permission modes: — → Supervised , Accept file changes , or Approve for me | [1] 2026-11-20T13:31:18Z | changed | This workspace path: ~/.kiro/workspace-roots//permissions.yaml → — | [1] 2026-11-20T13:31:18Z | changed | All workspaces path: ~/.kiro/settings/permissions.yaml → — | [1] 2026-11-20T13:31:18Z | changed | Persistent deny choice: Always deny → — | [1] 2026-11-20T13:31:18Z | changed | Persistent choices: Always allow → — | [1] 2026-11-20T13:31:18Z | changed | Approval prompt options: Allow and Deny are available for the current invocation. → — | [1] 2026-11-20T13:31:18Z | changed | Settings key: kiroAgent.agentAutonomy → — | [1] 2026-11-20T13:31:18Z | changed | Autopilot switch behavior: toggles between Supervised and Accept file changes (formerly Autopilot) → — | [1] 2026-11-20T13:31:18Z | changed | Permission modes: Supervised , Accept file changes , or Approve for me → — | [1] 2026-11-18T13:26:01Z | changed | This workspace path: — → ~/.kiro/workspace-roots//permissions.yaml | [1] 2026-11-18T13:26:01Z | changed | All workspaces path: — → ~/.kiro/settings/permissions.yaml | [1] 2026-11-18T13:26:01Z | changed | Persistent choices: — → Always allow | [1] 2026-11-18T13:26:01Z | changed | Approval prompt options: — → Allow and Deny are available for the current invocation. | [1] 2026-11-18T13:26:01Z | changed | Settings key: — → kiroAgent.agentAutonomy | [1] 2026-11-18T13:26:01Z | changed | Autopilot switch behavior: — → toggles between Supervised and Accept file changes (formerly Autopilot) | [1] 2026-11-18T13:26:01Z | changed | Chained commands: each sub-command in the chain is presented separately for approval → — | [1] 2026-11-18T13:26:01Z | changed | Apply to options: All workspaces → — | [1] 2026-11-18T13:26:01Z | changed | Persistent allow choice: Always allow → — | [1] 2026-11-18T13:26:01Z | changed | Current invocation options: Allow and Deny → — | [1] 2026-11-13T13:16:08Z | changed | Persistent deny choice: — → Always deny | [1] 2026-11-13T13:16:08Z | changed | Persistent allow choice: — → Always allow | [1] 2026-11-13T13:16:08Z | changed | Current invocation options: — → Allow and Deny | [1] 2026-11-13T13:16:08Z | changed | Persistent choices: Always allow → — | [1] 2026-11-13T13:16:08Z | changed | Approval prompt options: Allow and Deny are available for the current invocation. → — | [1] 2026-11-13T03:44:03Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/permission-modes-approval-flow/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-modes-approval-flow POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/permission-modes-approval-flow with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/permission-modes-approval-flow?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the permission modes in Kiro and how does the interactive approval flow work? Revision 4, last verified 2026-11-20T13:31:18Z. https://latestn.com/tool/kiro/permissions-and-security/permission-modes-approval-flow (accessed 2026-11-21T10:04:45Z). @misc{LatestN_tool_kiro_permissions_and_security_permission_modes_approval_flow_r4, title = {What are the permission modes in Kiro and how does the interactive approval flow work?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/permission-modes-approval-flow}}, note = {Revision 4; digest sha256:1e261b00862a14ab; last verified 2026-11-20T13:31:18Z; accessed 2026-11-21T10:04:45Z} } 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-modes-approval-flow