Answer: In 1.0, express your intent once at the capability level rather than per-tool; translate each trusted command prefix into a shell allow rule (git *, npm *) in your user-scoped permissions.yaml, and translate each command denylist entry into a shell deny rule. Deny rules win over allow rules in every scope. Status: Confirmed Entry: tool/kiro/permissions-and-security/migrate-permissions-from-0x Revision: 1 Digest: sha256:8bdf9698ffb071d0 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:43:13Z Last changed: 2026-11-13T03:43:13Z Last verified: 2026-11-20T13:30:12Z Next check: 2026-11-21T13:30:12Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Migration approach | express the intent once at the capability level | [1] | 2026-11-20 Trusted commands translation | translate each prefix into a shell allow rule | [1] | 2026-11-20 Allow rule examples | git * , npm * | [1] | 2026-11-20 Denylist translation | translate each entry into a shell deny rule | [1] | 2026-11-20 Rule precedence | Deny rules win over allow rules in every scope. | [1] | 2026-11-20 Page updated | August 4, 2026 | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Capability-based permissions - What's new in 1.0 - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/whats-new-v1/permissions/ Role: primary. Accessed: 2026-11-20T13:30:12Z Quote: "In 1.0, express the intent once at the capability level." (Supports: Migration approach) Quote: "If you used trusted commands , translate each prefix into a shell allow rule" (Supports: Trusted commands translation) Quote: "shell allow rule ( git * , npm * ) in your user-scoped permissions.yaml" (Supports: Allow rule examples) Quote: "If you relied on the command denylist , translate each entry into a shell deny rule." (Supports: Denylist translation) Quote: "Deny rules win over allow rules in every scope." (Supports: Rule precedence) Quote: "Page updated: August 4, 2026" (Supports: Page updated) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 2580cad86f9cb63981b32faab107d2716fbb9997429f8383b97fb55dd7c06828 (captured 2026-11-20T13:30:11Z) 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:30:12Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:30:12Z Last attempt: 2026-11-20T13:30:12Z Notes and limitations: Extracted automatically from a single official source (section "Migrating from 0.x"). Related: 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/kiro/permissions-and-security/mcp-environment-variables How do I use environment variables for MCP server configuration in Kiro? https://latestn.com/tool/kiro/permissions-and-security/mcp-tool-approval How does the MCP tool approval process work in Kiro and when should I use auto-approval? https://latestn.com/tool/kiro/permissions-and-security/migrate-acp-permissions-consent How do I migrate permissions and consent when moving a Kiro ACP client to CLI V3? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:43:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/migrate-permissions-from-0x/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/migrate-permissions-from-0x POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/migrate-permissions-from-0x with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/migrate-permissions-from-0x?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate my Kiro permissions from 0.x to 1.0? Revision 1, last verified 2026-11-20T13:30:12Z. https://latestn.com/tool/kiro/permissions-and-security/migrate-permissions-from-0x (accessed 2026-11-21T10:04:40Z). @misc{LatestN_tool_kiro_permissions_and_security_migrate_permissions_from_0x_r1, title = {How do I migrate my Kiro permissions from 0.x to 1.0?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/migrate-permissions-from-0x}}, note = {Revision 1; digest sha256:8bdf9698ffb071d0; last verified 2026-11-20T13:30:12Z; accessed 2026-11-21T10:04:40Z} } 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/migrate-permissions-from-0x