Why bother with this at all?
You don't need to become a programmer, but understanding these tools may soon be as important as understanding spreadsheets or email.
It's not really "learning to code"
Code is the hard, technical backbone behind every app and report you use. The shift: coding agents can handle much of that code for you. You describe what you want in plain English, review what they do, and stay focused on the outcome. You're not becoming a programmer.
- Coding agents handle much of the code for you
- You just describe what you want in plain English
- You review the work before trusting it
Every knowledge worker is becoming a builder
Right now, you work inside tools someone else built for you — the report, the spreadsheet, the software. That's changing fast. Soon, building the thing you need yourself will be a normal part of the job, not a favor you ask someone technical for.
- Today: you use what other people built
- Soon: you build what you need yourself
- No more waiting on someone technical
The real risk isn't AI taking your job
The usual fear is "AI will replace me." The more realistic risk is quieter: someone who's comfortable with these tools can finish certain kinds of work dramatically faster than someone who isn't. It's not AI versus you — it's people using AI versus people who aren't.
- The real risk isn't AI replacing you
- It's that AI-users move faster on certain work
- The gap is AI-users vs. everyone else
What can these tools actually do for you?
Fair question — even if you could write code, what would you actually make? The short version: many computer-based tasks can be broken down, drafted, analyzed, automated, or improved with these tools. If it lives in files, data, or documents, it's often fair game.
- Automate the repetitive tasks you do every week
- Build a report, tracker, or small tool from scratch
- Pull answers out of files, data, and documents
"I already use ChatGPT — how is this different?"
A chatbot can answer questions. That helps, but it does not give you much of an edge when everyone can ask the same questions. The bigger shift is AI making code useful for work so small, specific, and automatic that you would never have asked a programmer to do it.
- Chatbots answer; coding agents do
- The advantage is tiny, automatic work
- Code becomes useful for everyday tasks
Okay, you're in. What do you need to know?
Less than you'd think. A few plain-English ideas and a short list of words, and the rest of this stops sounding like a foreign language. Nothing to install yet — just getting your bearings.
What people mean by "Codex" and "Claude Code"
You'll hear these two names constantly. They're the same kind of thing — "coding agents" (don't worry about that phrase yet — the next card explains it) — just made by different companies. Codex comes from OpenAI; Claude Code comes from Anthropic. Both get real work done from plain-English instructions. Which one to use is a choice for later.
- Two coding agents you talk to in plain English
- Codex is OpenAI's; Claude Code is Anthropic's
- Same core idea — picking one comes later
What's an agent, really?
Forget the jargon — an agent is just something you hire to get a job done. You describe what you need, it goes and does it, and you check the work. Compare that to a chatbot like ChatGPT, which only gives you advice: it tells you how to combine two spreadsheets, then you do every step yourself. An agent is the hire — say "combine these two and flag anything that doesn't match," and it opens the files, does the work, and hands back the finished one.
- An agent is a hire: you give it the job, it gets it done
- A chatbot gives you advice; an agent does the work
- You describe, it works, you check the result
Where do these coding agents live?
Here's the most common mix-up: people assume they're a feature tucked inside the ChatGPT or Claude app they already use. They aren't. Those are chat apps — you ask, they answer. Coding agents are their own separate tools, built to actually do the work. Think of them as programs that run on your own computer and work right on your real files.
- They're not hidden inside ChatGPT or Claude — they're their own tools
- Chat apps answer questions; these do the work
- They're programs on your computer that work on your files
What does using one actually look like?
Simpler than you'd guess. You open a window and type what you want, like texting a capable coworker. The agent lays out its plan, works while you watch, and checks with you along the way when something needs your call. When it's done, you look over the result and say "good" or "change this." That back-and-forth is the whole experience.
- You type what you want, like a text conversation
- It works while you watch, checking in when it needs you
- You review the result and ask for changes
The words you need to know
Here's the secret: these words sound way more technical than they are. Every term you'll actually run into fits in three small buckets, each explained in plain English. Skim the dictionary once and the jargon loses its power.
- The building blocks — what the tools and their parts are called
- Working words — what you'll see on screen once you start using an agent
- Buzzwords — so headlines and coworkers stop sounding impressive
So how do you actually get this on your computer?
You know the words and what these tools are. This level walks you from "where do files even live?" to installed and ready — no step skipped, no step assumed.
First: files, and where your stuff actually lives
Here's the secret about every app you use: underneath, it's all files. Photos files your pictures, Spotify files your music, Google Docs files your documents — the app just does the filing for you, behind the scenes, so you never see it. A coding agent skips that middleman and works directly on files in a folder you can see. Nothing new to learn — you're just looking in the filing cabinet yourself for the first time.
- Every app you use is quietly filing things for you
- A file is a saved thing; a folder is the drawer it lives in
- With an agent, you finally see the cabinet — one folder, yours
The IDE: one window where you see it all
Think of an IDE as a browser for your files — Google Chrome, but instead of websites it shows what's on your computer. Your files are listed down the left; click one and it opens, like a tab. Your coding agent runs right inside it, so you can watch it work on your files. Bonus: one IDE runs both Codex and Claude Code, so you flip between them in one window instead of juggling separate apps.
- A browser for your files — open them like tabs
- Runs both Codex and Claude Code — toggle, don't juggle
- VS Code is the one you'll likely use, and it's free
The terminal: the window you barely need
One more window to recognize: plain text, blinking cursor, no buttons. Your Mac calls it Terminal; Windows calls it PowerShell (or just Terminal). It's simply a place where you type instructions instead of clicking them. Here's the relief: you'll mostly work in the IDE — the terminal is something you'll see mentioned, not something you'll live in.
- Mac calls it Terminal; Windows calls it PowerShell
- It's just typing instructions instead of clicking buttons
- You'll rarely need to open it yourself
Which one should you get?
Here's the part most people miss: you may already own one. If you pay for ChatGPT, your subscription includes Codex; if you pay for Claude, it includes Claude Code — nothing new to buy. Beyond that, the honest answer is you can't pick wrong: for a beginner they're more alike than different, and the IDE lets you run both later anyway. Starting from zero? Either plan costs streaming-subscription money, not software-license money.
- Pay for ChatGPT? Codex is included. Pay for Claude? Claude Code is
- You can't pick wrong — they're more alike than different
- Starting fresh? Either one; plans cost streaming-app money
Install it, step by step
Setup follows the exact path you just learned. First, install VS Code — the free IDE. Then add your tool inside it: open the Extensions panel, search for your pick, click install, and sign in with the ChatGPT or Claude account you already have. The official guides for Claude Code in VS Code and Codex in VS Code cover every click.
- Step 1: Install VS Code — free, on Mac or Windows
- Step 2: Add the Claude Code or Codex extension inside it
- Step 3: Sign in with the account you already have — done
Let's build something — right now
Because these tools write code — and everything digital is code — you can build basically anything. But walk before you run: this level is your first project. One step per card, about twenty minutes end to end. Prefer it on a single page? Full walkthrough →
Make a folder, open it in VS Code
Go to your Desktop, right-click an empty spot, choose New Folder, and name it my-first-project. Then open VS Code and pick File → Open Folder and choose it. The window will look mostly empty — an empty folder is an empty drawer. Normal.
- Desktop → right-click → New Folder → "my-first-project"
- VS Code → File → Open Folder → pick it
- Mostly-empty window = exactly right
Give it the job
Click your agent's icon in the sidebar and paste this: "Build me a fun webpage called 'What's for Dinner?' with one big button. When I click it, pick a random dinner idea from a list of 20 and show it with a playful animation. Make it colorful. When you're finished, tell me exactly how to open it."
- Open Claude Code or Codex from the sidebar
- Paste the prompt exactly as written
- Plain English with the outcome stated: that's a prompt
Now watch it build
Send it, and watch. The agent will usually lay out a quick plan, and depending on the tool and its settings it may check with you before making changes — or it may just get to work. Both are normal. Files appear in the left sidebar as it builds; if it asks you anything along the way, read it and answer in plain English.
- It may check with you first, or just get going — both are normal
- Files appear in the sidebar as it builds
- If it asks anything, answer in plain English
Open what you made
When it finishes, it tells you how to open the page — usually just double-clicking the new file, which opens it in your browser. Click the button. Get a dinner. Click it again. And pause on this: that's not a website you visited. It's a file on your computer that exists because you described it. You just made software.
- Double-click the file it made — it opens in your browser
- It actually works — that's yours
- You described it; now it exists
Now change something
The step that matters most. Go back to the chat and ask, in plain English: "make the background dark blue," "use my actual favorite meals," "add confetti when it picks one." Watch it update, refresh the page, check your change. That loop — describe, watch, check, refine — is the entire skill. And now that you have it: the dinner picker was just training wheels. Anything you can describe, you can build.
- Ask for any change in plain English
- Refresh, check, ask again — "not quite right" is normal
- Describe → watch → check → refine: the whole skill
You made it — now see what's possible
You went from "what's a coding agent?" to building software yourself. The next step isn't another lesson — it's ideas. Browse real examples of what people do with these tools, steal the prompts, and make them yours.
Explore real use cases →