Learn how to install, configure, and start using Claude Code to automate desktop tasks, fix bugs, manage Git workflows, and build features directly from your terminal, IDE, or desktop app.
This guide covers everything you need to install, configure, and start using Claude Code, Anthropic's agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools. It is written for developers who want to automate repetitive tasks, fix bugs, build features, and manage Git workflows directly from their terminal, IDE, desktop app, or browser.
Before you begin, make sure you have:

Claude Code is an AI-powered coding assistant that understands your entire codebase and can work across multiple files and tools to get things done. It runs on several surfaces: the terminal CLI, VS Code and JetBrains IDE extensions, a standalone desktop app, the web, Slack, and CI/CD pipelines with GitHub Actions and GitLab. Each surface connects to the same underlying Claude Code engine, so your CLAUDE.md files, settings, and MCP servers work across all of them.
The official documentation describes Claude Code as an agentic coding tool. It operates in an agentic loop: it reads your codebase, plans an approach, writes code across multiple files, runs commands, and verifies results. It can automate tasks you keep putting off, such as writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies, and writing release notes.
Here are some of the ways you can use Claude Code, drawn directly from the official documentation:
claude "write tests for the auth module, run them, and fix any failures" from your terminal.claude "commit my changes with a descriptive message".CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standards, architecture decisions, preferred libraries, and review checklists. Claude also builds auto memory as it works, saving learnings like build commands and debugging insights across sessions without you writing anything. Create skills to package repeatable workflows your team can share, like /review-pr or /deploy-staging. Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a commit.# Analyze recent log output
tail -200 app.log | claude -p "Slack me if you see any anomalies"
# Automate translations in CI
claude -p "translate new strings into French and raise a PR for review"
# Bulk operations across files
git diff main --name-only | claude -p "review these changed files for security issues"
/schedule in the CLI. Desktop scheduled tasks run on your machine, with direct access to your local files and tools. /loop repeats a prompt within a CLI session for quick polling.claude --teleport. Teleport requires a claude.ai subscription. Run /desktop to continue your current terminal session in the Desktop app, where you can review diffs visually. Available on macOS and x64 Windows. Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back.
Claude Code can be installed using several methods. The official documentation recommends the native install method for most users.
Native installations automatically update in the background to keep you on the latest version. Use the following commands based on your operating system:
macOS, Linux, WSL:
curl -fsSL https://claude.ai/install.sh | bash
Windows PowerShell:
irm https://claude.ai/install.ps1 | iex
Windows CMD:
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
If you see The token '&&' is not a valid statement separator, you are in PowerShell, not CMD. If you see 'irm' is not recognized as an internal or external command, you are in CMD, not PowerShell. Your prompt shows PS C:\ when you are in PowerShell and C:\ without the PS when you are in CMD. If the install command fails with syntax error near unexpected token, troubleshoot installation to match the error to a fix and for alternative install methods.
brew install --cask claude-code
Homebrew offers two casks. claude-code tracks the stable release channel, which is typically about a week behind and skips releases with major regressions. claude-code@latest tracks the latest channel and receives new versions as soon as they ship. Homebrew installations do not auto-update. Run brew upgrade claude-code or brew upgrade claude-code@latest, depending on which cask you installed, to get the latest features and security fixes.
winget install Anthropic.ClaudeCode
WinGet installations do not auto-update. Run winget upgrade Anthropic.ClaudeCode periodically to get the latest features and security fixes.
You can also install with apt, dnf, or apk on Debian, Fedora, RHEL, and Alpine. The official documentation does not provide the exact commands for these, but they are listed as supported options.
To confirm the installation worked, run:
claude --version
The command prints a version number followed by (Claude Code).
Claude Code requires an account to use. Start an interactive session with the claude command and you will be prompted to log in on first use:
claude
For Claude subscription or Console accounts, follow the prompts to complete authentication in your browser. To switch accounts later or re-authenticate, type /login inside the running session:
/login
You can log in using any of these account types:
/login opens directly on the Cloud gateway screen for you to sign in with corporate SSOOnce logged in, your credentials are stored and you will not need to log in again.
Open your terminal in any project directory and start Claude Code:
cd /path/to/your/project
claude
Replace /path/to/your/project with the path to the project you want to work on. You will see the Claude Code prompt with the version, current model, and working directory shown above it. Type /help for available commands or /resume to continue a previous conversation.
Let us start with understanding your codebase. Try one of these commands:
what does this project do?
Claude will analyze your files and provide a summary. You can also ask more specific questions:
what technologies does this project use?
where is the main entry point?
explain the folder structure
You can also ask Claude about its own capabilities:
what can Claude Code do?
how do I create custom skills in Claude Code?
can Claude Code work with Docker?
Claude Code reads your project files as needed. You do not have to manually add context.
Now let us make Claude Code do some actual coding. Try a simple task:
add a hello world function to the main file
Claude Code will:
Whether Claude Code asks before changing files depends on your permission mode. In default mode, Claude asks for approval before each change. Press Shift+Tab to cycle through modes: acceptEdits auto-approves file edits, and plan lets Claude propose changes without editing. Some accounts also have an auto mode that runs a background safety check and blocks risky actions, returning to prompts only after repeated blocks.
Claude Code makes Git operations conversational:
what files have I changed?
commit my changes with a descriptive message
You can also prompt for more complex Git operations:
create a new branch called feature/quickstart
show me the last 5 commits
help me resolve merge conflicts
Claude is proficient at debugging and feature implementation. Describe what you want in natural language:
add input validation to the user registration form
Or fix existing issues:
there's a bug where users can submit empty forms - fix it
Claude Code will:
There are a number of ways to work with Claude:
Refactor code:
refactor the authentication module to use async/await instead of callbacks
Write tests:
write unit tests for the calculator functions
Update documentation:
update the README with installation instructions
Code review:
review my changes and suggest improvements
Talk to Claude like you would a helpful colleague. Describe what you want to achieve, and it will help you get there.
Here are the most important commands for daily use. Shell commands run from your terminal to start or resume Claude Code. Session commands run inside Claude Code after it starts.
| Command | What it does | Example |
|---|---|---|
claude | Start interactive mode | claude |
claude "task" | Run a one-time task | claude "fix the build error" |
claude -p "query" | Run one-off query, then exit | claude -p "explain this function" |
claude -c | Continue most recent conversation in current directory | claude -c |
claude -r | Resume a previous conversation | claude -r |
| Command | What it does | Example |
|---|---|---|
/clear | Clear conversation history | /clear |
/help | Show available commands | /help |
/exit or Ctrl+D twice | Exit Claude Code | /exit |
See the CLI reference for the complete list of shell commands and the commands reference for the complete list of session commands.
For more, see best practices and common workflows in the official documentation.
Instead of: "fix the bug" Try: "fix the login bug where users see a blank screen after entering wrong credentials"
Break complex tasks into steps:
1. create a new database table for user profiles
2. create an API endpoint to get and update user profiles
3. build a webpage that allows users to see and edit their information
Before making changes, let Claude understand your code:
analyze the database schema
build a dashboard showing products that are most frequently returned by our UK customers
/ to see all commands and skillsShift+Tab to cycle permission modesThe official documentation mentions a few common issues:
syntax error near unexpected token: This typically means you are using the wrong shell. Check your prompt: PS C:\ means PowerShell, C:\ without PS means CMD. Use the correct install command for your shell.The token '&&' is not a valid statement separator: You are in PowerShell, not CMD. Use the PowerShell install command instead.'irm' is not recognized as an internal or external command: You are in CMD, not PowerShell. Use the CMD install command instead./login inside the running session to re-authenticate or switch accounts.Now that you have learned the basics, explore more advanced features:
For help, type /help in Claude Code, browse the documentation, or join the Discord community for tips and support.
Learn how to run Claude Code in CI/CD pipelines without interactive prompts. Covers authentication, permission configuration, GitHub Actions and GitLab CI integration, and troubleshooting common issues.
Complete guide to Claude Code settings, permissions, and configuration scopes. Learn how to manage user, project, local, and managed settings, use the /config command, and handle invalid entries.
Learn to use the Claude Message Batches API for cost-effective, high-throughput processing of multiple prompts. Covers setup, batch creation, monitoring, result retrieval, and troubleshooting with practical examples.
Learn how to connect Claude Code to your database using the Model Context Protocol (MCP). This guide covers setup, configuration, querying, and advanced usage with real-world examples.
Learn how to set up Claude Code with GitHub Actions for automated code review, issue triage, and CI/CD workflows. Covers workflow configuration, authentication, CLI flags, and best practices.
Learn how to write Claude system prompts that produce measurably better results using hooks, settings, CLAUDE.md files, and permission rules. Covers official Anthropic patterns and community-proven techniques.
Workflows from the Neura Market marketplace related to this Claude resource