Answer: In IDE 0.x, trusted commands were configured via the kiroAgent.trustedCommands setting (Settings → Kiro Agent: Trusted Commands) at user or workspace level using prefix matching with * wildcards, and the command denylist was configured via kiroAgent.commandDenylist (Settings → Kiro Agent: Command Denylist) using substring matching. The denylist check had highest priority, followed by the trust check, then default manual approval. Status: Confirmed Entry: tool/kiro/permissions-and-security/trusted-commands-denylist Revision: 1 Digest: sha256:6f9f65a02d156bc3 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:14Z Last changed: 2026-11-13T03:42:14Z Last verified: 2026-11-20T13:28:46Z Next check: 2026-11-21T13:28:46Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Trusted commands setting | kiroAgent.trustedCommands | [1] | 2026-11-20 Trusted commands location | Settings → Kiro Agent: Trusted Commands | [1] | 2026-11-20 Trusted commands matching | Prefix-based string matching | [1] | 2026-11-20 Denylist setting | kiroAgent.commandDenylist | [1] | 2026-11-20 Denylist location | Settings → Kiro Agent: Command Denylist | [1] | 2026-11-20 Denylist matching | substring matching | [1] | 2026-11-20 Evaluation order | Denylist check (highest priority) | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "0.x reference - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/0x-reference/ Role: primary. Accessed: 2026-11-20T13:28:46Z Quote: "Trusted commands ( kiroAgent.trustedCommands )" (Supports: Trusted commands setting) Quote: "Configured in Settings → Kiro Agent: Trusted Commands at user or workspace level." (Supports: Trusted commands location) Quote: "Matching rules: Prefix-based string matching" (Supports: Trusted commands matching) Quote: "Command denylist ( kiroAgent.commandDenylist )" (Supports: Denylist setting) Quote: "Configured in Settings → Kiro Agent: Command Denylist ." (Supports: Denylist location) Quote: "Used substring matching — if any denied pattern appeared anywhere in the command, approval was required regardless of trust settings." (Supports: Denylist matching) Quote: "Denylist check (highest priority) — if command contains a denied pattern, require approval" (Supports: Evaluation order) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 3c2b5bfcad3be8430d867e63b532d06bfe0efb2fc40c17829c26fc5f8f585b88 (captured 2026-11-20T13:28:49Z) 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:28:46Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:28:46Z Last attempt: 2026-11-20T13:28:46Z Notes and limitations: Extracted automatically from a single official source (section "Terminal trusted commands and denylist"). Related: https://latestn.com/tool/kiro/permissions-and-security/validate-hook-inputs How do I validate inputs in Kiro hooks for security? https://latestn.com/tool/kiro/permissions-and-security/vpc-iam-roles What IAM roles does Kiro need to connect cloud sessions to a VPC? https://latestn.com/tool/kiro/permissions-and-security/webex-who-can-reach Who can reach the Kiro Crew Webex bot? 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/trust-workspace-cli How do I trust a workspace in Kiro CLI? https://latestn.com/tool/kiro/permissions-and-security/trusted-commands How do I configure trusted commands in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:42:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/trusted-commands-denylist/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/trusted-commands-denylist POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/trusted-commands-denylist with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/trusted-commands-denylist?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure trusted commands and the command denylist in Kiro 0.x? Revision 1, last verified 2026-11-20T13:28:46Z. https://latestn.com/tool/kiro/permissions-and-security/trusted-commands-denylist (accessed 2026-11-21T10:05:07Z). @misc{LatestN_tool_kiro_permissions_and_security_trusted_commands_denylist_r1, title = {How do I configure trusted commands and the command denylist in Kiro 0.x?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/trusted-commands-denylist}}, note = {Revision 1; digest sha256:6f9f65a02d156bc3; last verified 2026-11-20T13:28:46Z; accessed 2026-11-21T10:05:07Z} } 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/trusted-commands-denylist