Answer: The IDE and CLI share the / prefix and Skills appear as slash commands on both, but their built-in command sets differ: IDE built-in commands load content into the agent's context (steering instructions or agent personas), while CLI built-in commands control the chat session itself (switching models, clearing history, inspecting context, rewinding turns, and managing tools). The built-in registries remain surface-specific, so CLI commands like /clear, /model, and /compact do not appear in the IDE menu, and IDE commands like /bug-fix or /architecture-selection are not available in CLI. Status: Confirmed Entry: tool/kiro/commands-and-shortcuts/ide-vs-cli-slash-commands Revision: 1 Digest: sha256:a12c3e4f0b8fc063 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:34Z Last changed: 2026-11-13T03:42:34Z Last verified: 2026-11-20T13:29:17Z Next check: 2026-11-21T13:29:17Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of IDE built-in commands | load content into the agent's context | [1] | 2026-11-20 CLI built-in commands | control the chat session itself | [1] | 2026-11-20 CLI-only commands | /clear , /model , and /compact | [1] | 2026-11-20 IDE-only commands | /bug-fix or /architecture-selection | [1] | 2026-11-20 CLI workflow commands | /plan and /spec | [1] | 2026-11-20 Page updated | October 13, 2026 | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Slash commands - Chat - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/chat/slash-commands/ Role: primary. Accessed: 2026-11-20T13:29:17Z Quote: "IDE built-in commands load content into the agent's context" (Supports: IDE built-in commands) Quote: "CLI built-in commands control the chat session itself" (Supports: CLI built-in commands) Quote: "CLI commands like /clear , /model , and /compact do not appear in the IDE menu" (Supports: CLI-only commands) Quote: "IDE commands like /bug-fix or /architecture-selection are not available in CLI" (Supports: IDE-only commands) Quote: "The CLI also ships workflow commands such as /plan and /spec ." (Supports: CLI workflow commands) Quote: "Page updated: October 13, 2026" (Supports: Page updated) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 13bcca6c8ee2f247bc5f330941cb4923ebd3ff30dc35b5c71d2d8af8990ca9bc (captured 2026-11-20T13:29:18Z) 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:29:17Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:29:17Z Last attempt: 2026-11-20T13:29:17Z Notes and limitations: Extracted automatically from a single official source (section "How IDE commands differ from CLI"). Related: https://latestn.com/tool/kiro/commands-and-shortcuts/inspect-computer-use-cli How can I inspect Computer Use from the Kiro CLI? https://latestn.com/tool/kiro/commands-and-shortcuts/keyboard-shortcuts What keyboard shortcuts are available in Kiro? https://latestn.com/tool/kiro/commands-and-shortcuts/knowledge-add-command How do I add files to a Kiro knowledge base using the /knowledge add command? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:42:34Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/commands-and-shortcuts/ide-vs-cli-slash-commands/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/ide-vs-cli-slash-commands POST: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/ide-vs-cli-slash-commands with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/ide-vs-cli-slash-commands?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do Kiro IDE slash commands differ from CLI slash commands? Revision 1, last verified 2026-11-20T13:29:17Z. https://latestn.com/tool/kiro/commands-and-shortcuts/ide-vs-cli-slash-commands (accessed 2026-11-21T10:08:28Z). @misc{LatestN_tool_kiro_commands_and_shortcuts_ide_vs_cli_slash_commands_r1, title = {How do Kiro IDE slash commands differ from CLI slash commands?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/commands-and-shortcuts/ide-vs-cli-slash-commands}}, note = {Revision 1; digest sha256:a12c3e4f0b8fc063; last verified 2026-11-20T13:29:17Z; accessed 2026-11-21T10:08:28Z} } 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/ide-vs-cli-slash-commands