← All sections

Section 2

Setting up your tools

One app, one AI assistant, and a microphone. After that, your AI can install almost everything else for you.

New to all this? If you've never typed a command into a black window before, read Section 0 first. It covers opening the Terminal, running a command, and telling whether it worked. This page assumes you can open a Terminal and paste a command into it.

What you're installing, and why it's short

You might expect a long list here. It isn't one, and that's deliberate.

You need exactly three things to start:

  1. VS Code — the window you write in
  2. An AI assistant living inside it — your pair of hands
  3. A microphone shortcut — so you can talk instead of type
The trick Once those three are working, you don't install anything else by hand. You just ask. "I need to run a Python script" — your AI figures out what's missing and walks you through it. Set up the thing that can set up other things, then stop.

Install VS Code

VS Code is a free app from Microsoft. It's a text editor, but a very good one — and more importantly it's where your AI assistant will live.

  1. Go to code.visualstudio.com and click the big download button. It detects your computer automatically.
  2. Mac: unzip it, then drag Visual Studio Code into your Applications folder. Don't skip the dragging part — if you run it from Downloads it'll act strangely later.
  3. Windows: run the installer. When it offers "Add to PATH", say yes.

On a Mac, do one more thing so you can open projects from the terminal. In VS Code press Cmd+Shift+P, type shell command, and pick "Shell Command: Install 'code' command in PATH".

Now code . in any folder opens it. Small thing, used constantly.

Add your AI — use your subscription, not the API

This is the part where people accidentally spend a lot of money, so read this section slowly.

There are two completely different ways to pay for AI coding help:

Subscription ✅API ❌
What you payA flat fee each monthPer word, forever, no cap
Surprise bills?No. It's the same every month.Yes. This is the famous problem.
How you sign inEmail and password, like any appPasting a long secret key
Right for you?YesNot for now

The API is built for companies running software that serves thousands of people. You're one person learning. Use the subscription.

What's out there

AssistantHow you payRoughlyNotes
Claude CodeSubscription$20 / $100 / $200 a monthVery strong at long multi-step work
OpenAI CodexSubscription$20 or $200 a monthComes with ChatGPT Plus / Pro
GitHub CopilotSubscription$10 a monthCheapest. Best at finishing lines.
KimiSubscriptionVariesHandles very long documents well
QwenPay per useVery cheapAlibaba's. Capable, inexpensive.
DeepSeekPay per useVery cheapStrong at code for the price
OpenRouterPrepaid creditYou top upOne key, hundreds of models. Later.

What to actually pick

Starting out, or the job is small Claude Pro ($20) or ChatGPT Plus ($20). Flat fee, no surprises. Plenty for a page, a script, or a small site.
When the work gets real — a whole app, or long sessions Step up to Claude Max ($100) or ChatGPT Pro.

This isn't showing off. Bigger plans let the assistant hold far more of your project in mind at once and keep working without stopping — exactly what real work needs. On a $20 plan you'll hit a limit mid-thought and lose the thread.

And the useful part: $100 is $100. It cannot become $400 because you made a mistake. For someone learning, a predictable ceiling is worth more than a cheaper price with no ceiling.

You don't need more than one. If you already pay for any of these, use that — no reason to pay twice.

To install Claude Code, open Terminal and run:

curl -fsSL https://claude.ai/install.sh | bash

Lines will scroll past for a minute while it downloads. That's normal — let it finish.

What you should see at the end Claude Code installed successfully

Wording varies slightly between versions. What matters is that it finishes without the word error on the last line.

Then start it and log in:

claude

It'll ask how you want to sign in. Choose the option that says Claude account with subscription — not the Console / API option. A browser window opens, you log in normally, and you're done.

For the VS Code extension: open the Extensions panel on the left (the four-squares icon), search Claude Code, check the publisher says Anthropic, and install. It uses the same login.

Always check the publisher Extensions are made by anyone. Before installing, look at the publisher name — Anthropic, Microsoft, OpenAI, GitHub. Copycat extensions with near-identical names are a real thing. Ten seconds of checking, every time.

The setting that costs people real money

Read this one twice If your computer has something called ANTHROPIC_API_KEY saved in it, Claude Code will ignore your subscription and bill you per word instead — even though you're paying monthly. You'd be paying twice, and the second one has no ceiling.

Check whether you have one. In Terminal:

echo $ANTHROPIC_API_KEY

To remove it for the current terminal window:

unset ANTHROPIC_API_KEY

