Claude Code has a lot of slash commands. Most people use /clear and call it a day.
That's fine, but you're missing a lot. I went through every command available and grouped them properly. Some of these I didn't know existed until I did this.
Session Management
Managing your conversations and context.
/clear (aliases: /reset, /new)
Wipes the current conversation history. Claude forgets everything. Use this when starting a fresh task.
/compact [instructions]
Clears history but keeps a compressed summary. Pass optional instructions to control what the summary focuses on. Better than /clear when you're mid-task and hitting context limits.
/resume [session] (alias: /continue)
Resume a previous session by ID, name, or pick from an interactive list. Useful when you've closed the terminal and want to pick up where you left off.
/rename [name]
Rename the current session. The name shows up on the prompt bar.
/branch [name] (alias: /fork)
Fork the current conversation at this point. Creates a copy you can take in a different direction without losing the original.
/rewind (alias: /checkpoint)
Rewind the conversation (and optionally your code) back to a previous point. Lets you pick which message to roll back to.
/export [filename]
Export the current conversation as plain text. Good for documentation or sharing.
/desktop (alias: /app)
Continue the current session in the Claude Code Desktop app. macOS and Windows only.
/exit (alias: /quit)
Close Claude Code.
Context & Memory
What Claude knows and how to manage it.
/context
Visualises your current context usage as a coloured grid with suggestions for optimisation. Run this when things start feeling slow or you're getting close to limits.
/memory
Edit your CLAUDE.md memory files, manage auto-memory entries, and enable or disable the auto-memory feature.
/init
Creates a CLAUDE.md file in your project root. This is how you give Claude persistent instructions about your codebase, style conventions, and anything else it needs to know. Do this for every project.
/add-dir <path>
Add an additional working directory to the current session. Useful when your project spans multiple directories.
Configuration & Settings
Getting your environment set up right.
/config (alias: /settings)
Opens the settings editor. Theme, model, output style, editor mode — most of the important stuff lives here.
/model [model]
Switch the AI model mid-session. Drop to a cheaper model for simple tasks, bump up to Opus when you need it.
/effort [low|medium|high|max|auto]
Set the model's effort level. max requires Opus 4.6.
/fast [on|off]
Toggle fast mode. Faster responses, same model.
/theme
Change the colour theme. Includes light, dark, and colourblind-accessible options.
/color [color|default]
Set the prompt bar colour for the current session. Options: red, blue, green, yellow, purple, orange, pink, cyan.
/keybindings
Open or create your keybindings configuration file.
/terminal-setup
Configure terminal keybindings (Shift+Enter and similar). Only shows up when your terminal actually needs it.
Work & Productivity
Day-to-day commands for getting things done.
/plan [description]
Enter plan mode. Claude drafts a plan before taking action. Useful for complex tasks where you want to review the approach before anything gets executed.
/diff
Open an interactive diff viewer showing uncommitted changes and per-turn diffs.
/tasks (alias: /bashes)
List and manage background tasks running in the current session.
/btw <question>
Ask a quick side question without adding it to the main conversation context. Like pulling someone aside without derailing the meeting.
/copy [N]
Copy the last assistant response to clipboard. Pass N to copy the Nth-latest response.
Tools & Integrations
Managing what Claude can connect to and do.
/permissions (alias: /allowed-tools)
Manage allow, ask, and deny rules for tool access. Control exactly what Claude is and isn't allowed to do.
/hooks
View your hook configurations. Hooks are shell commands that fire automatically in response to tool events.
/mcp
Manage Model Context Protocol server connections and OAuth authentication. This is how you connect Claude to external tools and data sources.
/agents
Manage agent configurations for subagents.
/skills
List available skills, including any custom ones you've configured.
/plugin
Manage Claude Code plugins.
/reload-plugins
Reload all active plugins to pick up any pending changes.
/ide
Manage IDE integrations and check their status.
/chrome
Configure the Claude in Chrome integration settings.
Developer Workflow
Commands for people shipping actual code.
/security-review
Analyse pending changes on the current branch for security vulnerabilities.
/install-github-app
Set up the Claude GitHub Actions app for a repository.
/install-slack-app
Install the Claude Slack app through an OAuth flow.
Usage & Analytics
Understanding how you're using the tool and what it's costing you.
/cost
Token usage and estimated cost for the current session.
/usage
Show your plan's usage limits and current rate limit status.
/stats
Visualise daily usage, session history, streaks, and model preferences.
/insights
Generate a report analysing your Claude Code sessions over time.
/extra-usage
Configure extra usage to keep working when you hit rate limits.
Account & Authentication
/login
Sign in to your Anthropic account, or switch accounts.
/logout
Sign out.
/privacy-settings
View and update privacy settings. Pro and Max plans only.
/upgrade
Open the upgrade page to move to a higher plan tier.
/passes
Share a free week of Claude Code with a friend, if you're eligible.
Help & Documentation
/help
Show available commands and keyboard shortcuts.
/doctor
Health check your Claude Code installation. Run this first when something's broken.
/status
Version, model, account info, and connectivity status at a glance.
/release-notes
Browse the changelog in an interactive version picker.
/powerup
Discover Claude Code features through short interactive lessons with animated demos. Good for onboarding people who are new to the tool.
/feedback (alias: /bug)
Submit feedback or bug reports directly to Anthropic.
Remote & Scheduling
/remote-control (alias: /rc)
Make the current session available for remote control from claude.ai.
/remote-env
Configure the default remote environment for web sessions started with --remote.
/schedule [description]
Create, update, list, or run scheduled tasks that run in the cloud.
/ultraplan <prompt>
Draft a plan in an ultraplan session, review it in the browser, then execute it remotely.
Miscellaneous
/voice
Toggle push-to-talk voice dictation. Requires a Claude.ai account.
/mobile (aliases: /ios, /android)
Show a QR code to download the Claude mobile app.
/setup-bedrock
Configure Amazon Bedrock authentication. Only relevant if you've set CLAUDE_CODE_USE_BEDROCK=1.
/stickers
Order Claude Code stickers. Yes, really.
Bundled Skills
These show up as slash commands but are implemented as skills under the hood.
/simplify — Review changed code for quality, reuse, and efficiency, then fix issues.
/batch — Research and plan a large-scale change, then execute it in parallel across multiple worktree agents.
/loop — Run a prompt or slash command on a recurring interval.
/debug — Enable debug logging to help diagnose issues.
/update-config — Configure Claude Code hooks and settings via settings.json.
/keybindings-help — Help with customising keyboard shortcuts.
MCP Prompts
If you have MCP servers connected, they can expose their own slash commands using the format /mcp__<server>__<prompt>. These appear dynamically based on what's connected.
Commands That Got Removed
Worth knowing so you stop searching for them.
/pr-comments — Removed in v2.1.91. Just ask Claude directly to view PR comments instead.
/review — Deprecated. Install the code-review plugin if you want this back.
/vim — Removed in v2.1.92. Toggle Vim mode through /config → Editor mode instead.
The Commands I Actually Use
Honest answer: /clear, /compact, /context, /cost, and /memory cover most of my sessions. /init is essential for any new project. /plan is underrated when you're about to do something non-trivial.
If you're setting up a new site from scratch and want a deployment workflow that just works, here's the exact stack this site runs on — Claude Code, GitHub, and Vercel wired together so pushing to main is all you ever have to do.
The rest are there when you need them. Now you know where to look.