Slash commands are special commands you can use within an interactive chat session to quickly perform actions without leaving the conversation. They start with a forward slash (/) and provide shortcuts for common tasks.
Slash commands are only available in interactive chat mode:
kiro chat > /help
/helpDisplay available slash commands and their usage.
> /help
/quitExit the interactive chat session.
> /quit
Aliases: /exit, /q
/clearClear the current conversation history.
> /clear
Note: This only clears the display, not the saved conversation.
/contextManage context files and view context window usage. Context rules determine which files are included in your Kiro session and are derived from the current active agent.
# Display context rule configuration and matched files > /context show # Add context rules (filenames or glob patterns) > /context add src/app.js > /context add "*.py" > /context add "src/**/*.js" # Remove specified rules > /context remove src/app.js # Remove all rules > /context clear
Available subcommands:
show - Display the context rule configuration and matched filesadd - Add context rules (filenames or glob patterns)remove - Remove specified rulesNotes:
*.py, src/**/*.js)See Context Management for detailed documentation.
/modelSwitch to a different AI model or set your default model preference.
# Show current model > /model # Save current model as default for future sessions > /model set-current-as-default
Available subcommands:
set-current-as-default - Persist your current model selection as the default for all future sessionsNote: The set-current-as-default command saves your current model preference to ~/.kiro/settings/cli.json, so it will be used automatically in all future chat sessions.
/agentManage agents and switch between different agent configurations.
# List all available agents > /agent list # Create a new agent > /agent create my-agent # Edit an existing agent configuration > /agent edit my-agent # Generate an agent configuration using AI > /agent generate # Show agent config schema > /agent schema # Set default agent for new chat sessions > /agent set-default my-agent # Swap to a different agent at runtime > /agent swap code-reviewer
Available subcommands:
list - List all available agentscreate - Create a new agent with the specified nameedit - Edit an existing agent configurationgenerate - Generate an agent configuration using AIschema - Show agent config schemaset-default - Define a default agent to use when kiro-cli chat launchesswap - Swap to a new agent at runtimeNotes:
~/.kiro/agents/ or per-workspace in .kiro/agents/kiro-cli chat --agent agent_namekiro-cli settings chat.defaultAgent agent_nameSee Custom Agents for detailed documentation.
/chatManage chat sessions, including saving, loading, and switching between sessions. Kiro CLI automatically saves all chat sessions on every conversation turn.
# Open interactive session picker to resume a previous session > /chat resume # Save current session to a file > /chat save /myproject/codereview.json # Load a session from a file > /chat load /myproject/codereview.json
Available subcommands:
resume - Open interactive session picker to choose a session to resumesave - Save current session to a fileload - Load a session from a file (.json extension is optional)save-via-script - Save session using a custom script (receives JSON via stdin)load-via-script - Load session using a custom script (outputs JSON to stdout)Notes:
↑/↓ to navigate, Enter to select, / to filterYou can use custom scripts to control where chat sessions are saved to and loaded from. This allows you to store sessions in version control systems, cloud storage, databases, or any custom location.
Save via script:
> /chat save-via-script ./scripts/save-to-git.sh
Your script receives the chat session JSON via stdin. Example script to save to Git notes:
#!/bin/bash set -ex COMMIT=$(git rev-parse HEAD) TEMP=$(mktemp) cat > "$TEMP" git notes --ref=kiro/notes add -F "$TEMP" "$COMMIT" --force rm "$TEMP" echo "Saved to commit ${COMMIT:0:8}" >&2
Load via script:
> /chat load-via-script ./scripts/load-from-git.sh
Your script should output the chat session JSON to stdout. Example script to load from Git notes:
#!/bin/bash set -ex COMMIT=$(git rev-parse HEAD) git notes --ref=kiro/notes show "$COMMIT"
/saveSave the current conversation to a file.
# Save <PATH> > /save /myproject/codereview.json
/loadLoad a previously saved conversation.
# List available conversations > /load /myproject/codereview.json
/editorOpen your default editor (defaults to vi) to compose a prompt.
> /editor
Opens $EDITOR to compose a longer message.
/replyOpen your editor with the most recent assistant message quoted for reply.
> /reply
Useful for referencing and responding to specific parts of the AI's response.
/compactSummarize the conversation to free up context space.
> /compact
Condenses the conversation history while preserving key information, useful when approaching context limits.
/pastePaste an image from clipboard.
> /paste
Adds an image from your system clipboard to the conversation.
/toolsView tools and permissions. By default, Kiro will ask for your permission to use certain tools. You can control which tools you trust so that no confirmation is required.
# View all tools and their permissions > /tools # Show the input schema for all available tools > /tools schema # Trust a specific tool for the session > /tools trust write # Revert a tool to per-request confirmation > /tools untrust write # Trust all tools (equivalent to deprecated /acceptall) > /tools trust-all # Reset all tools to default permission levels > /tools reset
Available subcommands:
schema - Show the input schema for all available toolstrust - Trust a specific tool or tools for the sessionuntrust - Revert a tool or tools to per-request confirmationtrust-all - Trust all tools (equivalent to deprecated /acceptall)reset - Reset all tools to default permission levelsNote: For permanent tool configuration, see Agent Configuration Reference.
/promptsView and retrieve prompts. Prompts are reusable templates that help you quickly access common workflows and tasks. These templates are provided by the MCP servers you have installed and configured.
# List available prompts from a tool or show all available prompts > /prompts list # Show detailed information about a specific prompt > /prompts details code-review # Get a specific prompt by name > /prompts get code-review [arg] # Quick retrieval (without /prompts prefix) > @code-review [arg] # Create a new local prompt > /prompts create my-prompt # Edit an existing local prompt > /prompts edit my-prompt # Remove an existing local prompt > /prompts remove my-prompt
Available subcommands:
list - List available prompts from a tool or show all available promptsdetails - Show detailed information about a specific promptget - Get a specific prompt by namecreate - Create a new local promptedit - Edit an existing local promptremove - Remove an existing local promptQuick tip: To retrieve a prompt directly, use @<prompt name> [arg] without the /prompts get prefix.
See Manage Prompts for detailed documentation.
/hooksView context hooks.
> /hooks
Display active context hooks for the current session.
/usageShow billing and credits information.
> /usage
View your current usage statistics and remaining credits.
/mcpSee MCP servers loaded.
> /mcp
Display Model Context Protocol servers currently active.
/codeManage code intelligence configuration and get feedback.
# Initialize code intelligence in the current directory > /code init # Force reinitialization in the current directory - restarts LSP servers > /code init -f # Get workspace status and LSP server statuses > /code status # View LSP logs for troubleshooting > /code logs # Show last 20 ERROR logs > /code logs -l INFO # Show INFO level and above > /code logs -n 50 # Show last 50 entries > /code logs -l DEBUG -n 100 # Show last 100 DEBUG+ logs > /code logs -p ./lsp-logs.json # Export logs to JSON file
Available subcommands:
init - initialize LSP serversstatus - Show the detailed status of the LSP servers and workspace statuslogs - View logs/experimentToggle experimental features.
> /experiment
Enable or disable experimental CLI features.
/tangentCreate conversation checkpoints to explore side topics.
> /tangent
Enter or exit tangent mode to explore tangential topics without disrupting your main conversation. Use Ctrl+T as a keyboard shortcut (when tangent mode is enabled).
/todosView, manage, and resume to-do lists.
# View todo > /todo # Add todo > /todo add "Fix authentication bug" # Complete todo > /todo complete 1
/issueCreate a new GitHub issue or make a feature request.
> /issue
Opens a workflow to submit issues or feature requests to the Kiro team.
/logdumpCreate a zip file with logs for support investigation.
> /logdump
Generates a diagnostic log bundle for troubleshooting with support.
/changelogView changelog for Kiro CLI.
> /changelog
Display recent updates and changes to the CLI.
In interactive mode, you can also use:
Ctrl+C - Cancel current inputCtrl+J - To insert new-line for multi-line promptCtrl+S - Fuzzy search commands and context files, use tab to select multiple itemsCtrl+T - Toggle tangent mode for isolated conversations (if Tangent mode is enabled)Up/Down arrows - Navigate command history
Slash commands