Answer: The page lists fixes by symptom: confirm which harness is running then save a default harness, use the guidance for launches that still select Classic, follow the reinstall message on Linux machines with older glibc, and see Terminal UI troubleshooting if the terminal UI does not load or renders incorrectly. Status: Confirmed Entry: tool/kiro/troubleshooting/cli-launch-harness-troubleshooting Revision: 2 Digest: sha256:51f7ddbd1a080558 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:06Z Last changed: 2026-11-20T13:20:48Z (Return to V2 fix: — → Return to V2) Last verified: 2026-11-20T13:20:48Z Next check: 2026-11-21T13:20:48Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of V3 session fix | Confirm which harness is running | [1] | 2026-11-20 Classic launch fix | If a launch still selects Classic | [1] | 2026-11-20 Linux glibc fix | Linux machines with older glibc | [1] | 2026-11-20 Missing terminal UI fix | Installation | [1] | 2026-11-20 Scripts/CI fix | Scripts and CI | [1] | 2026-11-20 ACP fix | ACP clients | [1] | 2026-11-20 Return to V2 fix | Return to V2 | [1] | 2026-11-20 Terminal UI fix | Terminal UI troubleshooting | [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:48Z Quote: "Confirm which harness is running , then Save a default harness" (Supports: V3 session fix) Quote: "If a launch still selects Classic" (Supports: Classic launch fix) Quote: "Linux machines with older glibc" (Supports: Linux glibc fix) Quote: "Kiro CLI prints a reinstall message because the terminal UI is missing Installation" (Supports: Missing terminal UI fix) Quote: "A script or pipeline ran on V2 when you expected V3 Scripts and CI" (Supports: Scripts/CI fix) Quote: "An editor connected over ACP started on the wrong harness ACP clients" (Supports: ACP fix) Quote: "You want V2 back Return to V2" (Supports: Return to V2 fix) Quote: "The terminal UI does not load or renders incorrectly Terminal UI troubleshooting" (Supports: Terminal UI 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:48Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:20:48Z Last attempt: 2026-11-20T13:20:48Z Notes and limitations: Extracted automatically from a single official source (section "Launch and harness"). Related: 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/kiro/troubleshooting/confirm-running-harness How do I confirm which agent harness is running in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/change-requirements-after-design How do I change Kiro spec requirements after the design phase is done? https://latestn.com/tool/kiro/troubleshooting/check-mcp-logs How do I check MCP logs in Kiro to troubleshoot a server? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:20:48Z | changed | Return to V2 fix: — → Return to V2 | [1] 2026-11-20T13:20:48Z | changed | Scripts/CI fix: — → Scripts and CI | [1] 2026-11-20T13:20:48Z | changed | Missing terminal UI fix: — → Installation | [1] 2026-11-20T13:20:48Z | changed | Linux glibc fix: — → Linux machines with older glibc | [1] 2026-11-20T13:20:48Z | changed | V2 fix: Return to V2 → — | [1] 2026-11-20T13:20:48Z | changed | Scripts fix: Scripts and CI → — | [1] 2026-11-20T13:20:48Z | changed | Reinstall fix: Installation → — | [1] 2026-11-20T13:20:48Z | changed | Linux fix: Linux machines with older glibc → — | [1] 2026-11-13T03:37:06Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/cli-launch-harness-troubleshooting/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-launch-harness-troubleshooting POST: https://latestn.com/dispute/tool/kiro/troubleshooting/cli-launch-harness-troubleshooting with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/cli-launch-harness-troubleshooting?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix Kiro CLI launch or harness problems? Revision 2, last verified 2026-11-20T13:20:48Z. https://latestn.com/tool/kiro/troubleshooting/cli-launch-harness-troubleshooting (accessed 2026-11-21T10:01:36Z). @misc{LatestN_tool_kiro_troubleshooting_cli_launch_harness_troubleshooting_r2, title = {How do I fix Kiro CLI launch or harness problems?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/cli-launch-harness-troubleshooting}}, note = {Revision 2; digest sha256:51f7ddbd1a080558; last verified 2026-11-20T13:20:48Z; accessed 2026-11-21T10:01:36Z} } 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-launch-harness-troubleshooting