Command Quick Reference
Use this page as a lookup table. If you are still learning, start with Core Session Commands, Review and Debug Commands, and Using Skills.
Start here
These are the commands most developers should learn first:
/plan
/context
/compact
/rename
/rc
/ide
/plugin
/simplify
/debugPermission modes
| Input | Mode | Behavior |
|---|---|---|
Shift+Tab (1x) | Auto-Accept | Claude proceeds without asking |
Shift+Tab (2x) | Plan Mode | Read-only, no edits |
Shift+Tab (3x) | Normal | Permission prompts for edits and commands |
--permission-mode auto | Auto Mode | Claude classifies routine permissions automatically |
How to stop confirmations
There are three different ways to reduce or remove confirmation prompts, and they are not equally safe:
1. Best default: commit sane shared permissions
Use .claude/settings.json to pre-approve the commands your team runs constantly. This is the normal team path because it reduces noise without throwing away all guardrails.
2. Session-level pre-approval: --allowedTools
If you want one session to stop asking about a known set of tools, you can pre-approve them on the command line:
claude --allowedTools "Bash(*)" "Edit(*)" "Write(*)" "Read(*)" "WebFetch(*)"That is broad, but it is still more controlled than disabling permissions entirely because you are explicitly naming the tools Claude may use without asking.
3. Full bypass: --dangerously-skip-permissions
This removes permission prompts entirely:
claude --allowedTools "Bash(*)" "Edit(*)" "Write(*)" "Read(*)" "WebFetch(*)" --dangerously-skip-permissionsUse this only when you truly mean it:
- a throwaway sandbox
- a tightly controlled local environment
- automation where you already trust the command surface
Do not treat this as the normal team default. For shared repo work, it is almost always better to tighten permissions.allow or use a narrower --allowedTools set instead of removing the guardrail completely.
Session management
/plan Enter Plan Mode
/context Check context usage
/compact [focus] Compress context and tell Claude what to retain
/rename <name> Name the current session
/rc Enable Remote Control
/clear Reset the conversation
/rewind Selective rollback
/color <color> Color-code the prompt bar
/stats Usage stats for interactive accounts
/usage Rate limit status
/cost Detailed token/cost view when billing context mattersReview and debugging
/simplify [focus] Parallel review pass
/debug Structured debugging workflow
/security-review Security-oriented review of the current change
/permissions Inspect current permission rules
/hooks Inspect current hooksProject utilities
/init Bootstrap a baseline CLAUDE.md
/memory Inspect or edit CLAUDE.md
/skills List available skills
/mcp Authenticate with and manage connected MCP servers
/plugin Open the interactive plugin manager
/ide Install or connect IDE support
/config Configure preferences
/doctor Environment diagnostics
/insights Usage analysis
/release-notes Recent product changesSpeed and scale
/fast Favor speed for straightforward work
/effort <level> Tune reasoning depth
/batch <desc> Parallelizable broad migration
/loop <int> <prompt> Recurring scheduled taskCLI flags
claude
claude "prompt"
claude -p "prompt"
claude -c
claude -r "name"
claude -n "name"
claude -w branch
claude -w branch --tmux
claude -c --fork-session
claude --rc
claude --from-pr 42
claude --bare
claude --permission-mode auto
claude --model opus
claude --effort high
claude --agents
claude --max-turns 20
claude --debug "api,hooks"
claude --chrome
claude mcp add <name> ...
claude mcp list
claude mcp get <name>
claude mcp remove <name>Keyboard shortcuts
Shift+Tab Cycle permission modes
Alt+T Toggle extended thinking
Alt+P Model picker
Ctrl+G Open the current plan in your editor
Ctrl+C Interrupt Claude
Esc+Esc Open the rewind menu
Ctrl+S Screenshot stats
!command Run a raw shell command
@filepath Mention a file pathPlugin reminder
For most teams, the right first step is:
/pluginBrowse what is already installed, then add only what the repo actually needs.