Answer: The AcpTimeoutError occurs when the agent backend doesn't respond to the handshake; common causes include kiro-cli not installed, not logged in, broken MCP config, or slow first launch. Fixes include running kiro-cli login, running kirocrew setup --agent-only --clean to rebuild the agent, or waiting out slow MCP server initialization (60+ seconds). Status: Confirmed Entry: tool/kiro/troubleshooting/acp-timeout-error Revision: 3 Digest: sha256:7c2bfbf70eeb91f5 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:39Z Last changed: 2026-11-20T13:24:39Z (cause: slow first launch: — → 60+ seconds) Last verified: 2026-11-20T13:24:39Z Next check: 2026-11-21T13:24:39Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of error | AcpTimeoutError: ACP prompt timed out | | [1] | 2026-11-20 cause: not installed | kiro-cli not installed | | [1] | 2026-11-20 cause: not logged in | Not logged in | | [1] | 2026-11-20 fix: login | kiro-cli login | | [1] | 2026-11-20 fix: rebuild agent | kirocrew setup --agent-only --clean | | [1] | 2026-11-20 cause: slow first launch | 60+ seconds | seconds | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Troubleshooting - Crew - Docs - Kiro". https://kiro.dev/docs/crew/troubleshooting/ Role: primary. Accessed: 2026-11-20T13:24:39Z Quote: "AcpTimeoutError: ACP prompt timed out" (Supports: error) Quote: "kiro-cli not installed" (Supports: cause: not installed) Quote: "Not logged in — run kiro-cli login" (Supports: cause: not logged in) Quote: "run kiro-cli login" (Supports: fix: login) Quote: "kirocrew setup --agent-only --clean rebuilds the agent from scratch" (Supports: fix: rebuild agent) Quote: "MCP server initialization can take 60+ seconds; wait it out" (Supports: cause: slow first launch) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 1ef2c8e0c370efd0fe2c0d5baf02fb626de0fcd5a09ce13e996e9500079b38e2 (captured 2026-11-20T13:24:40Z) 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:24:39Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:39Z Last attempt: 2026-11-20T13:24:39Z Notes and limitations: Extracted automatically from a single official source (section "AcpTimeoutError: ACP prompt timed out"). Related: https://latestn.com/tool/kiro/troubleshooting/agent-not-found-wrong-version Why is my Kiro custom agent not found or loading the wrong version? 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/settings/windows-shell-selection How do I change the shell used by the terminal on Windows in Kiro? https://latestn.com/tool/kiro/troubleshooting/access-denied-after-sign-in How do I fix Kiro Web showing access denied after IAM Identity Center sign-in? https://latestn.com/tool/kiro/troubleshooting/acp-migration-troubleshooting How do I troubleshoot a Kiro ACP client migration that hangs or fails after upgrading to CLI V3? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:24:39Z | changed | cause: slow first launch: — → 60+ seconds | [1] 2026-11-20T13:24:39Z | changed | fix: rebuild agent: — → kirocrew setup --agent-only --clean | [1] 2026-11-20T13:24:39Z | changed | fix: login: — → kiro-cli login | [1] 2026-11-20T13:24:39Z | changed | cause: not logged in: — → Not logged in | [1] 2026-11-20T13:24:39Z | changed | cause: not installed: — → kiro-cli not installed | [1] 2026-11-20T13:24:39Z | changed | error: — → AcpTimeoutError: ACP prompt timed out | [1] 2026-11-20T13:24:39Z | changed | First launch wait time: 60+ seconds → — | [1] 2026-11-20T13:24:39Z | changed | Fix for broken MCP config: kirocrew setup --agent-only --clean → — | [1] 2026-11-20T13:24:39Z | changed | Fix for not logged in: kiro-cli login → — | [1] 2026-11-20T13:24:39Z | changed | Cause: The agent backend didn't respond to the handshake. → — | [1] 2026-11-20T13:24:39Z | changed | Error: AcpTimeoutError: ACP prompt timed out → — | [1] 2026-11-17T13:46:39Z | changed | First launch wait time: — → 60+ seconds | [1] 2026-11-17T13:46:39Z | changed | Fix for broken MCP config: — → kirocrew setup --agent-only --clean | [1] 2026-11-17T13:46:39Z | changed | Fix for not logged in: — → kiro-cli login | [1] 2026-11-17T13:46:39Z | changed | Cause: — → The agent backend didn't respond to the handshake. | [1] 2026-11-17T13:46:39Z | changed | Error: — → AcpTimeoutError: ACP prompt timed out | [1] 2026-11-17T13:46:39Z | changed | first launch wait time: 60+ seconds → — | [1] 2026-11-17T13:46:39Z | changed | fix for broken MCP config: kirocrew setup --agent-only --clean → — | [1] 2026-11-17T13:46:39Z | changed | fix for not logged in: kiro-cli login → — | [1] 2026-11-17T13:46:39Z | changed | cause: The agent backend didn't respond to the handshake → — | [1] 2026-11-17T13:46:39Z | changed | error: AcpTimeoutError → — | [1] 2026-11-13T03:39:39Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/acp-timeout-error/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/acp-timeout-error POST: https://latestn.com/dispute/tool/kiro/troubleshooting/acp-timeout-error with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/acp-timeout-error?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I resolve the AcpTimeoutError when the ACP prompt times out in Kiro Crew? Revision 3, last verified 2026-11-20T13:24:39Z. https://latestn.com/tool/kiro/troubleshooting/acp-timeout-error (accessed 2026-11-21T09:59:41Z). @misc{LatestN_tool_kiro_troubleshooting_acp_timeout_error_r3, title = {How do I resolve the AcpTimeoutError when the ACP prompt times out in Kiro Crew?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/acp-timeout-error}}, note = {Revision 3; digest sha256:7c2bfbf70eeb91f5; last verified 2026-11-20T13:24:39Z; accessed 2026-11-21T09:59:41Z} } 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/acp-timeout-error