Your first coding agent: the smallest useful setup

A coding agent is an AI that doesn’t just answer — it acts: creates files, writes code, checks its own work, and reports back. That is the “implementer” role the second lesson warns about: the work is fine to hand over, the understanding is not. So keep the oracle stance from that lesson — the agent implements, you stay the one who decides and understands. Here is the smallest setup that actually does something useful — a small website, in a folder, on your own laptop.

Pick your agent: three good options

One tool, one command, one login — and you pick which one. All three below do the same job: they read your folder, write files, run commands and ask before anything risky. What differs is what they cost to start:

They all work on Windows, macOS and Linux, and all three ask before they do anything risky — which is exactly why a non-programmer can drive them safely.

The setup, step by step

The loop you just started

Every coding agent runs the same cycle. Knowing it makes the whole thing predictable:

The first prompt (copy it)

Make me a small personal page in this folder as index.html.

About me: [name, what you do, one interesting fact]
The page needs: a short intro, 3 facts about me, and my contact email [email].
Style: clean and modern, dark background, one accent color of your choice.
Then explain to me in 3 sentences what files you created and what each does.

That last paragraph — “explain what you created” — is the oracle mindset again. The agent does the work, you keep the understanding.

What a first session actually looks like

1$ claude --version
2x.y.z (Claude Code)
3 
4$ claude
5 
6> Make me a small personal page as index.html.
7 
8● Creating index.html...
9● Writing HTML + CSS... done.
10 
11Done. Created:
12- index.html (your page: header, 3 facts, contacts)
13 
14Open it in your browser to see the result.
15 
16> make the accent color red instead
17● Updating index.html... done. Accent color changed to red.
18 
19> /exit
20Bye.

See the rhythm: you ask, it acts, you review, you refine. Ten rounds like this and you have a real page — and a real skill. Whichever of the three you installed, the transcript looks the same; only the program name and the colors change.

Rules of the safe road

• One folder per project. Always start the agent inside a fresh, empty folder. Never run it in “Documents” or at the top of your disk. Deleting the whole experiment is then one keypress.

• Read before you approve. The agent asks before significant actions. The permission dialog is not a formality — it’s the steering wheel. Here is one, so you know what it looks like before you meet it for real:

  The agent asking first

  press the button below to send the first message

  sent to the modelnothing yet — every message is sent in full

  send next →↻ restart

  Press send next → and watch the middle of the transcript: the agent stops and asks before it touches anything, and nothing moves until you answer — it asks before acting outside its folder, and before anything destructive inside it, like this delete. Notice the two outcomes: say no, and the files stay exactly as they were; say yes, and the change lands. Now read that middle button carefully: “yes, and don’t ask again” is not the same as “yes” — it is yes plus a standing permission, so the next action of that kind happens without asking you. Say yes often. Say “don’t ask again” only when you would be fine never being asked about that exact action again.

• Wrong result? Just say so. “The email section is missing, add it” is a complete instruction. No restarting, no reinstalling.

• Lost? Exit and re-enter. Type /exit (or press Ctrl+D) to quit — in some tools it’s /quit or pressing Ctrl+C twice. To stop something mid-run, press Ctrl+C: that cancels the current action, it doesn’t quit the agent. Worst case, close the terminal window; nothing is lost.

• Hit a limit? That’s the plan, not a bug. On a free plan you will eventually get “come back later” or a smaller model at busy times. Switch to a lighter model, or wait it out.

• It can be wrong about its own work. The page might not open, a feature might be missing. That’s normal and fixable: tell it the exact symptom, or paste the error back.

• Want to keep going? The natural next step is publishing that page for free — it’s its own article: How to create and host a website for free.

The takeaway

One tool installed, one login, one folder, one prompt — and you’re no longer someone who “doesn’t do computers”. Everything you build from here is the same loop: describe, approve, review, refine.