Answer: Treat the standard options[] list as authoritative and render only the choices supplied by the agent, and remove CLI v2 permission fields: use the supplied standard options[] and _meta.kiro.consent instead of Request _meta.trustOptions, and return canonical _meta.kiro.consent for a persistent option instead of Response _meta.trustOption. Status: Confirmed Entry: tool/kiro/permissions-and-security/migrate-acp-permissions-consent Revision: 1 Digest: sha256:457871364e3e010f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:11Z Last changed: 2026-11-13T03:37:11Z Last verified: 2026-11-20T13:20:56Z Next check: 2026-11-21T13:20:56Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Request field replacement | Use the supplied standard options[] and _meta.kiro.consent | [1] | 2026-11-20 Response field replacement | Return canonical _meta.kiro.consent for a persistent option | [1] | 2026-11-20 Authoritative options list | Treat the standard options[] list as authoritative | [1] | 2026-11-20 Persistent option metadata | return the original optionId with canonical consent metadata | [1] | 2026-11-20 fsReadPaths behavior | CLI V3 evaluates every path before requesting permission | [1] | 2026-11-20 feedback behavior | Send text as conversational input, not permission metadata | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "ACP client migration - Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/acp-migration/ Role: primary. Accessed: 2026-11-20T13:20:56Z Quote: "Request _meta.trustOptions Use the supplied standard options[] and _meta.kiro.consent" (Supports: Request field replacement) Quote: "Response _meta.trustOption Return canonical _meta.kiro.consent for a persistent option" (Supports: Response field replacement) Quote: "Treat the standard options[] list as authoritative and render only the choices supplied by the agent." (Supports: Authoritative options list) Quote: "then return the original optionId with canonical consent metadata" (Supports: Persistent option metadata) Quote: "Request _meta.fsReadPaths CLI V3 evaluates every path before requesting permission" (Supports: fsReadPaths behavior) Quote: "Response _meta.feedback Send text as conversational input, not permission metadata" (Supports: feedback behavior) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 003b7aafb2f220e2ea06442b5fbf1143a26418be6b7d3da3ebdb0adb13f9e31c (captured 2026-11-20T13:20:56Z) 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:20:56Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:20:56Z Last attempt: 2026-11-20T13:20:56Z Notes and limitations: Extracted automatically from a single official source (section "5. Migrate permissions and consent"). Related: https://latestn.com/tool/kiro/permissions-and-security/migrate-permissions-from-0x How do I migrate my Kiro permissions from 0.x to 1.0? 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/limit-hook-scope How do I limit the scope of Kiro hooks? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:37:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/migrate-acp-permissions-consent/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-acp-permissions-consent POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/migrate-acp-permissions-consent with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/migrate-acp-permissions-consent?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate permissions and consent when moving a Kiro ACP client to CLI V3? Revision 1, last verified 2026-11-20T13:20:56Z. https://latestn.com/tool/kiro/permissions-and-security/migrate-acp-permissions-consent (accessed 2026-11-21T10:04:53Z). @misc{LatestN_tool_kiro_permissions_and_security_migrate_acp_permissions_consent_r1, title = {How do I migrate permissions and consent when moving a Kiro ACP client to CLI V3?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/migrate-acp-permissions-consent}}, note = {Revision 1; digest sha256:457871364e3e010f; last verified 2026-11-20T13:20:56Z; accessed 2026-11-21T10:04:53Z} } 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-acp-permissions-consent