0
1
2
3
4
5
6
7
No experience needed

Get Claude Code Running in 5 Minutes

A step-by-step guide to getting superpowers on your Mac. Just follow along — you've got this.

0

Before We Start

One thing you need first.

Claude Code requires a Claude Pro ($20/mo) or Claude Max ($100/mo) subscription. If you already use Claude in the browser, you're set — Claude Code is included with your subscription.

Go sign up or upgrade: claude.ai
Already have Pro or Max? Keep going.
1

Open Terminal

It's already on your Mac. Here's how to find it.

Press Cmd + Space (the keys at the same time), type Terminal, and press Enter.

Terminal

A window will open with some text and a blinking cursor. That's Terminal.

Don't worry. Terminal is just a way to type instructions to your computer. You'll only need to paste a few things — nothing scary.
2

Install Claude Code

One command. 30 seconds.

Copy this command and paste it into Terminal, then press Enter:

curl -fsSL https://claude.ai/install.sh | bash
Terminal
~ % curl -fsSL https://claude.ai/install.sh | bash
Installing Claude Code... Downloading latest release... Installing to ~/.local/bin/claude... Claude Code installed successfully!

Text will scroll by — that's normal. When it's done, you'll see a success message.

Important: After it finishes, close Terminal completely (Cmd + Q) and reopen it. This is so Terminal recognizes the new command.
3

Go to Your Project Folder

Claude Code works inside a folder — like opening a specific document to work on.

You need to tell Terminal which folder to work in. Here's the easiest way:

  1. In Terminal, type cd  (with a space after)
  2. Open Finder and find your project folder
  3. Drag the folder from Finder into the Terminal window — it pastes the path for you
  4. Press Enter
Terminal
~ % cd /Users/you/Desktop/my-project
my-project %
Alternative: Right-click any folder in Finder while holding the Option key — you'll see "Copy as Pathname". Then in Terminal, type cd  and paste.
Don't have a project folder yet? No problem — make one:
mkdir ~/Desktop/my-first-project && cd ~/Desktop/my-first-project
4

Start Claude Code

One word. That's it.

claude

Your browser will open asking you to sign in. Sign in with your Claude account and approve access.

Come back to Terminal. You're in. Start typing.

Terminal — claude
my-project % claude
╭──────────────────────────────────────╮ │ │ │ Welcome to Claude Code! │ │ │ │ Type anything to get started. │ │ │ ╰──────────────────────────────────────╯
You: what can you help me with?
You're in. Claude Code is running. You can talk to it just like you'd talk to a person. Ask it anything.
Something not working? Open troubleshooting.
"I typed claude but it says command not found"

Terminal doesn't know about Claude Code yet. Close Terminal completely (Cmd + Q, not just the window) and reopen it. That fixes it 90% of the time. If it still doesn't work, run the install command from Step 2 again.

"I pasted the command but nothing happened"

Make sure you pressed Enter after pasting. The command won't run until you hit Enter. You should see text start scrolling.

"My browser didn't open for sign-in"

