What Claude Code actually is, in plain terms

Not an editor, not autocomplete. A command-line agent that reads your repository, runs commands and iterates until a task is done.

Most descriptions make it sound like autocomplete with extra steps. It is closer to the opposite: you describe an outcome, and it works in your repository until the outcome exists.

The loop

You give it a task in a terminal. It explores the files it thinks are relevant, proposes a change, applies it, runs whatever command verifies it (tests, a build, a type check), reads the output and adjusts. You can stop it at any point, and you approve the plan before it starts if you ask it to plan first.

What makes it different from an editor assistant

• It acts, not just suggests. It edits files and runs commands rather than producing a diff you paste somewhere.
• It works without you. A run can last minutes; you are not steering every step.
• It reads context on demand. Instead of you pasting files, it opens what it needs — which is also why it burns quota faster than chat.

What it is bad at

Broad, ambiguous requests. "Make the app better" produces expensive wandering. Narrow, verifiable tasks — "make this failing test pass", "add pagination to this endpoint", "split this 900-line file" — are where it earns its cost.

What you need to run it

Node.js, a terminal and a plan that includes Claude Code. Pro includes it with modest limits; the Max tiers exist because the limits are the thing you run into, not the features.

How people actually use it

Usually alongside an editor that handles small edits better. The common split is: editor for renames and type fixes, agent for anything measured in "implement this feature".

If you are sizing the plan, the rate-limits guide explains where the ceilings are, and the plan list shows what each tier costs here.

Back to plans →