Answer: The page lists fixes by symptom: for example, if V2 cannot open a session you created in V3, start V3 and keep V2 sessions available; for a custom agent that is skipped or shows an upgrade warning, review diagnostics; and for a saved session missing from /sessions, see session management troubleshooting. Status: Confirmed Entry: tool/kiro/troubleshooting/cli-sessions-config-after-upgrade Revision: 1 Digest: sha256:0ca9a821995e0439 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:06Z Last changed: 2026-11-13T03:37:06Z Last verified: 2026-11-20T13:20:49Z Next check: 2026-11-21T13:20:49Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of V2 cannot open V3 session fix | Start V3 and keep V2 sessions available | [1] | 2026-11-20 Custom agent skipped fix | Reviewing diagnostics | [1] | 2026-11-20 Custom agent load issue fix | Custom agents troubleshooting | [1] | 2026-11-20 Hooks no longer fire fix | Hooks migration | [1] | 2026-11-20 Trust settings fix | Permissions migration | [1] | 2026-11-20 ACP client capabilities fix | Validate the migrated client | [1] | 2026-11-20 MCP server fails fix | MCP troubleshooting | [1] | 2026-11-20 Setting rejected fix | Troubleshooting settings | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Troubleshooting - CLI - Docs - Kiro". https://kiro.dev/docs/cli/troubleshooting/ Role: primary. Accessed: 2026-11-20T13:20:49Z Quote: "V2 cannot open a session you created in V3 Start V3 and keep V2 sessions available" (Supports: V2 cannot open V3 session fix) Quote: "A custom agent is skipped or shows an upgrade warning Reviewing diagnostics" (Supports: Custom agent skipped fix) Quote: "A custom agent does not load or behaves unexpectedly Custom agents troubleshooting" (Supports: Custom agent load issue fix) Quote: "Hooks from Kiro CLI 2.x no longer fire Hooks migration" (Supports: Hooks no longer fire fix) Quote: "Trust settings from Kiro CLI 2.x no longer apply Permissions migration" (Supports: Trust settings fix) Quote: "An ACP client lost capabilities after moving to V3 Validate the migrated client" (Supports: ACP client capabilities fix) Quote: "An MCP server fails to start or its tools are missing MCP troubleshooting" (Supports: MCP server fails fix) Quote: "A setting is rejected or has no effect Troubleshooting settings" (Supports: Setting rejected fix) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 201ed2b79c9485e0a0d957b136c764f85e2d1749a90ec92cf54b59010ef77a9f (captured 2026-11-20T13:20:48Z) 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:49Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:20:49Z Last attempt: 2026-11-20T13:20:49Z Notes and limitations: Extracted automatically from a single official source (section "Sessions and configuration after an upgrade"). Related: https://latestn.com/tool/kiro/troubleshooting/confirm-running-harness How do I confirm which agent harness is running in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/crew-messages-during-restart What happens to Kiro Crew messages received during a restart? https://latestn.com/tool/kiro/troubleshooting/crew-services-capacity-health How do I view Kiro Crew's services capacity and health status? https://latestn.com/tool/kiro/troubleshooting/check-tls-inspection-affected How do I check whether Kiro is affected by TLS inspection issues? https://latestn.com/tool/kiro/troubleshooting/cli-launch-harness-troubleshooting How do I fix Kiro CLI launch or harness problems? https://latestn.com/tool/kiro/troubleshooting/cli-log-file-locations Where are the Kiro CLI log files located for debugging? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:37:06Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/cli-sessions-config-after-upgrade/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/troubleshooting/cli-sessions-config-after-upgrade POST: https://latestn.com/dispute/tool/kiro/troubleshooting/cli-sessions-config-after-upgrade with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/cli-sessions-config-after-upgrade?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I resolve Kiro CLI session and configuration issues after an upgrade? Revision 1, last verified 2026-11-20T13:20:49Z. https://latestn.com/tool/kiro/troubleshooting/cli-sessions-config-after-upgrade (accessed 2026-11-21T10:06:08Z). @misc{LatestN_tool_kiro_troubleshooting_cli_sessions_config_after_upgrade_r1, title = {How do I resolve Kiro CLI session and configuration issues after an upgrade?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/cli-sessions-config-after-upgrade}}, note = {Revision 1; digest sha256:0ca9a821995e0439; last verified 2026-11-20T13:20:49Z; accessed 2026-11-21T10:06:08Z} } 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/troubleshooting/cli-sessions-config-after-upgrade