If it comes back every time you open Terminal, it's saved in a startup file. Ask your AI: "find where ANTHROPIC_API_KEY is being set in my shell config and help me remove it." That's exactly the kind of errand it's good at.

The same idea applies to the others — OPENAI_API_KEY does the same thing to Codex.

OpenRouter — for later, not now

OpenRouter is a middleman. One account, one key, and you can reach hundreds of models — Claude, GPT, Gemini, Qwen, DeepSeek and many more — without signing up to each one separately.

It's worth knowing this exists, because one day you'll want to compare models, or use a cheap one for something boring and an expensive one for something hard. Have a look at the model list on their site; it's genuinely impressive.

But don't start here OpenRouter charges by the word, with no monthly ceiling. That's fine when you know what you're doing. When you don't, it's the setup most likely to hand you a bill you didn't expect.

The specific trap: you ask for something big, the assistant works away in a loop for twenty minutes, and every step of that loop is charged. Nothing went wrong and nobody hacked you — it simply worked hard on your behalf, and you paid for all of it.

Come back to this when you've got comfortable. Until then, a $100 subscription does the same work with a ceiling you can't fall through.
The honest summary Start slowly on a flat monthly plan where mistakes are free. Once you can predict roughly what a task will cost — which takes a few months, not years — OpenRouter becomes a genuinely good tool. Not before.

When you are ready: the tricky part

Here's the bit that confuses everyone, so let's be blunt:

OpenRouter is not a VS Code extension You can't search the extensions panel for "OpenRouter" and install it. It isn't there. People lose a lot of time to this.

OpenRouter is the supply. You still need something inside VS Code to plug it into — and that something is an extension called Cline.

Like a games console: OpenRouter is the electricity, Cline is the console. Neither does anything alone.

  1. Make an OpenRouter account.
    openrouter.ai — sign in with Google, GitHub, or email.
  2. Add a small amount of credit.
    Account menu → Credits → add $10. Start small deliberately: this is your ceiling, and a low ceiling is the whole safety net. Without credit nothing works, and the error won't clearly say why.
  3. Create your key.
    Keys page → Create Key → name it vscode.
    You see it once The key shows a single time. Copy it straight away. Close that window without copying and it's gone for good — you'd have to delete it and make another.
  4. Install Cline in VS Code.
    Extensions panel (four-squares icon, left edge) → search Cline → Install. A new icon appears in the left bar.
  5. Open Cline's settings.
    Click the new Cline icon, then the gear icon at the top of the panel that opens.
  6. Set the provider.
    Find API Provider and choose OpenRouter. The fields beneath will change.
  7. Paste your key into OpenRouter API Key.
    Leave "Use custom base URL" unticked — you don't need it, and ticking it breaks things.
  8. Pick a model from the Model dropdown.
    Hundreds are listed. Start with a familiar Claude or GPT one. You can switch any time.
  9. Ask it something tiny.
    "What files are in this folder?" — harmless, and it proves the connection works.
How to tell it's working Cline answers, and shows a small cost beside the conversation — something like $0.003. Watch that number. It's the habit that keeps this safe: if a task ever jumps to something that makes you wince, stop it.

When it doesn't work

What you seeWhat it means
401 / "invalid key"Key is wrong or has a stray space. Paste it again, carefully.
402 / "insufficient credits"No money on the account. Back to step 2.
429 / "rate limited"Too many requests too fast. Common on free models. Wait, or pick a paid one.
Nothing happensProvider probably isn't set to OpenRouter. Check step 6.
Never put this key in a file It's a key to a wallet with your money in it. It belongs in Cline's settings and nowhere else — not in your code, not in a screenshot, not pasted into a chat. If you think it's leaked, delete it on OpenRouter immediately and make a new one. Ten seconds, and the old one is instantly worthless.

The part that matters more than the model

Read this before paying for anything bigger A more powerful AI without guardrails doesn't give you better work. It gives you wrong work, faster, and with more confidence.

It's tempting to think the answer to disappointing results is a stronger model. Usually it isn't. Almost every time an AI heads off in the wrong direction, it's because nobody told it which direction was right — and the stronger the model, the further it gets before anyone notices.

The fix isn't a bigger subscription. It's a couple of small text files in your project saying what you're building, what you've already ruled out, and what it must never touch.

That's Section 3 — and it's the most important thing on this whole site. Better model, no harness, is the expensive way to go wrong. If you properly read one section, make it that one.

