Answer: Review the permissions rules created by /upgrade-agent, then apply any remaining changes below, and resolve every warning before using the migrated profile in CI. Status: Confirmed Entry: tool/kiro/permissions-and-security/review-converted-permissions Revision: 2 Digest: sha256:1ad87116d4bfcca9 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:15Z Last changed: 2026-11-19T13:14:11Z (command that creates rules: /upgrade-agent → —) Last verified: 2026-11-20T13:21:03Z Next check: 2026-11-21T13:21:03Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of review step | Review converted permissions | [1] | 2026-11-20 warning requirement | Resolve every warning before using the migrated profile in CI. | [1] | 2026-11-20 user scope permissions file | ~/.kiro/settings/permissions.yaml | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Migration guide - Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/migration-guide/ Role: primary. Accessed: 2026-11-20T13:21:03Z Quote: "3. Review converted permissions Review the permissions rules created by /upgrade-agent , then apply any remaining changes below." (Supports: review step) Quote: "Resolve every warning before using the migrated profile in CI." (Supports: warning requirement) Quote: "You can also create ~/.kiro/settings/permissions.yaml with capability-specific allow rules in your CI environment." (Supports: user scope permissions file) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 475b86970159f5a5debfbe4b6506675ab3283d78fde7186559a147163f52ae74 (captured 2026-11-20T13:21:02Z) 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:03Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:03Z Last attempt: 2026-11-20T13:21:03Z Notes and limitations: Extracted automatically from a single official source (section "3. Review converted permissions"). Related: https://latestn.com/tool/kiro/permissions-and-security/sandbox-allow-hosts How do I allow specific hosts in Kiro sandbox network modes? https://latestn.com/tool/kiro/permissions-and-security/sandbox-credentials-how-they-work How do credentials work in the Kiro sandbox? https://latestn.com/tool/kiro/permissions-and-security/sandbox-custom-allow-list How do I set up a custom allow-list of domains for a Kiro sandbox? https://latestn.com/tool/kiro/permissions-and-security/protected-paths How do I set up protected paths in Kiro and what match types are supported? https://latestn.com/tool/kiro/permissions-and-security/remote-extensions-security What security risks do remote extensions pose in Kiro and how should I handle them? https://latestn.com/tool/kiro/permissions-and-security/required-iam-permissions-general What IAM permissions does Kiro require for general use? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:14:11Z | changed | command that creates rules: /upgrade-agent → — | [1] 2026-11-13T03:37:15Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/review-converted-permissions/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/review-converted-permissions POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/review-converted-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/review-converted-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I review converted permissions after upgrading Kiro CLI to V3? Revision 2, last verified 2026-11-20T13:21:03Z. https://latestn.com/tool/kiro/permissions-and-security/review-converted-permissions (accessed 2026-11-21T10:04:38Z). @misc{LatestN_tool_kiro_permissions_and_security_review_converted_permissions_r2, title = {How do I review converted permissions after upgrading Kiro CLI to V3?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/review-converted-permissions}}, note = {Revision 2; digest sha256:1ad87116d4bfcca9; last verified 2026-11-20T13:21:03Z; accessed 2026-11-21T10:04:38Z} } 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/review-converted-permissions