/. They control session state, configuration, integrations, and tooling — without consuming any AI tokens. Claude never sees them; they are intercepted and handled locally before the message is sent to the model.
Commands are available in the interactive REPL (
claude). Most are not available in non-interactive / pipe mode unless the entry in the table below notes supportsNonInteractive: true.All commands by category
Session & History
Session & History
Configuration
Configuration
MCP & Integrations
MCP & Integrations
Agents & Workflow
Agents & Workflow
Information & Help
Information & Help
How slash commands work
1
Input interception
When you press Enter after typing
/command, Claude Code intercepts the input before it reaches the AI model. The command name is matched against the built-in command registry.2
Argument parsing
Everything after the command name is passed as a raw argument string to the command handler. Commands that accept arguments document them with an
argumentHint, visible in autocomplete.3
Local execution
The command runs locally — modifying session state, opening a UI panel, or performing a system operation. No API call is made unless the command itself triggers one (e.g.
/compact).4
Return to prompt
After the command completes, the REPL returns to the input prompt, ready for the next message or command.
Custom slash commands (skills)
In addition to built-in commands, Claude Code loads skills from:.claude/commands/in the current project directory~/.claude/commands/in your home directory
.claude/commands/ to make them available as slash commands.