Your server is ready and its toolbox is stocked. Now for the exciting part: bringing in an AI helper that can read your files, write real code, and run commands โ right there in the terminal, working alongside you. This module gets Claude Code installed and shows you how to work with it well.
Get Claude Code running and building alongside you.
Meet your new pair programmer
Claude Code is a version of Claude that lives inside your terminal instead of a chat window in a browser. You describe what you want in plain English, and it reads your project's files, writes new ones, edits existing code, and can run commands on your server โ always pausing to ask your permission before it changes anything.
Picture a patient, expert programmer sitting right next to you at the keyboard. You explain the goal in your own words. They do the typing, explain their choices as they go, and check with you before anything risky. That's the relationship you're about to build.
In plain words
Claude Code doesn't take over your computer. It proposes changes, shows you exactly what it wants to do, and waits for your yes before running anything that touches your files or your server.
Two ways to run Claude Code
There are two common setups for using Claude Code on a project like this one. Both genuinely work. This course picks one on purpose, to keep things simple.
Workflow A: run it on your server (what we'll do)
You already know how to connect to your VPS. In this workflow, you connect the same way, then start Claude Code right there. It writes files directly into your project folder on the server โ the exact place your site will live. Nothing needs to be copied or uploaded afterward, because it was never anywhere else. For a first course, this is the simplest path, and it's the one we'll use starting today.
Workflow B: run it on your laptop, then send the files up
The other option is to install Claude Code on your own laptop, build your project there, and then transfer the finished files to your server afterward โ a step usually called "deploying." It's a completely normal way to work, and plenty of professional developers do exactly this. But it adds a moving part: two computers to keep in sync, and an upload step every time something changes. It's worth knowing this exists, but it isn't what this course focuses on.
Why Workflow A for this course
Building directly on the server means there's never a gap between "it works on my computer" and "it works online." One computer, one truth. Simpler for a beginner โ and it's exactly what we'll do for the rest of the course.
Installing Claude Code
Claude Code needs Node.js to run โ the same Node.js you installed back in Module 5. If you skipped that module, go set it up first; everything here builds on it.
Before you type anything
Claude Code updates often, and the exact install command, required Node version, and sign-in flow can change over time. Treat everything below as "the usual way, but confirm it" โ the current, definitive steps always live at docs.claude.com/claude-code (also linked from docs.claude.com).
With that caveat in mind, here's the usual way to install it. Connect to your server over SSH, then run:
npm install -g @anthropic-ai/claude-code
This downloads Claude Code and makes a new claude command available anywhere on your server. Next, move into the project folder you want to work in, and start it up:
claude
The first time you run it, Claude Code will walk you through signing in with your Anthropic account โ the same one from Module 0. Usually, it gives you a link to open in your browser, you approve access there, and you come back to the terminal already signed in. Just follow whatever it shows you on screen; if the exact wording looks a little different from what's described here, that's normal โ trust docs.claude.com over anything else, including this page.
One thing this needs: an active plan
Using Claude, including Claude Code, requires an active Anthropic plan or available credits on your account. Pricing and plan options change over time, so check the current choices directly on Anthropic's site before you get too deep into a project โ you don't want a surprise halfway through.
How to talk to Claude so it actually helps
Claude Code is powerful, but like any collaborator, it works best when you communicate clearly. A few habits make a huge difference:
- State a clear goal. "Make a simple web page that says hello and shows the time" is a great instruction โ specific and small.
- Go one step at a time. Let Claude finish a change and show it to you, then ask for the next one โ rather than piling on five requests at once.
- Ask it to explain what it did. "Explain that in plain English" turns a wall of code into something you actually understand.
- If something breaks, paste the error back. Claude can usually read an error message and fix the problem faster than you could describe it yourself.
- Keep requests small and specific. "Build my whole website" is much harder to review than five small requests in a row.
Safety habits worth building now
Always read what a command actually does before you approve it, even if you don't understand every word. Never paste passwords, API keys, or other secrets into the chat or into a code file โ not even "just to show Claude." And if Claude ever wants to delete or overwrite something that matters, pause and double-check before you say yes.
Hands-on: build something tiny, together
Let's actually use it. This is just a warm-up โ a way to see Claude Code work before Module 7, where we build the real project. It takes about five minutes.
-
Make a project folder
Connect to your server, then create a small folder to work in:
terminalcd ~/apps mkdir hello && cd hello -
Start Claude Code
From inside that folder, run:
terminalclaude -
Ask for something tiny
Once Claude Code is ready, type a request like this one:
inside claudeCreate a tiny web page that says Hello, world and shows today's date, and tell me how to open it. -
Review what it built
Claude will show you the files it wants to create before it creates them, then explain what it did. Read that explanation โ it's genuinely one of the best ways to learn. Don't worry about actually opening or running the page yet; that's exactly what Modules 7 and 8 are for. Right now, just notice this: you described an idea in plain English, and real files now exist because of it.
You did it
You just had a working conversation with an AI that wrote real code on your server. That's the core loop you'll use for the rest of this course โ describe, review, refine.
- Claude Code is Claude running in your terminal โ it reads, writes, and edits files, and runs commands with your OK.
- This course runs it on your server over SSH (Workflow A) โ simpler than building locally and deploying separately (Workflow B).
- Install with
npm install -g @anthropic-ai/claude-code, then runclaudeand sign in โ but always confirm current steps at docs.claude.com. - Talk to it in small, clear steps, and never paste secrets into the chat.