Talk instead of typing

Describing what you want out loud is faster than typing it, and you'll naturally give more detail — which happens to make the AI much better at its job. Two ways to set this up.

Inside VS Code

  1. Extensions panel → search VS Code Speech → publisher must be Microsoft → Install.
  2. It downloads a small speech model. Takes a moment, once.
  3. Now hold the shortcut, talk, and let go when you're done. Like a walkie-talkie.
What you wantMacWindows
Talk into the file you're editingOption+Cmd+VCtrl+Alt+V
Talk to your AI assistantCmd+ICtrl+I

It runs entirely on your own computer. Your voice isn't sent anywhere, and it works with the wifi off.

Choose your own key

If those shortcuts are awkward, change them:

  1. Press Cmd+K then Cmd+S (Windows: Ctrl+K, Ctrl+S) to open Keyboard Shortcuts.
  2. Search voice.
  3. Click the little pencil next to the one you want, press your preferred key combination, hit Enter.
About using a single key Pick a combination, not a plain key on its own. If you bind dictation to just the spacebar, you can no longer type a space — VS Code will start listening instead. Something like Option+Space gives you hold-to-talk without breaking normal typing.

Everywhere else on your Mac

For dictation in any app, not just VS Code:

  1. System Settings → Keyboard → Dictation, switch it on.
  2. Under Shortcut, pick how you want to trigger it — pressing a key twice, or holding one down.

There are also paid apps built specifically for hold-a-key-and-talk that tend to punctuate better. Worth looking at once you know you like working this way, but don't buy anything yet — start with the free one built into VS Code.

Let the AI install the rest

Here's where the effort stops. You've now got something that can set up anything else.

Whenever a project needs a tool you don't have, don't go hunting through websites. Ask:

I'm on a Mac and I want to <what you're trying to do>.

Tell me what I need to install, check whether I already
have it first, and give me the commands one at a time.
Explain what each one does before I run it, and tell me
if any of them change things outside this project folder.

Every clause in that prompt is doing something:

Start with plain HTML

There's enormous pressure in programming to use the newest, most complicated tool. Resist it for now.

The rule If you can build it with plain HTML and CSS — build it with plain HTML and CSS. Only reach for anything heavier when the page genuinely needs to do something.
What you're makingUse
Portfolio, blog, band page, anything you mostly readPlain HTML
Something with a form that just emails youPlain HTML
A page that updates live, logs people in, or saves their stuffNow you need JavaScript
Something with accounts, payments, a databaseJavaScript, and ask for help planning it

Plain HTML has no build step, no dependencies to update, and nothing that can break while you sleep. The page you're reading is plain HTML. It loads instantly on a phone on bad hotel wifi, and it will still work in fifteen years.

Fancy frameworks are built to solve problems that appear at large scale. Borrowing their complexity before you have their problems just gives you the complexity.

When you do need JavaScript: Bun

When a project really does need JavaScript, use Bun.

Historically you'd install four separate tools that all had to agree with each other — and a lot of beginner pain came from them not agreeing. Bun is all four in one program. Fewer parts, fewer arguments.

curl -fsSL https://bun.com/install | bash

Check it landed:

bun --version
What you should see 1.4.2

Any version number means it worked. command not found means the install didn't finish — close the Terminal, open a new one, and try again. New programs often only appear in a fresh window.

The four commands that cover most of what you'll do:

CommandWhat it does
bun initStart a new project here
bun add <name>Add someone else's code to your project
bun installGet everything a project needs (after downloading someone's project)
bun run <file>Run it
If a tutorial says npm Most of the time you can type bun where it says npm and it just works. If it doesn't, that's fine — npm still works too. Nothing is broken, they're simply two tools doing the same job.

Things to try

  1. Open a folder in VS Code and make a file called index.html. Type <h1>hi</h1>, save, and open it in your browser. That's a web page. You've made one now.
  2. Dictate something. Hold the voice shortcut and talk a sentence into a file. Seeing your own words appear is the moment this stops feeling like a chore.
  3. Ask your AI to explain your own folder. "What files are in this project and what does each one do?" Good practice for reading unfamiliar code.
  4. Check for the expensive setting. Run echo $ANTHROPIC_API_KEY. Confirm it prints nothing. Thirty seconds, potentially saves a lot.
  5. Install one thing by asking. Pick anything — Python, Bun, whatever — and have your AI walk you through it instead of searching for instructions. Get used to that being the normal way.