Answer: The best practices are to use --require-mcp-startup in CI/CD when tasks depend on MCP tools, add verbose logging (-v or -vv) when debugging exit code issues, check exit codes explicitly rather than relying on implicit shell behavior, and separate MCP failures from general failures to provide better error messages to users. Status: Confirmed Entry: tool/kiro/commands-and-shortcuts/exit-code-best-practices Revision: 2 Digest: sha256:c2f352e1b0433704 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:33Z Last changed: 2026-11-19T13:23:03Z (Page updated: — → November 18, 2026) Last verified: 2026-11-20T13:31:59Z Next check: 2026-11-21T13:31:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of CI/CD practice | --require-mcp-startup | [1] | 2026-11-20 Debugging practice | -v or -vv | [1] | 2026-11-20 Exit code checking practice | Check exit codes explicitly | [1] | 2026-11-20 Error handling practice | Separate MCP failures from general failures | [1] | 2026-11-20 Page updated | November 18, 2026 | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Exit codes - Commands and Reference - Docs - Kiro". https://kiro.dev/docs/reference/exit-codes/ Role: primary. Accessed: 2026-11-20T13:31:59Z Quote: "Use --require-mcp-startup in CI/CD when your tasks depend on MCP tools" (Supports: CI/CD practice) Quote: "Add verbose logging ( -v or -vv ) when debugging exit code issues" (Supports: Debugging practice) Quote: "Check exit codes explicitly rather than relying on implicit shell behavior" (Supports: Exit code checking practice) Quote: "Separate MCP failures from general failures to provide better error messages to users" (Supports: Error handling practice) Quote: "Page updated: November 18, 2026" (Supports: Page updated) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 6137bfd1d3bfef7777ad565e0657ccc240509e6976f98c2d05903ea49ab694ce (captured 2026-11-20T13:31:57Z) 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:31:59Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:59Z Last attempt: 2026-11-20T13:31:59Z Notes and limitations: Extracted automatically from a single official source (section "Best practices"). Related: https://latestn.com/tool/kiro/commands-and-shortcuts/general-keyboard-shortcuts What are the general keyboard shortcuts in Kiro? https://latestn.com/tool/kiro/commands-and-shortcuts/headless-flags What flags does Kiro CLI headless mode support? https://latestn.com/tool/kiro/commands-and-shortcuts/how-to-use-slash-commands How do I use slash commands in Kiro chat? https://latestn.com/tool/kiro/commands-and-shortcuts/enter-exit-tangent-mode How do I enter and exit tangent mode in Kiro CLI? https://latestn.com/tool/kiro/commands-and-shortcuts/enter-leave-fullscreen How do I enter or leave fullscreen mode in the Kiro CLI? https://latestn.com/tool/kiro/commands-and-shortcuts/essential-slash-commands What are the essential slash commands in the Kiro CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:23:03Z | changed | Page updated: — → November 18, 2026 | [1] 2026-11-19T13:23:03Z | changed | Error handling practice: — → Separate MCP failures from general failures | [1] 2026-11-19T13:23:03Z | changed | Exit code checking practice: — → Check exit codes explicitly | [1] 2026-11-19T13:23:03Z | changed | Debugging practice: — → -v or -vv | [1] 2026-11-19T13:23:03Z | changed | page updated: November 2, 2026 → — | [1] 2026-11-19T13:23:03Z | changed | failure separation: Separate MCP failures from general failures → — | [1] 2026-11-19T13:23:03Z | changed | exit code checking: Check exit codes explicitly → — | [1] 2026-11-19T13:23:03Z | changed | debugging logging: -v or -vv → — | [1] 2026-11-13T03:44:33Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/commands-and-shortcuts/exit-code-best-practices/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/commands-and-shortcuts/exit-code-best-practices POST: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/exit-code-best-practices with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/exit-code-best-practices?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the best practices for using Kiro exit codes? Revision 2, last verified 2026-11-20T13:31:59Z. https://latestn.com/tool/kiro/commands-and-shortcuts/exit-code-best-practices (accessed 2026-11-21T10:06:05Z). @misc{LatestN_tool_kiro_commands_and_shortcuts_exit_code_best_practices_r2, title = {What are the best practices for using Kiro exit codes?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/commands-and-shortcuts/exit-code-best-practices}}, note = {Revision 2; digest sha256:c2f352e1b0433704; last verified 2026-11-20T13:31:59Z; accessed 2026-11-21T10:06:05Z} } 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/commands-and-shortcuts/exit-code-best-practices