Look in Terminal — there should be a web address (starts with https://). Highlight it, copy it (Cmd + C), open Chrome yourself, and paste it into the address bar.

"Claude is asking me to allow or approve things"

That's normal. Claude Code asks permission before making changes to your files. Read what it's asking and press y (yes) to approve. You can also type n (no) if you're not sure — it won't break anything.

"Claude seems stuck or is taking forever"

Press Escape to stop it. Then rephrase what you asked — sometimes a simpler question gets a better response. If it's really frozen, press Ctrl + C twice to force-cancel.

"I see a bunch of red text or errors"

Don't panic. Copy the error message and paste it right back to Claude: "I got this error, what does it mean?" — Claude is great at explaining and fixing its own errors.

"It says something about rate limits"

You've used a lot of messages in a short time. This is normal on the Pro plan. Wait about 30 minutes and it resets. If this happens a lot, the Max plan ($100/mo) has much higher limits.

"I closed Terminal and lost my conversation"

That's expected — conversations don't save (see Tip 2 below). But any files Claude created are still in your project folder. Open Terminal, type your shortcut, and tell Claude to read those files. You're back.

Still stuck?

Check the official docs: code.claude.com/docs — or just ask Claude itself: "I'm having trouble with [describe problem], can you help me fix it?"

5

Set Up a Shortcut

So you never have to remember the folder path again.

The concept: Each project you work on lives in its own folder. When you open Claude Code, you go to that folder first — that's its world. But typing that folder path every time is annoying.

Here's the fix. Your very first ask to Claude Code — paste this in:

Create a terminal shortcut so that when I type "code" in any new Terminal window, it automatically opens this folder and starts Claude Code. Add it to my ~/.zshrc file.

Claude will create the shortcut for you. Close and reopen Terminal. Now just type code and you're in. Every time.

Make one for each project. Working on a website? Make a website shortcut. Working on a report? Make a report shortcut. You pick the name — whatever feels natural.
6

How to Actually Use It

Read this. It'll save you a lot of confusion.

Tell Claude what you're working on

Every time you start a session, give it context. Don't just jump in with a random question. Think of it like briefing a coworker.

"Hey, I'm working on [project name] today. Here's what I need to do: [describe task]. The relevant files are in this folder."

The more context you give upfront, the better the output.

Claude does NOT remember your conversations

This is the biggest thing to understand.

When you close Terminal, the conversation is gone. Completely. It does not remember what you talked about. This is normal. Don't panic.

The solution is the next two tips.

Files are memory. Not the conversation.

Since conversations disappear, the trick is: save important stuff to files.

Anything you want Claude to know next time — decisions, plans, context, rules — just tell it to save it:

"Save that to a file so you remember next time"

Claude will pick a sensible name and save it. Next session, it can read that file and pick up where you left off. Files live in your project folder. They persist forever.

Create a CLAUDE.md file — your cheat code

There's a special file called CLAUDE.md that Claude Code automatically reads every single time it starts up. You don't need to tell it to — it just does.

"Create a CLAUDE.md file in this project. Put in a summary of what this project is, what we're working on, and any important decisions we've made."

It's like a sticky note on your desk that Claude always reads before saying hi. When you learn something new, just say:

"Update CLAUDE.md with [this new info]"

What is "compaction"?

Don't worry about this — but know what it is so you're not confused when you see it.

Claude Code has a memory limit for each conversation — like a whiteboard. As you work, it fills up. When it's full, Claude "compacts" — it summarizes older stuff to make room.

You might see a message about it. That's fine. If things start feeling off or Claude seems confused, here's what to try (in order):

  1. Press Escape to stop Claude mid-response, then rephrase your question
  2. Type /clear — this resets the conversation without leaving Claude Code. Like wiping the whiteboard but staying in the room.
  3. Type /exit then claude — fully restarts Claude Code fresh

Your files still have everything. Fresh start = fresh brain.

Don't be afraid of it

Seriously. You cannot break your computer with Claude Code. The worst that happens is Claude writes a bad file — and you can just say "undo that."

  • Ask "dumb" questions — Claude is infinitely patient
  • Say "that's wrong" or "try again" — it won't be offended
  • Say "explain what you just did in simple terms" — it will
  • Say "undo that" — it will
  • Close Terminal if things get weird — no harm done
What you want to doWhat to type
Cancel something runningCtrl + C (press twice)
See available commands/help
Quit Claude Code/exit or Ctrl + D
Ask Claude to simplify"Explain this like I'm not technical"
Paste a file path easilyDrag file from Finder into Terminal
Start freshClose Terminal, reopen, type your shortcut

See What Claude Can Actually Do

This is the fun part. Paste this into Claude Code. Let it interview you. Watch what happens.

I just set up Claude Code for the first time. I want you to help me discover something useful you can build for me right now. Ask me 3-4 questions about: - My role and what I do day to day - Tasks that are repetitive or annoying - Things I wish I had a tool for Based on my answers, suggest 2-3 things you could build for me right now — simple, useful tools (like a calculator, a dashboard, a tracker, a formatter, a template generator — whatever fits). I'll pick one, and then you build it as a single HTML file and open it in Chrome so I can see it immediately.

What happens next:

  1. Claude asks about your role and daily work
  2. You chat back and forth — just be natural
  3. Claude suggests 2-3 small tools it could build right now
  4. You pick one
  5. Claude builds it and opens it in your browser
  6. You just got a custom tool built for you in minutes
This is the magic. It's not a demo — it's a real tool, built around YOUR job, that you can use right now. Welcome to superpowers.

You now have superpowers.

The more you use Claude Code, the more you'll discover what it can do. Don't overthink it — just start asking.