SHORT ANSWER
An IDE is a fancy text editor that knows about code. You don't need one for this course. If your work IT blocks the terminal or if you strongly prefer a visual file browser, VS Code is the default pick and it's free. Otherwise, stick with the terminal. Joe's videos show the terminal-first path because that's how most people will use these tools.
What an IDE actually is
IDE stands for "integrated development environment," which is a mouthful that means nothing useful. Here's what it actually is: a program that's half text editor, half file manager. You open a folder, see the files inside it in a sidebar, click one to read or edit it, and have a built-in terminal at the bottom for running commands. That's it.
The "integrated" part is the pitch: instead of switching between Finder, a plain text editor, and a terminal, you do everything in one window. For people who work with code every day, that saves constant context switching. For people who only occasionally run a Claude Code session, it's usually overkill.
Think of it as Microsoft Word for programmers. Same basic idea — a document editor with a bunch of smart features — but tuned for code instead of prose.
The names Joe drops in the video
Joe names four IDEs as fallback options. Here's what each one is, in plain terms:
VS Code
Made by Microsoft. Free. The most widely used IDE in the world, which means it has the biggest community, the most plugins, and the most help online when something goes wrong. If you pick one IDE and stop worrying about it, pick this one.
Mike Janssen, the digital editor at Current who Joe interviews in the bonus interviews, uses VS Code with Codex. He'd never coded before, and says he didn't compare it to anything else because he didn't know anything else.
Cursor
A fork of VS Code with AI features built directly into the editor. Looks and feels like VS Code because it basically is VS Code, but the AI integration is more native. Paid subscription required for most of the good features.
Windsurf
Another AI-first IDE, made by a company called Codeium. Similar pitch to Cursor. Free tier available. Also a fork of VS Code under the hood, so if you've used VS Code you'll feel at home.
AntiGravity
Google's recent entry. Also AI-focused, also built for "the AI is another collaborator in your editor" workflow. Newer than the others, so the community and plugin set are smaller.
When you might actually want one
- ›Your work IT blocks the terminal. This is the main reason Joe mentions IDEs in the video. If you can't open Terminal on a company laptop, you can often still install VS Code and use its built-in terminal instead. Talk to your IT person first — they usually have a list of approved tools.
- ›You want to see your files as a browsable tree while Claude works. Some people find this reassuring, especially early on. You watch the file list update live as Claude writes or edits things.
- ›You're already using one for other work. If you have VS Code open for an unrelated project, it's easier to run Claude Code inside it than to switch apps.
- ›You want to watch Claude edit files in real time. One participant, Sharon, mentioned in the course forums that she likes the VS Code extension because she can see the edits Claude is making as they happen. That kind of transparency is harder to get in a plain terminal.
When you don't need one
Which is most of the time, for this course. Here's the honest version:
- ›Every command in Joe's Module 1 video works the same way in a plain terminal. There's no part of the course that requires an IDE.
- ›Installing, configuring, and learning an IDE is real work. If you're new to all of this, it adds a second unfamiliar tool on top of the one you're trying to learn.
- ›The terminal is where you'll end up anyway. Almost everything Claude Code does, it does by running commands in a terminal. Using an IDE just means running those commands in a window that has a file browser on the side.
IF YOU STILL WANT TO TRY ONE
Start with VS Code. It's free, the install is a normal Mac or Windows installer (no terminal required), and Claude Code runs inside it the same way it runs anywhere else — open the built-in terminal from the Terminal menu, type claude, and you're off.
RELATED: The plain-English CLI explainer covers what a terminal actually is. The bonus interviews include Mike Janssen on using Codex inside VS Code with no coding background.