AI Coding Agents — Fundamentals¶
A practical, vendor-neutral guide to working seriously with AI coding agents — before you need a full harness around them.
Who this guide is for¶
Technical teams that are just starting to operate AI coding agents (Claude Code, Codex, Cursor, Copilot…) and want a solid mental model before they hit scaling pain. No prior experience with agents required — only with software engineering.
This space moves fast
AI coding agents evolve in weeks, not years. A feature this guide describes as "missing" in tool X may already exist by the time you read it; a vendor-specific name may have been renamed; a "Yes/No" comparison row may have flipped. Treat the comparisons as a snapshot of intent, not as an authoritative spec — and check each tool's current docs before making decisions. The mental model (context, tools, loop, verification, hooks, skills, subagents) is what stays stable; the implementations don't.
How to read it¶
The 14 chapters build progressively. If you're brand new, read in order. If you already have some experience, jump to the chapter that matches your current question.
Chapters¶
- 0. What an AI coding agent really is
- 1. Context, tools, loop — the mental model
- 2. Your first AGENTS.md
- 3. Rules and instructions: same problem, different formats
- 4. Slash commands and reusable prompts
- 5. Skills: knowledge on demand
- 6. Subagents and delegation
- 7. Deterministic guarantees: hooks, specialized agents, and external workflows
- 8. MCP and external tools
- 9. Permissions, sandbox, execution modes
- 10. Privacy and sensitive data
- 11. Memory and persistence across sessions
- 12. Anti-patterns of the first months
- 13. Signs you need a harness
What's next¶
This guide is the first volume of a trilogy. When it stops being enough — when your team starts feeling the pain of running agents at scale — the next steps are:
👉 Spec-Driven Development — how to specify intent clearly and keep that spec alive as the code evolves.
👉 Harness Engineering — building software at scale with agents — how to build the guides, sensors, loops, sandboxes, subagents, and structured context that turn an LLM into an agent a team can rely on.