Answer: Read the first lines of the session: a V3 session opens with "Welcome to Kiro CLI V3" and lists kiro-cli --v2 as the way to launch the previous experience, while a V2 session opens with "Kiro CLI V3 is here." To confirm your saved default, run kiro-cli settings chat.agentEngine, or kiro-cli settings acp.agentEngine for ACP clients. Status: Confirmed Entry: tool/kiro/troubleshooting/confirm-running-harness Revision: 1 Digest: sha256:b5d461a4fb8643dc (changes whenever the content changes) Timeline: Created: 2026-11-13T03:36:07Z Last changed: 2026-11-13T03:36:07Z Last verified: 2026-11-20T13:19:19Z Next check: 2026-11-21T13:19:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of V3 session opening | Welcome to Kiro CLI V3 | [1] | 2026-11-20 V2 session opening | Kiro CLI V3 is here. | [1] | 2026-11-20 Launch previous experience | kiro-cli --v2 | [1] | 2026-11-20 Upgrade command | kiro-cli --v3 | [1] | 2026-11-20 Confirm saved default | kiro-cli settings chat.agentEngine | [1] | 2026-11-20 ACP clients setting | kiro-cli settings acp.agentEngine | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Choose an agent harness - CLI - Docs - Kiro". https://kiro.dev/docs/cli/agent-harness/ Role: primary. Accessed: 2026-11-20T13:19:19Z Quote: "A V3 session opens with Welcome to Kiro CLI V3" (Supports: V3 session opening) Quote: "A V2 session opens with Kiro CLI V3 is here." (Supports: V2 session opening) Quote: "lists kiro-cli --v2 as the way to launch the previous experience instead" (Supports: Launch previous experience) Quote: "To upgrade, run: kiro-cli --v3" (Supports: Upgrade command) Quote: "To confirm your saved default, run kiro-cli settings chat.agentEngine" (Supports: Confirm saved default) Quote: "or kiro-cli settings acp.agentEngine for ACP clients" (Supports: ACP clients setting) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 4964a4b66739496e7725c1f9a7986bc1b90cd4dd169584d3a13307f79e7ee7c1 (captured 2026-11-20T13:19:17Z) 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:19:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:19:19Z Last attempt: 2026-11-20T13:19:19Z Notes and limitations: Extracted automatically from a single official source (section "Confirm which harness is running"). Related: 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/debug-agent-behavior How do I debug missing context, MCP server issues, or test a Kiro custom agent configuration? 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/kiro/troubleshooting/cli-sessions-config-after-upgrade How do I resolve Kiro CLI session and configuration issues after an upgrade? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:36:07Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/confirm-running-harness/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/confirm-running-harness POST: https://latestn.com/dispute/tool/kiro/troubleshooting/confirm-running-harness with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/confirm-running-harness?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I confirm which agent harness is running in Kiro CLI? Revision 1, last verified 2026-11-20T13:19:19Z. https://latestn.com/tool/kiro/troubleshooting/confirm-running-harness (accessed 2026-11-21T10:07:04Z). @misc{LatestN_tool_kiro_troubleshooting_confirm_running_harness_r1, title = {How do I confirm which agent harness is running in Kiro CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/confirm-running-harness}}, note = {Revision 1; digest sha256:b5d461a4fb8643dc; last verified 2026-11-20T13:19:19Z; accessed 2026-11-21T10:07:04Z} } 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/confirm-running-harness