Choose an AI-Native Editor or Assistant
Your first decision is where the AI lives. There are roughly three categories today, and you don't have to forever.
- AI-native editors (Cursor, Windsurf): a familiar code editor with the AI deeply wired in. Best if you want to see and touch the code while the AI works alongside you.
- /CLI agents (Claude Code, Codex CLI, Gemini CLI, Aider): think of typing commands at a instead of clicking buttons — that text-only control panel is the command line, or CLI (Command-Line Interface). The AI runs as a command-line that reads files, edits them, and runs commands. Best for letting the AI work more autonomously across many files.
- IDE plugins (GitHub Copilot, Continue, JetBrains AI): an IDE (Integrated Development Environment) is the all-in-one app most programmers write code in — these are bolt-on assistance inside an editor you already love.
For shipping real software, pick one that can read your whole project, edit multiple files, and run commands (tests, builds, linters) on its own. The ability to run and check its own work is what separates a helpful assistant from an autocomplete toy. A tool that can only suggest the next line leaves you doing all the verification by hand; a tool that can run the test it just changed closes the loop itself.
Beyond that core capability, a few things are worth weighing before you settle in:
- and project awareness — can it actually load the relevant files, or does it forget the start of the conversation halfway through a task?
- Permission model — does it ask before running commands and editing files, or does it act first? Both have a place; know which mode you're in.
- Cost and limits — autonomous agents can burn through usage fast. Understand the pricing before you let one run for an hour.
Don't agonize over the choice; the skills in this book transfer between tools. Most experienced vibe coders end up keeping two installed — a fast terminal agent for bulk work and a GUI editor for review. A GUI (Graphical User Interface) is the familiar point-and-click kind of program with windows and buttons; a TUI (Text User Interface) is its text-only cousin that lives in the terminal. The chapter's closing section on TUI vs GUI returns to exactly that pairing.