If you are a programming beginner, or not very familiar with command-line tools, this article will introduce, in plain and easy-to-understand terms, the built-in “/” slash commands of the Claude Code tool developed by Anthropic in its v2.0.76 release. These commands are the core control mechanism of Claude Code: you simply type an instruction starting with “/” in the chat interface to quickly manage sessions, check status, and adjust settings, all without writing complex code.

Claude Code is an intelligent coding assistant that runs in the terminal (command line). It can understand your codebase, perform tasks, fix errors, and interact with you through natural language. v2.0.76 is one of the tool's latest stable releases, with a rich set of built-in slash commands that help users operate more efficiently.

Why should you learn about slash commands?

  • Convenient control: These commands act like shortcuts that directly affect the tool's behavior.
  • Beginner-friendly: No programming knowledge required, just type and use.
  • All built-in: The list below covers all of the major built-in commands in v2.0.76 (based on the official documentation and changelog). Custom commands can be created additionally, but this article focuses on the built-in ones.
  • How to use: In a Claude Code session, simply type the command (such as /help) and press Enter. Most commands require no arguments; a few support optional arguments.

Complete list of built-in slash commands

The following are arranged in alphabetical order. Each command includes:

  • Command name
  • Purpose: a brief explanation of what it does.
  • Usage example: how to type it.
  • Beginner tip: why it is useful for beginners, plus things to watch out for.
  1. /add-dir
    Purpose: Add an additional folder so Claude Code can access the files in it.
    Usage example: /add-dir /path/to/your/project/folder
    Beginner tip: Great for multi-folder projects, helping the assistant “see” more content. An incorrect path will prompt you to try again.
  2. /agents
    Purpose: Create, manage, or view subagents (task-specific AI assistants).
    Usage example: /agents (to list) or follow the prompts to create one. Beginner tip: Break large tasks into smaller pieces; beginners can start by viewing the default agents.
  3. /bashes
    Purpose: View or manage tasks running in the background.
    Usage example: /bashes (shows the list, with the option to stop them). Beginner tip: Clean up the background when the tool lags, to avoid using up resources.
  4. /bug
    Purpose: Report a tool problem to the developers.
    Usage example: /bug describe the problem you encountered
    Beginner tip: Reporting bugs helps improve the tool and is highly encouraged.
  5. /clear
    Purpose: Clear the current chat history and restart a fresh session.
    Usage example: /clear
    Beginner tip: A “one-click reset” when the conversation gets messy, like clearing the chat window.
  6. /compact [instructions]
    Purpose: Compress the chat history to save context space (you can optionally specify what to keep).
    Usage example: /compact or /compact keep only the code
    Beginner tip: Use it during long conversations to avoid exceeding the token limit.
  7. /config
    Purpose: Open the settings menu to adjust options such as theme and notifications.
    Usage example: /config
    Beginner tip: Personalize the tool's appearance and behavior; start here.
  8. /context
    Purpose: Show the current context usage (a colorful grid chart).
    Usage example: /context
    Beginner tip: Visually understand how much of the tool's “memory” is used, to avoid going over the limit.
  9. /cost
    Purpose: Show the number of tokens used and a cost estimate.
    Usage example: /cost
    Beginner tip: Paid users can monitor their spending, like checking data usage.
  10. /doctor
    Purpose: Diagnose the tool's health and report potential problems.
    Usage example: /doctor
    Beginner tip: Run this “checkup” first when the tool acts up.
  11. /exit
    Purpose: Safely exit the current session.
    Usage example: /exit
    Beginner tip: Use it when you finish working; you won't lose saved content.
  12. /export [filename]
    Purpose: Export the chat history to a file or the clipboard.
    Usage example: /export chat.txt or /export (clipboard) Beginner tip: Back up important conversations for easy reference later.
  13. /help
    Purpose: Show a list of all available commands with brief descriptions.
    Usage example: /help
    Beginner tip: The most used one! When you forget, use this to look up the manual.
  14. /hooks
    Purpose: Manage automatic hooks (actions triggered when files change).
    Usage example: /hooks
    Beginner tip: Enables automation; beginners can skip it for now.
  15. /ide
    Purpose: Connect an external code editor (such as VS Code).
    Usage example: /ide
    Beginner tip: Seamlessly integrate your editor for a better experience.
  16. /init
    Purpose: Initialize a new project and generate a CLAUDE.md guidance file.
    Usage example: /init
    Beginner tip: A standard template for starting a new project.
  17. /install-github-app
    Purpose: Install and connect the GitHub App.
    Usage example: /install-github-app
    Beginner tip: Essential for GitHub users, simplifying code pushes.
  18. /login
    Purpose: Switch or log in to an Anthropic account.
    Usage example: /login
    Beginner tip: Use it when switching between multiple accounts.
  19. /logout
    Purpose: Log out of the current account.
    Usage example: /logout
    Beginner tip: Protect your privacy on a shared computer.
  20. /mcp
    Purpose: Manage external tool connections (such as GitHub and Jira).
    Usage example: /mcp
    Beginner tip: Extend the tool's capabilities by connecting to commonly used services.
  21. /memory
    Purpose: View or edit persistent notes (stored in CLAUDE.md).
    Usage example: /memory
    Beginner tip: Like a built-in notepad for recording project key points.
  22. /model
    Purpose: Switch the AI model (such as Sonnet or Opus).
    Usage example: /model claude-3-5-sonnet
    Beginner tip: Different models have different speeds/capabilities; experiment to choose.
  23. /output-style [style]
    Purpose: Adjust the response output style (concise/detailed).
    Usage example: /output-style brief
    Beginner tip: Match your personal reading preference.
  24. /permissions
    Purpose: View or manage tool permissions.
    Usage example: /permissions
    Beginner tip: Control the security boundaries to avoid accidental operations.
  25. /plugin
    Purpose: Manage plugin installation and configuration.
    Usage example: /plugin
    Beginner tip: Extend with extra features.
  26. /pr-comments
    Purpose: View GitHub Pull Request comments.
    Usage example: /pr-comments
    Beginner tip: Quickly review feedback during team collaboration.
  27. /privacy-settings
    Purpose: Adjust privacy-related options.
    Usage example: /privacy-settings
    Beginner tip: Protect sensitive data.
  28. /release-notes
    Purpose: View the tool's changelog.
    Usage example: /release-notes
    Beginner tip: Learn about new features and fixes.
  29. /rename <name>
    Purpose: Rename the current session.
    Usage example: /rename my project
    Beginner tip: Manage multiple parallel sessions.
  30. /resume [session]
    Purpose: Restore a previously saved session.
    Usage example: /resume session name
    Beginner tip: Continue interrupted work.
  31. /review
    Purpose: Ask Claude to review code.
    Usage example: /review
    Beginner tip: Automatically find bugs and optimization suggestions.
  32. /rewind
    Purpose: Roll back to a previous checkpoint (undo changes).
    Usage example: /rewind
    Beginner tip: Like an “undo” feature, a lifesaver when you make a mistake.
  33. /sandbox
    Purpose: Enter sandbox mode (restrict network/file access).
    Usage example: /sandbox
    Beginner tip: Test code safely while avoiding risk.
  34. /security-review
    Purpose: Perform a code security review.
    Usage example: /security-review
    Beginner tip: Check for potential vulnerabilities.
  35. /stats
    Purpose: Show usage statistics charts.
    Usage example: /stats
    Beginner tip: View your personal usage habits.
  36. /status
    Purpose: Show the version, account, and connection status.
    Usage example: /status
    Beginner tip: Quickly diagnose whether the tool is working properly.
  37. /statusline
    Purpose: Enable/disable the bottom status bar.
    Usage example: /statusline
    Beginner tip: Display key information in real time.
  38. /terminal-setup
    Purpose: Configure terminal shortcuts.
    Usage example: /terminal-setup
    Beginner tip: Optimize how smoothly you can operate.
  39. /todos
    Purpose: Extract TODO items from the code.
    Usage example: /todos
    Beginner tip: Manage your task list.
  40. /usage
    Purpose: Check usage against your paid limits.
    Usage example: /usage
    Beginner tip: Avoid accidental overspending.
  41. /vim
    Purpose: Switch to Vim editing mode.
    Usage example: /vim
    Beginner tip: For users familiar with Vim; otherwise you can ignore it.

Conclusion

The above is a complete explanation of all the major built-in slash commands in Claude Code v2.0.76. These commands make using the tool simple and efficient, so that even a programming beginner can get started quickly. Begin your exploration with /help and /status, and you will find that Claude Code is powerful yet friendly. If you want to create custom commands (via the .claude/commands folder), or need example code for a specific command, feel free to ask anytime. We hope this article has been helpful, and happy coding!