Claude Code

Remember that mockup from the last door — the one that turned out to be the shape of an app you actually wanted built? At some point, somebody has to go and build the thing. And there's a version of Claude made for exactly that moment: one that doesn't just talk about software, but writes it, fixes it, and ships it. It's called Claude Code.

This is the builder's door. I'll say this early, because it matters more than anything else in this lesson: you may never walk through it, and that is completely fine. But it's worth a peek inside — because what lives in this room is genuinely one of the most remarkable things Claude can do.

Talking about code vs. working in the code

Here's the difference that makes it click. In the everyday app, you can ask about code — "what's wrong with this?" — and Claude will explain it, the way it'd explain anything else. Helpful. But it's still a conversation: you're holding the code, and Claude is talking you through it.

Claude Code works the other way around. It sits inside a real software project — the actual pile of files an app is made of — and it can read through the whole thing, change the files itself, and run them to see if they work.

Picture a developer saying, "the login is broken — fix it." Claude Code goes and looks through the project, traces where the trouble actually starts, makes the change, runs a test to confirm it held, and comes back to report what it did. Not a suggestion you then go type out yourself. The actual fix, done.

If "an agent is an LLM with hands" rang a bell from earlier, this is those hands, in a developer's workshop. It's also exactly what we promised back at Cowork: Cowork is this same go-and-do-it power, made simple for non-coders. Claude Code is the original — for the people who build software for a living. It shows up wherever developers already work: in the plain-text terminal, inside their code editor, in the desktop app, on the web. Different entrances, same builder behind them.

You're allowed to walk right past this one

Back in the first course, we sorted people into three kinds: the driver who just wants to use the car well, the mechanic who likes knowing what's under the hood, and the engine designer who builds the thing itself. Claude Code is the engine designer's corner of the house.

So here's your permission slip, plainly. If this sounds thrilling — wonderful, you've already got the perfect foundation to go learn it. If it sounds like someone else's job entirely, that's completely fine too. You can be a confident, capable Claude user and never once open Claude Code. Knowing it exists — knowing the house simply has this room — is the whole goal for now.

Where the build path keeps going

For the curious, two more rooms sit just past this one — quick glances, nothing you need to use.

One is the Platform (you'll also hear it called the API). This is how companies build Claude right into their own apps — so that helpful assistant tucked inside some other website or product you use might quietly be Claude under the hood. They pay for how much they use.

The other is Claude Security — Claude pointed at a project to hunt for safety holes, double-check what it finds, and suggest fixes a human still has to approve. That one's aimed at company security teams more than individuals.

Both sit deep in builder territory. You don't need either. They're just good to know the shape of.

Next door

Notice that every door so far has been about what Claude can do — chat, take on whole tasks, design, build. The next one flips the question around: instead of you going to Claude, how do you bring Claude to the things you already use every day — your email, your calendar, the apps your life actually runs on? That's about connecting Claude to your world, and it's where we head next.