Answer: When Kiro suggests a command, you can Allow or Deny that invocation, and when a saved rule can be derived it also offers persistent choices: Always allow or Always deny. You control which commands require approval through the Permissions system by defining shell capability rules in your permissions.yaml to allow, deny, or prompt for specific command patterns. Status: Confirmed Entry: tool/kiro/permissions-and-security/terminal-command-approval-security Revision: 1 Digest: sha256:60b041fece25fb62 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:37Z Last changed: 2026-11-13T03:42:37Z Last verified: 2026-11-20T13:29:19Z Next check: 2026-11-21T13:29:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of approval options | Allow or Deny | [1] | 2026-11-20 persistent choice allow | Always allow | [1] | 2026-11-20 persistent choice deny | Always deny | [1] | 2026-11-20 permissions file | permissions.yaml | [1] | 2026-11-20 permissions file path | ~/.kiro/settings/permissions.yaml | [1] | 2026-11-20 allow match patterns | git * | [1] | 2026-11-20 deny match patterns | rm -rf * | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Terminal - Chat - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/chat/terminal/ Role: primary. Accessed: 2026-11-20T13:29:19Z Quote: "When Kiro suggests a command, you can Allow or Deny that invocation." (Supports: approval options) Quote: "Always allow : Execute and trust similar commands in the future" (Supports: persistent choice allow) Quote: "Always deny : Block similar commands going forward" (Supports: persistent choice deny) Quote: "Define shell capability rules in your permissions.yaml to allow, deny, or prompt for specific command patterns" (Supports: permissions file) Quote: "# ~/.kiro/settings/permissions.yaml" (Supports: permissions file path) Quote: "match : [ "git *" , "npm *" , "npx *" ]" (Supports: allow match patterns) Quote: "match : [ "rm -rf *" , "sudo *" ]" (Supports: deny match patterns) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: a048abbdddcd47b965b35ccd50abaee5fad4bf9ec341b3d116a61b4c7565aed1 (captured 2026-11-20T13:29:19Z) 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:29:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:29:19Z Last attempt: 2026-11-20T13:29:19Z Notes and limitations: Extracted automatically from a single official source (section "Command approval and security"). Related: https://latestn.com/tool/kiro/permissions-and-security/tool-approval How do I approve or deny tool calls in Kiro Crew, including bulk approval and per-call reject? https://latestn.com/tool/kiro/permissions-and-security/tool-permission-problems Why does the /tools command return an empty list or show unexpected permission prompts in Kiro? https://latestn.com/tool/kiro/permissions-and-security/tool-permissions How do I set tool permissions for Kiro's built-in tools? https://latestn.com/tool/kiro/permissions-and-security/supervised-mode What does Supervised mode do in Kiro and when should I use it? https://latestn.com/tool/kiro/permissions-and-security/supervised-vs-autopilot-mode How does supervised mode work in Kiro and how is it different from Autopilot mode? https://latestn.com/tool/kiro/permissions-and-security/support-power-iam-permissions What IAM permissions are required to use the Kiro Support power? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:42:37Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/terminal-command-approval-security/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/terminal-command-approval-security POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/terminal-command-approval-security with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/terminal-command-approval-security?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I approve or manage command approval and security for terminal commands in Kiro? Revision 1, last verified 2026-11-20T13:29:19Z. https://latestn.com/tool/kiro/permissions-and-security/terminal-command-approval-security (accessed 2026-11-21T10:03:51Z). @misc{LatestN_tool_kiro_permissions_and_security_terminal_command_approval_security_r1, title = {How do I approve or manage command approval and security for terminal commands in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/terminal-command-approval-security}}, note = {Revision 1; digest sha256:60b041fece25fb62; last verified 2026-11-20T13:29:19Z; accessed 2026-11-21T10:03:51Z} } 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/terminal-command-approval-security