Slash commands - Chat - IDE 1.x - Docs - Kiro Loading image... Product * About Kiro * IDE * CLI * Web * Mobile * Crew * Pricing * Downloads For * Enterprise * Startups * Students Community * Overview * Ambassadors * Discord * Events * Powers * Shop * Showcase Resources * Docs * Blog * Changelog * FAQs * Report a bug * Suggest an idea * Billing support Social * * * * * * * English Site Terms License Responsible AI Policy Legal Privacy Policy Cookie Preferences English Loading image... * Apps * CLI * Web * Enterprise * Pricing * Docs * Community * Resources SIGN IN DOWNLOADS Loading image... Get Started Installation Authentication Your first project Models Overview Available models Reasoning effort Features How Kiro works Specs Steering Hooks MCP Permissions Custom agents Agent Skills Powers Cloud sessions Compaction Kiroignore Checkpoints and rewind Built-in tools Configuration scopes IDE 1.x What's new in 1.0 Setup & First Run Editor Chat Autopilot Slash commands Agent notifications Dockable chat Export sessions Terminal Dev servers Experimental Troubleshooting 0.x reference CLI What's new in 3.0 Setup & First Run Terminal UI Chat Voice mode Headless mode ACP Auto complete Experimental 2.x reference Crew Quick start Installation Running 24/7 Chat Agent Capabilities Features Interfaces Apps System & storage Configuration Security Troubleshooting Web Setup & First Run Identity Center Connect your repositories Working with the agent Autonomous mode Automations Memory Configuration Sync Sandbox Mobile - Preview Overview Commands and Reference CLI commands Slash commands Built-in tools Exit codes Settings Billing Overview Managing your subscription Upgrading your plan Downgrading your plan Cancelling your plan Purchasing add-on credits Managing your payments Managing usage notifications Managing your taxes Contacting billing support Deleting your account Related questions Enterprise Concepts Onboarding quickstart Connecting your identity provider Deployment options Subscribe your team Manage subscriptions Governance Monitor and track Settings Managed updates Billing IAM Supported regions Privacy and Security Overview Data protection Code references Compliance validation Infrastructure security IAM permissions Firewalls, proxies, and data perimeters VPC endpoints (AWS PrivateLink) Guides Overview Language support Learn by playing Migration Migrating from Q Developer Migrating from VSCode Upgrading from Q CLI * Docs * * IDE 1.x * * Chat * * Slash commands Copy page View as Markdown Slash commands Copy page View as Markdown Slash commands let you invoke steering files , custom agents , and skills on demand, directly from the chat. Type / in the chat input to see available commands and execute them instantly. Available commands Kiro's slash command menu pulls from several sources: steering files, agents, and skills. When you type / , commands from all sources appear in a single searchable list with no manual registration required. Each command type is identified by an icon: Icon Type # Steering files 🤖 Agents 🌐 Skills Steering files Steering files (shown with the # icon) provide contextual instructions to the agent. Kiro ships with several predefined steering commands, and you can create your own: Predefined by Kiro: Command Description /architecture-selection Performs a systematic architecture analysis on the current feature's requirements and proceeds to design /quick-spec Generates requirements, design, and tasks in a single pass. See Quick Spec /bug-fix Starts a guided bug-fix workflow for diagnosing and resolving issues /bug-fix The login page throws a 403 after upgrading the auth library User-created steering files configured with inclusion: manual or inclusion: auto appear as slash commands. When selected, the file's contents are added to your current conversation context. Auto-inclusion files also activate automatically when your request matches their description field. See Steering for configuration options. Agents Agents (shown with the 🤖 icon) automatically appear as slash commands. Kiro ships with predefined agents, and you can create your own: Predefined by Kiro: Kiro's built-in sub-agents ( /context-gatherer , /general-task-execution ) also appear in the slash command menu. These are normally invoked automatically by the main agent when needed, but you can invoke them directly when you want explicit control, for example when exploring an unfamiliar codebase or delegating a specific task. /context-gatherer How does the authentication flow work in this project? User-created agents automatically appear as slash commands. You can define them at two levels: * Project-level ( .kiro/agents/ ): available only in that workspace * Global ( ~/.kiro/agents/ ): available across all workspaces The filename (without extension) becomes the command name. For example, code-reviewer.md or code-reviewer.json becomes the /code-reviewer slash command. Sample usage: /code-reviewer Review the changes in src/auth/ for security issues See Custom agents for details on creating your own. Skills Skills (shown with the 🌐 icon) automatically appear as slash commands. Type / followed by the skill name to invoke it directly. For example, a skill named pr-review becomes the /pr-review slash command. You can add text after the skill name, and it is passed along to the agent as extra context: /pr-review focus on the authentication changes In the CLI, if the skill body contains $ARGUMENTS or ${N} placeholders, your text is substituted into them; see Passing arguments to a skill . Placeholder substitution into the skill body is currently CLI-only. See Skills for details on creating skills. How to use * Type / in the chat input field * Browse or search the available commands * Select a command and press Enter Best practices Designing commands * Use descriptive names : Choose names that clearly communicate what the command does so you can quickly find the right command. Example: Use /run-e2e-tests instead of a generic name like /test . * Keep commands focused : Create each command for a specific, repeatable task. Avoid combining unrelated workflows into a single command. Example: Use /review-api-security for a security-focused review rather than a broad /review command. * Define the expected outcome : Include enough instruction for the agent to understand what completing the command means. Example: /run-e2e-tests can run the test suite, report failures, and recommend fixes for failing tests. Using commands * Make required input clear : Provide the context or arguments the command needs to do its job. Example: /fix-issue #123 identifies the issue you want the agent to work on. * Add relevant context when needed : Combine slash commands with steering files and # context providers to give the agent additional project or file context. Example: Run /accessibility with #current while your frontend steering files provide your project's UI guidelines. How IDE commands differ from CLI The IDE and CLI share the / prefix, and Skills appear as slash commands on both surfaces. Where they differ is in the built-in command sets each ships: * IDE built-in commands load content into the agent's context: steering instructions or agent personas. The IDE has GUI equivalents for session control (model picker, context panel, history), so its / menu focuses on directing the agent's behavior. * CLI built-in commands control the chat session itself: switching models, clearing history, inspecting context, rewinding turns, and managing tools. The CLI also ships workflow commands such as /plan and /spec . These exist because a terminal has no GUI, so session management must be reachable by typing. The two built-in registries are otherwise independent. 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 the CLI. For the full CLI slash command reference, see CLI slash commands . Page updated: September 2, 2026 Autopilot Agent notifications