Do You Need Claude Pro or Max to Use Claude Code?

Pro is enough. Since you probably arrived mid-search with the pricing page open in the next tab, here's the answer with the numbers attached: Claude Code is included starting at the Claude Pro plan, which costs $17 a month with annual billing ($200 billed up front for the year) or $20 month to month. You do not need Max to use Claude Code. Max, which starts at $100 a month, includes it too, but what Max actually sells is volume, roughly five or twenty times Pro's usage allowance, for people who work in Claude all day. It's an upgrade for heavy use, not the price of admission.

Two clarifications, and then you're free to go. The one plan that won't get you there is Free: Claude Code requires a paid subscription, and Pro is the first rung that includes it. The free plan will happily generate code for you in the chat window; Claude Code, the tool that works on your own computer, is the part that needs Pro. And the same rule covers the rest of the family people search for. Claude Design, Claude Cowork, and Claude Science are all included starting at Pro as well. No Max required for any of them.

That's the whole answer. What follows is for the more interesting question hiding underneath it, the one most people typing that search are actually asking: what is this thing, and is it for someone like me?

What Claude Code actually is

Regular Claude lives in a chat window, and the chat window has a rule you've probably never noticed because you've never seen it broken: you are the courier. Every document Claude reads, you carried in. Every answer it writes, you carry out. It's like working with a brilliant helper through a mail slot. The help is real, but everything passes through that slot one page at a time, and you're the one doing the passing.

Claude Code removes the slot. It runs on your computer, in the terminal (the plain window with the blinking cursor that programmers keep open all day), and it works with your actual files. It reads them. It edits them. It creates new ones, runs commands, and asks your permission before it changes anything. You still talk to it in plain English; "can you rename these so the date comes first" is a perfectly good instruction. The difference is where Claude is standing. Not behind glass anymore. At the workbench.

A session has a rhythm you pick up within minutes. You describe what you want. Claude Code lays out its plan, then narrates as it works: which file it's reading, what it found, what it wants to change and why. When it reaches for anything consequential, it stops and asks. Yes continues; no redirects. The whole exchange reads less like operating software and more like supervising a fast, unusually polite apprentice.

It's called Code because programmers found it first, and it is genuinely a programmer's tool; they use it to build and repair software all day. But the honest, plain-language description is simpler than the name: Claude, with hands.

What a non-programmer does with hands

Once the carrying stops, a particular species of chore becomes conversational. The folder of nine hundred vacation photos named IMG_4471 that you've meant to organize since 2019: Claude Code can read what's actually in there and sort it into folders by year. The bank statement exports scattered through your downloads: it can merge them into one tidy spreadsheet and tell you, step by step, what it did. The little website for your sourdough bakery or your rec-league team: it can build the thing file by file and explain each one in words you'd use with a neighbor.

None of that requires you to write code. It requires you to describe what you want to something that writes it, and then to say yes or no when it asks permission. That permission step matters more than it sounds: Claude Code proposes, you approve, and nothing on your computer changes without your say-so. And for the record, opening the terminal doesn't make you a programmer any more than opening the hood makes you a mechanic. You're allowed to just look around.

The first-timer's fear is usually breakage, so let's name it. Every chore above begins with reading, and reading changes nothing. You can spend an entire session asking questions about what's on your own computer without altering a byte, and the byte-altering, when you're ready for it, happens one approved step at a time.

When you're ready for the full walk-through, from installation to first project, we wrote The Complete Guide to Claude Code for exactly this reader. The catalog on a-gnt keeps two more entries worth bookmarking: CClaude Code Guide, the at-a-glance listing for the tool itself, and CClaude Code Templates, ready-made starting points so your first session begins from something instead of a blank cursor.

What Pro's budget feels like in a session

Now the part where we're honest about what nobody can tell you precisely. Anthropic's pricing page doesn't publish exact message counts or token limits for any plan, so we won't invent them. What it does publish is the structure: Claude Code is included starting at Pro, and Max is sized at roughly 5x or 20x Pro's usage for the people who need more. The structure is the answer restated. Pro is the intended starting point, by design.

Here's the texture underneath that structure. Claude Code draws on your allowance faster than chat does, for a sensible reason: a chat message reads the paragraph you pasted, while a Claude Code session might read your entire folder before deciding what to do. It works in longer stretches on bigger material, so a serious hour at the workbench costs more of your budget than a serious hour of conversation. How much more depends on the project; pointing it at three recipe files is not pointing it at a decade of photos, and no two sessions spend alike, which is one more reason the exact-numbers question has no honest answer.

In practice, that means Pro fits the life of the curious. An evening of tinkering. A weekend spent finally building the bakery site. A few focused sessions a week on a project you care about. What Pro doesn't fit is the person running long sessions every single working day, and that's not a flaw in the plan; it's exactly where Anthropic drew the line between the tiers, and the multipliers exist to absorb exactly that person.

And when you do hit the limit mid-session, it's a pause, not a penalty. You get a notice, then a time when you can resume. Your files never left your computer, so nothing is lost and nothing is locked. The work simply waits for you, which is more than most interruptions can say.

When people upgrade

Watch for three signs, all of them volume-shaped. You hit the ceiling more weeks than you don't. The pause lands in the middle of paid work instead of a hobby evening. And your sessions keep getting longer because the projects got real. When those three arrive together, Max starts making sense: from $100 a month for roughly five times Pro's usage, with a 20x tier above it, plus higher output limits, early access to new features, and priority access at high-traffic times.

Notice what's missing from that list: a smarter Claude. Max doesn't change what Claude Code can do. It changes how long you can keep it doing it, which is precisely what a daily professional user runs out of and a weekend builder doesn't.

But that's a bridge to cross when you're standing on it, with your own usage as evidence. The full decision framework, including the annual-billing math and the one-sentence comparison that settles most cases, lives in this article's companion: Claude Pro vs Max: Which Plan Do You Actually Need?

How to try it without overbuying

The sane path takes one month and twenty dollars.

Subscribe to Pro on monthly billing. Skip annual for now; $200 up front is a good deal on a tool you know you love and a silly one on a tool you haven't met.

Then make your first session deliberately small and completely read-only. Point Claude Code at your messiest folder and ask: "What's in here, and how would you organize it?" It reads, it reports, and nothing changes until you approve something. The prompt takes thirty seconds to type, and the answer is strangely revealing, about your folder and about what this tool actually is. There's a moment, somewhere in that first report, when you realize Claude isn't describing files you pasted. It's describing your files, the real ones, because it's standing in the room with them. That moment is the product.

Spend the rest of the month on whatever that first session makes you want to do next. Then read your own evidence. If Claude Code became part of your week and you never hit a wall, switch to annual billing and keep the $40, which is two months free. If you hit walls repeatedly while doing work that pays, upgrade to Max with receipts in hand. And if it turned out not to be for you, you spent twenty dollars to learn something true, which is cheaper than most lessons.

Either way, the question you searched for has a short answer, and it always did. You don't need the hundred-dollar plan to give Claude hands. You need twenty dollars and a messy folder.