A free beginner's guide to Claude Code. Pick your setup, complete your first real task, and understand how to work with AI directly in your files and projects.
What's inside
Last updated April 2, 2026
Claude Code lets AI work directly inside your files and projects instead of just chatting about them. You don't need to be a developer to use it. This guide walks you through setup, your first real task, and everything you need to feel comfortable using it on your own.
Section 1
You've probably used Claude before. You type a question, it gives you an answer. Maybe you've had it draft an email or brainstorm ideas. That's regular Claude, and it works through a chat window.
Claude Code is different. Instead of you copying text into a chat and pasting results back out, Claude Code works directly with the files and folders on your computer. It can read your documents, create new files, edit existing ones, run commands, and build things right where you work.
Think of regular Claude as a conversation partner you brainstorm with over text. Claude Code is more like handing someone the keys to your workspace and saying "here's what I need done."
You don't need to be a programmer to use it. Claude Code is useful for anyone who works with files on their computer. Organizing a project folder, writing scripts to automate repetitive tasks, building a simple website, editing documents, analyzing data. If it lives on your computer, Claude Code can work with it.
It's available for free with a Claude account (with usage limits), or with more capacity on Pro and Team plans. You can learn more about what it can do on the official Claude Code page.
Section 2
There are three ways to run Claude Code. You only need one. Pick whichever matches your comfort level and jump to that section. Once you're set up, skip ahead to Section 6.
Option A: Desktop App (Section 3)
Best for complete beginners. No terminal, no code editor. Just a standalone app you download and open. This is the fastest way to get started if you've never touched a command line.
Option B: IDE Extension (Section 4)
Best for people who already use VS Code, Cursor, or a JetBrains editor (IntelliJ, PyCharm, WebStorm) for work. If you already have one of these open every day, adding Claude Code as an extension keeps everything in one place.
Option C: Terminal (Section 5)
Best for people comfortable with the command line who want the most control and the full feature set.
Not sure? Start with the Desktop App. You can always switch later.
Pick one of the next three sections based on your comfort level.
You don't need to do all three. Complete your chosen setup, then skip to Section 6.
Option A
10 minutes
The simplest path. No terminal, no code editor. Just download, install, and go.
That's it. You're in.
To start working, point Claude Code at a folder on your computer. This is the folder it will be able to read, edit, and work inside. Click Open Folder, navigate to whatever project or directory you want to work in, and select it.
Once a folder is open, you can type requests in the chat and Claude will work directly with the files in that folder. Try something simple like "What files are in this folder?" or "Read the file called notes.txt and summarize it."
For a more detailed walkthrough, check out Anthropic's Desktop App Quickstart guide.
You're set up. Skip to Section 6.
Option B
10 minutes
If you already use VS Code, Cursor, or a JetBrains editor, this keeps Claude Code right where you work.
VS Code / Cursor:
You'll see a Claude Code panel open inside your editor. Sign in with your Claude account, and you're ready to go. Claude can now see the files in whatever project you have open.
You can find the official VS Code extension here.
JetBrains (IntelliJ, PyCharm, WebStorm, etc.):
Note: The JetBrains plugin also requires the CLI to be installed separately (see Section 5 for the install command, but you don't need to use the terminal as your main interface).
For full setup details, check out Anthropic's VS Code guide or JetBrains guide.
You're set up. Skip to Section 6.
Option C
10 minutes
The most direct access to Claude Code. Full feature set, full control.
Install Claude Code:
On Mac or Linux, open your terminal and run:
Mac / Linux
curl -fsSL https://claude.ai/install.sh | bashOn Windows (PowerShell):
Windows PowerShell
irm https://claude.ai/install.ps1 | iexOnce installed, type claude and hit enter. You'll be prompted to sign in with your Claude account on your first run.
Basic usage:
Navigate to whatever folder you want to work in using cd, then run claude to start an interactive session. Claude will be able to see and work with everything in that folder.
You can also run one-off commands without starting a full session:
For a beginner-friendly walkthrough, check out Anthropic's Terminal Guide for New Users. For the full installation reference, see the Setup guide.
You're set up. Continue to Section 6.
Section 6
15 minutes
Setup is done. Now let's do something real.
This works the same regardless of whether you're using the Desktop App, an IDE extension, or the terminal. Open Claude Code in the folder where you keep some work files (documents, notes, a project, anything).
Task 1: Have Claude Code read and explain a file
Type this into Claude Code:
Try This
What files are in this folder? Give me a quick summary of what's here.Claude will scan the folder and describe what it finds. Now pick a specific file and go deeper:
Task 2: Have Claude Code create something from scratch
Try asking Claude Code to build something simple:
Try One of These
Create a file called meeting-prep.md with an agenda template for a 30-minute team standup. Write a Python script that renames all the files in this folder to lowercase. Create a simple HTML page that says 'Hello World' with a dark background.Claude will create the file, show you what it wrote, and ask for your permission before saving it. You're always in control of what actually gets written to your computer.
Section 7
The way you phrase your requests makes a real difference in what you get back. A few principles that help:
Be specific about what you want. "Fix this code" is vague. "The function on line 12 is returning the wrong value when the input is negative" gives Claude something concrete to work with.
Give context about your situation. Claude Code can read your files, but it doesn't know your goals. "I'm building a landing page for my consulting business" is more useful than "make a website."
Tell it what format you want. If you want bullet points, say so. If you want a short answer, say "keep it under 3 sentences." If you want a file created, say where you want it saved.
Push back when something isn't right. If Claude's first attempt misses the mark, don't start over. Say what's wrong: "That's too formal, make it more conversational" or "Good structure but the second section needs more detail." Claude Code remembers the full conversation and can iterate.
Use follow-up questions. Your session is a conversation. You can say "now do the same thing for the other three files" or "actually, change the heading to something catchier." You don't need to re-explain the full context each time.
For more tips, check out Anthropic's Best Practices guide.
Section 8
These are the building blocks that help you understand what Claude Code is doing and how to get the most from it.
Tools and Permissions
Claude Code has built-in tools: it can read files, edit files, search your project, run terminal commands, and search the web. By default, it asks your permission before making changes. You'll see prompts like "Claude wants to edit this file" or "Claude wants to run this command" before anything happens. You can adjust how much autonomy it gets using Shift+Tab to cycle through permission modes. For details, see the Permissions guide.
CLAUDE.md Files
A CLAUDE.md file is a plain text file you can place in any project folder. Claude reads it automatically at the start of every session. Think of it as a set of standing instructions: "always write in this tone," "use these naming conventions," "here's how this project is structured." It's optional, but powerful once you start using Claude Code regularly. You can generate a starter one by typing /init in a Claude Code session. Learn more in the Memory and CLAUDE.md docs.
Slash Commands
These are shortcuts you can type during a Claude Code session:
Full list in the CLI Reference.
You can also create your own custom slash commands using Skills. A Skill is a set of saved instructions that teaches Claude Code how to handle a specific task your way. Instead of re-explaining what you need every session, you build the Skill once and trigger it with a slash command anytime. Anthropic has a full walkthrough on how to build your own Skills.
Plan Mode
When you're working on something complex, you can switch to Plan Mode (press Shift+Tab until you see it). In this mode, Claude reads your files and creates a step-by-step plan for what it would do, but doesn't actually execute anything. You review the plan, approve it, tweak it, or reject it before Claude takes any action. It's a good safety net when you're learning.
Context Window
Claude Code can only hold so much information in a single conversation. When a session gets long, you might notice it starting to lose track of earlier context. If that happens, use /compact to compress the conversation, or start a new session with /clear. You can also use /context to see what's taking up space.
Section 9
Being too vague. "Make this better" doesn't give Claude anything to work with. Be specific about what "better" means to you: shorter, more professional, reorganized, simplified.
Not reading what Claude is doing. Claude Code shows you every action it's about to take. Don't just click "approve" on everything without reading it. Understanding what it's doing is how you learn and how you catch mistakes early.
Approving everything blindly. Claude will ask permission before editing files or running commands. Take a second to read what it's proposing. If something looks wrong or unfamiliar, say no and ask it to explain. You can always undo changes, but it's better to catch issues before they happen.
Starting over instead of iterating. If Claude's first attempt isn't right, you don't need to restart the conversation. Just tell it what to change. "Make the tone more casual" or "remove the third section" is faster than re-explaining everything from scratch.
Ignoring CLAUDE.md. If you find yourself repeating the same instructions every session ("always use this tone," "this project uses Python 3.11"), put those instructions in a CLAUDE.md file. Claude reads it automatically so you don't have to repeat yourself.
Not using Plan Mode for big tasks. If you ask Claude to restructure an entire project or make sweeping changes, use Plan Mode first. Let it show you what it plans to do before it does it.
Section 10
You've got Claude Code set up and you've completed your first tasks. Here's where to go from here.
Take Anthropic's free courses. Anthropic Academy has structured courses that walk you through Claude and Claude Code step by step. Claude Code in Action is the most relevant one if you want to go deeper on what you've learned here. Claude 101 is a good starting point if you want a broader understanding of how Claude works overall. Both are free and available at anthropic.com/learn.
Explore the documentation. Anthropic's Claude Code docs are thorough and beginner-friendly. Start with the Common Workflows page to see what other people are using Claude Code for.
Try it on a real project. The best way to learn is to point Claude Code at something you're actually working on. A report you need to write, a folder that needs organizing, a spreadsheet that needs analyzing. Real tasks teach you faster than practice exercises.
Set up a CLAUDE.md for your main project. Run /init in your most-used project folder and let Claude generate a starting point. Then customize it with your preferences and conventions.
Try the web version. If you want to use Claude Code without installing anything, you can run it directly in your browser at claude.ai/code. No local setup required. Read more about it in the Claude Code on the Web guide.
Learn how it works under the hood. Once you're comfortable with the basics, Anthropic's How Claude Code Works page explains the agentic loop, how Claude decides which tools to use, and why it behaves the way it does.
Join the community. If you get stuck or want to see how other people are using Claude Code, join the Anthropic Discord. There are channels specifically for Claude Code users.
That's everything you need to get started. Claude Code is one of those tools that gets more useful the more you use it. Start with small tasks, build your confidence, and gradually take on bigger projects. The learning curve is gentle and you're always in control of what happens to your files.
If this guide was helpful, check out the other free resources at aydanautomates.com/free-guides.
Find me online: