Before you begin
Make sure you have:- A terminal or command prompt open
- A code project to work with
- A Claude subscription (Pro, Max, Team, or Enterprise), Claude Console account, or access through a supported cloud provider
These cases are covered on other pages:
- Never used a terminal before: start with the terminal guide
- Want Claude Code somewhere other than the terminal: Claude Code is also available on the web, as a desktop app, in VS Code and JetBrains IDEs, in Slack, and in CI/CD with GitHub Actions and GitLab. See all interfaces.
Step 1: Install Claude Code
To install Claude Code, open a terminal and run the command for your system. If you haven’t used a terminal before, the terminal guide shows how to open one and paste the command.- Native Install (Recommended)
- Homebrew
- WinGet
macOS, Linux, WSL:On Windows, your prompt shows Windows CMD:The install command shows no progress while it downloads Claude Code. When the installer finishes, open a new terminal window and run
PS C:\ when you’re in PowerShell and C:\ without the PS when you’re in CMD.Windows PowerShell:claude --version. A working installation prints a version number. If your shell says claude isn’t found or isn’t recognized, the install directory isn’t on your PATH yet: see Fix your PATH.If you see The token '&&' is not a valid statement separator, you’re in PowerShell, not CMD. If you see 'irm' is not recognized as an internal or external command, you’re in CMD, not PowerShell.If the install command fails with syntax error near unexpected token '<', a 403, or any other error, see Troubleshoot installation to match the error to a fix and for alternative install methods.Git for Windows is recommended on native Windows so Claude Code can use the Bash tool. If Git for Windows is not installed, Claude Code uses PowerShell as the shell tool instead. WSL setups do not need Git for Windows.Native installations automatically update in the background to keep you on the latest version.
(Claude Code).
Step 2: Start your first session
Open your terminal in any project directory and start Claude Code:/path/to/your/project with the path to the project you want to work on.
Claude Code prompts you to log in on first use. For Claude subscription or Console accounts, follow the prompts to complete authentication in your browser. If you’ve set the ANTHROPIC_API_KEY environment variable and you approve the key when Claude Code asks whether to use it, Claude Code skips the login prompt.
You can log in using any of these account types:
- Claude Pro, Max, Team, or Enterprise (recommended)
- Claude Console (API access with pre-paid credits). On first login, a “Claude Code” workspace is automatically created in the Console for centralized cost tracking.
- Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry (enterprise cloud providers)
- A self-hosted Claude apps gateway, if your organization runs one: your admin pre-configures the gateway URL, and
/loginopens directly on the Cloud gateway screen for you to sign in with corporate SSO
/help for available commands or /resume to continue a previous conversation. To switch accounts later or re-authenticate, type /login inside the running session.
Step 3: Ask your first question
Try one of these commands:Claude Code reads your project files as needed. You don’t have to manually add context.
Step 4: Make your first code change
Try a small task:Shift+Tab at any time to switch the permission mode of the session you’re in.
Step 5: Use Git with Claude Code
Claude Code makes Git operations conversational:Step 6: Fix a bug or add a feature
Describe what you want in natural language:Step 7: Test out other common workflows
Try a few more prompts. You can ask Claude to refactor code, write tests, update documentation, or review your changes:Essential commands
Here are the most important commands for daily use, grouped by where you run them.Shell commands
Run these from your terminal to start or resume Claude Code.
See the CLI reference for the complete list of shell commands.
Session commands
Run these inside Claude Code after it starts.
See the commands reference for the complete list of session commands.
Pro tips for beginners
For more, see best practices and common workflows.Be specific with your requests
Be specific with your requests
Instead of: “fix the bug”Try: “fix the login bug where users see a blank screen after entering wrong credentials”
Use step-by-step instructions
Use step-by-step instructions
Break complex tasks into steps:
Let Claude explore first
Let Claude explore first
Before making changes, let Claude understand your code:
Save time with shortcuts
Save time with shortcuts
- Type
/to see the commands and skills available to you - Use Tab for command completion
- Press ↑ for command history
- Press
Shift+Tabto cycle permission modes
What’s next?
Now that you’ve learned the basics, explore more advanced features:- How Claude Code works: understand the agentic loop, built-in tools, and how Claude Code interacts with your project
- Best practices: get better results with effective prompting and project setup
- Common workflows: step-by-step guides for common tasks
- Extend Claude Code: customize with CLAUDE.md, skills, hooks, MCP, and more
Getting help
- In Claude Code: type
/helpor ask a “how do I” question - Documentation: browse the other guides on this site
- Courses: take Claude Code 101 and other free self-paced courses on Claude Academy
- Community: join the Discord server for tips and support