Guides › New to AI
Claude Code for beginners: how to work on a real project
Updated · Level: Beginner · Facts from Anthropic's own docs. Tips and example prompts are ours.
You don't have to be a developer to use Claude Code on a real project. This page starts with how to install it and open it, including Windows PowerShell if that's how you need to run it, then covers how to ask, how to get a plan before anything changes, how to undo a mistake, and how to stay safe. Which plans include it, and a shorter setup recap: Claude Code explained.
Get it installed and open
You only do the install once. After that, you just open the app or type claude in a terminal. Anthropic's own terminal guide for new users2 is the source for the PowerShell and Terminal steps below. 2,6,1
What you need
- A paid Claude plan: Pro, Max, Ultra, Team or Enterprise. The free plan doesn't include Claude Code. 7,1
- A claude.ai account on that plan, so you can sign in. 8
- A computer that meets Anthropic's requirements: macOS 13 or newer, or Windows 10 (version 1809) or newer, with at least 4 GB of memory and an internet connection. 6
Choose the desktop app or the terminal
There are two common ways to use Claude Code on your computer:
- The Claude desktop app (easiest if you've never used a terminal). You click a Code tab, pick a folder and type in a box, like a chat. You don't need to install the terminal version to use it. 1,2
- The terminal (PowerShell on Windows, or Terminal on a Mac). You type short commands. If you've already been opening Claude Code this way, the Windows and Mac steps below are for you. 2
You can install both. They can work on the same project folder. 1
Option A: the desktop app, with no terminal
- Go to the Claude download page9 and download the installer for Mac or Windows. Run the file to install the app. 9,10
- Open Claude from your Applications folder on a Mac, or from the Start menu on Windows, and sign in with your paid account. 1,10
- Click the Code tab at the top of the sidebar. If you only see icons, hover to see the names. If it asks you to upgrade, you need a paid plan first. 1
- Under the message box, choose Local, then Open folder… and pick your project folder. Start with a small folder you know well, or a copy of it. 1
What you'll see: a chat box, plus controls for the folder and how much Claude can do without asking. In Manual mode it shows you each change and waits for you to approve it. 1
Option B, on Windows: install and open it in PowerShell
You need Windows 10 version 1809 or later. You do not need to run PowerShell as Administrator. 6,2
Anthropic recommends installing Git for Windows as well, so Claude Code can use its Bash tool. It's optional: without it, Claude Code uses PowerShell instead, and you don't have to learn Git. If you don't already have it, download the installer from git-scm.com/downloads/win, run it, and click Next on each screen to keep the defaults. When you see "Adjusting your PATH environment," leave the recommended option selected. If you already have Git, you can skip this. 6,2
- Open PowerShell. PowerShell is Windows' built-in window for typing commands; it comes with Windows. Open the Start menu, type
PowerShell, and open Windows PowerShell or Terminal — not the one that says(x86). You can also hold the Windows key and pressX, then choose Windows PowerShell (or Terminal). A window with a blinking cursor appears. 2 - Check you're in PowerShell, not Command Prompt. The line should start with
PS C:UsersYourName>. If you only seeC:UsersYourName>withoutPS, you're in CMD. Close it and open PowerShell, or use the CMD install command in the note below. 2,6 - Paste the official install command with Ctrl+V or a right-click, then press Enter. The command shows no progress while it downloads, so leave the window open and wait. When it finishes, you should see "Claude Code successfully installed!" 2,6
Windows PowerShell — copy this line, paste it, and press Enter
irm https://claude.ai/install.ps1 | iexOnly if you're in Command Prompt (CMD), not PowerShell
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd- Open a new PowerShell window (close the old one, then open PowerShell again) and type
claude --version, then press Enter. A working install prints a version number, such as2.1.211 (Claude Code). 6
Check that it installed
claude --versionOption B, on a Mac: install and open it in Terminal
You need macOS 13 or later. 2,6
- Open Terminal. Press Cmd+Space to open Spotlight, type
Terminal, and press Enter. A window with a blinking cursor appears. That's where you type commands. 2 - Paste the official install command with Cmd+V, then press Enter. It shows no progress while it downloads; leave the window open and wait. When it finishes, you should see "Claude Code successfully installed!" 2
Mac, Linux or WSL — copy this line, paste it, and press Enter
curl -fsSL https://claude.ai/install.sh | bash- Open a new Terminal window and type
claude --version, then press Enter. A working install prints a version number followed by(Claude Code). 6
On most Linux systems you can open a terminal with Ctrl+Alt+T, or search for Terminal, then use the same install command as on a Mac. 2
The first time you open it: sign in
In the terminal, go to your project folder (next section) and type claude, then press Enter. The first time, Claude Code opens a browser window so you can log in with your claude.ai account. If the browser doesn't open, press c to copy the login URL and paste it into your browser. If the browser shows a login code instead of sending you back, paste that code into the terminal where it says Paste code here if prompted. When login finishes, the terminal shows Login successful and asks you to press Enter to continue. 8,11,2
After that, your sign-in is stored, so you shouldn't have to log in every time. To sign out later, type /logout at the Claude Code prompt. 11,8
In the desktop app, you sign in when you first launch Claude, before you open the Code tab. 1
What you'll see in the terminal: after you're signed in, a text prompt appears, with the version, the current model and your working folder shown above it. You type a message and press Enter to send it. You can't click around in the terminal; use the arrow keys. Type /help to see commands. 11,2
Get into your project folder
In the desktop app, use Open folder… as described above. In the terminal, you first move into the folder, then start Claude Code. Officially that looks like this11
Go to your project folder, then start Claude Code
cd /path/to/your/project
claudecd means "change directory": it points the terminal at a folder on your computer. Replace /path/to/your/project with the real path of your folder. If the path has spaces, put quotes around it, for example cd "C:\Users\YourName\Documents\my project". 11
To copy that path:
- Windows File Explorer: open the folder, click once in the address bar at the top (or press Ctrl+L), then copy the path with Ctrl+C. Or hold Shift, right-click the folder, and choose Copy as path. In PowerShell, type
cd, a space, paste the path, and press Enter. If you pasted quotes and it errors, try it with or without the quotes. - Mac Finder: right-click the folder, hold the Option key, and choose Copy … as Pathname. In Terminal, type
cd, a space, paste with Cmd+V, and press Enter. You can also drag the folder from Finder onto the Terminal window to paste its path.
Then type claude and press Enter. Work in a copy of the folder if you're just getting started, so a change is easy to undo.
How to reopen it next time
- Desktop app: open Claude from the Start menu (Windows) or Applications (Mac), click the Code tab, and open your folder again if it isn't already selected. You shouldn't need to install anything again. 1,10
- Terminal: open a new PowerShell or Terminal window,
cdto your project folder, and typeclaude. Don't run the install command again. 11,2
How to quit
In the terminal, type exit or /exit, or press Ctrl+D twice on an empty prompt. That leaves Claude Code and takes you back to the ordinary PowerShell or Terminal prompt. 2,11
In the desktop app, close Claude the way you close any other app.
Keeping it up to date
If you installed it with the commands above (Anthropic calls this a native install), Claude Code updates itself in the background. Updates take effect the next time you start it. To update immediately, run claude update in a terminal (not inside a Claude Code session). 6
Update Claude Code now
claude updateIf something goes wrong
- "command not found: claude" or "'claude' is not recognized": first close the window and open a new PowerShell or Terminal window, then try
claude --versionagain. The installer often needs a fresh window before the command is found. If it still fails, the install folder isn't on your PATH yet. Anthropic's terminal guide2 has the exact fix; on Windows that's two PowerShell lines that add%USERPROFILE%\.local\binto your PATH, then another new window. 2,6 - "irm is not recognized": you're in Command Prompt, not PowerShell. Open PowerShell, or use the CMD install command above. 2
- "The token '&&' is not a valid statement separator": you're in PowerShell and used the CMD install line. Use the PowerShell command instead. 6
- A 32-bit or "(x86)" error on Windows: close that window and open the Start menu entry named Windows PowerShell or Terminal, without
(x86)in the name. 2 - Anything else looks off: in a terminal, run
claude doctor. It prints a read-only check of your install and settings, with warnings and suggested fixes, without starting a session. 6
Check your install
claude doctorYour first 5 minutes
- Confirm you're on a paid Claude plan and can sign in at claude.ai. 7
- Install the desktop app from claude.com/download, or run the official install command in a new PowerShell or Terminal window, then check it with
claude --version. 9,6 - Sign in when the browser window opens (or when the desktop app asks). 8
- Open your project folder: Open folder… in the desktop app, or
cdto the folder and typeclaudein the terminal. 1,11 - Ask it to look around and explain the folder in plain English, and to change nothing yet. That's the first prompt later on this page.
Before you start work
Once it's installed and open, a few habits will keep you safer. Claude Code shares your plan's limits with your chats. 7,6 If you want the shorter setup recap, it's in Claude Code explained.
- Work in a copy of the folder, or in a folder already saved in git, so a change is easy to undo.
- Start with a small job you can check yourself, not a big rewrite.
- Keep passwords, API keys and other secrets out of the folder and out of the chat. 1,4
How to describe what you want
Talk to it the way you'd brief a careful helper who has never seen the project. Include:
- What you want done, in one or two sentences.
- What's already there, if you know (a website, a form, a folder of files).
- What not to touch (for example: "don't change the design, only the wording").
- How you want it to talk to you: "Explain each step in plain words, and ask before you change anything."
Prompt: describe a job
Don't change anything yet. Then tell me the smallest useful change I could ask for first, and what I'd need to check afterwards.
Prompt: ask it to explain the steps
Ask it to plan before it changes anything
Plan mode tells Claude to look around and propose a plan without editing your files. You can turn it on by prefixing a message with /plan, or with the mode control (in the terminal, Shift+Tab). When the plan is ready, you can approve it, stay in planning and ask for changes, or review each edit yourself. 3
A plain-English request works too, and is a good habit even if you forget the command:
Prompt: plan first, don't change yet
Permission prompts: read them before you say yes
A permission mode sets what Claude can do without asking you first. In Manual mode it asks before most actions that edit files, run commands or use the network. Plan mode explores and writes a plan without editing your source. Accept edits lets file edits through and still asks about many commands. Auto mode lets a second model review actions instead of you. You can change the mode during a session. 3
If you want to see every step, start in Manual or Plan. Anthropic says you're responsible for reviewing proposed code and commands for safety before you approve them. 4
When a prompt appears, read what it's about to do. If you don't understand it, type "Explain this in plain words, and what happens if I say no." You can refuse anything that looks like it's deleting files, sending data, or installing software you didn't ask for.
Checkpoints, undo and git
Claude Code automatically tracks the file edits it makes in a session. To undo them, run /rewind or its alias /undo. You can restore the files, the conversation, or both, back to an earlier prompt. 5
That is a session safety net, not a lasting history. A file that was only changed by a shell command, or by something outside this session, may not be undone that way. Anthropic says checkpoints are not a replacement for version control such as git. 5
If the project already uses git (you'll often see a hidden .git folder, or a site like GitHub), ask Claude to save a snapshot — a "commit" — before a big change, and again after you've checked the result. If it doesn't use git yet, working in a copy of the folder is the simplest backup. You can also ask: "Show me how to save a git snapshot of the current files, in plain words, and wait for me to say go ahead."
Reading its output and errors
You don't have to understand every line of code. You do need to follow the story:
- The plan: which files will change, and why.
- The summary: what it says it did when it finishes.
- The check: how it verified the work, or why it couldn't.
- An error: the exact message, in the words on the screen.
When something fails, paste the error back and ask it to explain. Don't keep saying "try again" without understanding the failure.
Prompt: explain an error
Keep notes in CLAUDE.md
CLAUDE.md is a plain-text notes file in your project that Claude Code reads at the start of every session: your rules, preferences and how the project works. 12 You can type it yourself, or run /init to have Claude draft a starter file from what's already in the folder. If the file already exists, /init suggests improvements rather than overwriting it. 12
Write down the things you keep repeating: "Explain in plain words", "Plan first and wait", "Don't deploy without my go-ahead", and any project-specific rules. Anthropic suggests keeping it short and specific; the more concise the instructions, the more consistently they're followed. 12,13
Prompt: start a notes file
When you're stuck
- Ask it to slow down. "Stop. Summarize where we are, what's done, and what's still uncertain. Don't change anything."
- Start a fresh chat for a new job with
/clear. Anthropic recommends it to save usage. 13 - Rewind if the last change made things worse, then try a smaller request.
- Show it the evidence. Paste the error, a screenshot description, or the page that looks wrong, rather than restating the goal.
- Get a second explanation. "Explain this as if I don't write code. What should I check myself?"
Prompt: when you're stuck
Safe habits
- Don't paste secrets. Leave passwords, API keys, tokens and private account details out of the chat and, when you can, out of the project folder. 4
- Read before you approve. A yes to a command can change or delete files, or reach the network. 4
- Review before you publish or deploy. Open the result yourself (the page, the app, the file). If you don't understand a change, ask for a plain-English walkthrough of what will go live.
- Don't grant more access than the job needs. Stay in Manual or Plan until you trust the routine.
- Watch your usage. Long sessions and harder models use your plan faster. Start a fresh chat between jobs. 13
Prompt: review before anything goes live
When the work is bigger than one session: Projects
In Claude Code, a project is one ongoing conversation where Claude coordinates a stream of related tasks. It starts a parallel thread for each piece of work, answers questions in the project chat, and shows you which threads need you. Most threads run in the cloud and keep going after you close your laptop; if a task needs something only your computer has, you can ask Claude to run that thread on your computer through Remote Control. 14,15
Projects are in public beta on Pro, Max and Ultra, rolling out gradually, and aren't offered on Team or Enterprise yet. How to start one, and a copyable first prompt: Projects in the Claude Code guide.
Want to leave Claude Code running on your computer and steer it from your phone or a browser? That's Remote Control, and it needs the computer to stay on. Control Claude Code from your phone or the web.
Want the main model to do the everyday work and call a stronger model only for hard decisions? That's the Advisor in Claude Code.
Common questions
5 quick questions, answered
Do I have to use PowerShell or a terminal?
No. The Claude desktop app's Code tab is the easiest start, with no terminal. If you do use the terminal, this page walks through opening PowerShell on Windows or Terminal on a Mac, the install command, and how to open your project folder.
Do I run the install command every time?
No. You install once. After that, open the desktop app, or open a new terminal, go to your project folder and type claude.
Do I need to know how to code?
No, not to start. You describe the job in plain English. You do need to read what it plans to do, approve permission prompts, and check the result before you share or publish it.
Can it break my project?
It can change and delete files you allow it to touch. Work in a copy, ask it to plan first, and use rewind or git so you can go back.
What do I do when I don't understand an error?
Paste the message back and ask it to explain in plain words, what it was trying to do, and the safest next step. Don't approve a fix you can't follow.
Related: Claude Code explained: what it is and how to set it up · Control Claude Code from your phone or the web · AI agents, explained for normal people · Get more out of your Claude plan for less · Build a mini-app with AI, no coding · Claude plans and prices
Sources (15)
- Claude Code docs: Get started with the desktop app
- Claude Code docs: Terminal guide for new users
- Claude Code docs: Choose a permission mode
- Claude Code docs: Security
- Claude Code docs: Checkpointing
- Claude Code docs: Advanced setup
- claude.com/pricing
- Claude Code docs: Authentication
- Claude: Download
- Claude Help Center: Install Claude Desktop
- Claude Code docs: Quickstart
- Claude Code docs: How Claude remembers your project
- Claude Help Center: Models, usage and limits in Claude Code
- Claude Code docs: Projects
- Claude Code docs: Remote Control
Last checked Nov 14, 2026.
