Practice · process · tools
What is agentic coding
Agentic coding is when AI agents take multi-step actions on a real codebase — reading, editing, running tools, and looping — while humans set goals and hold the verification gate.
Definition
Agentic coding means the agent does not only complete the next token in your editor. It pursues a task across steps, inspect the repo, change files, run commands, read failures, and continue until the goal or a stop condition.
Agentic coding vs autocomplete vs vibe coding
Autocomplete
Suggests the next line. You drive every keystroke of control.
Vibe coding
You state intent in natural language, agents implement. Emphasis on flow and speed of expression.
Agentic coding
Agents plan and act over multiple tool steps with limited hand-holding between actions.
Agentic software engineering
Agentic coding plus process. CI, security, ownership, roles, and durable architecture.
A default agentic workflow
-
01
Specify
Acceptance criteria and out-of-scope edges before the first edit.
-
02
Plan
A scout or planner reads the repo and proposes a bounded plan.
-
03
Implement
Builders edit in isolation (worktrees help).
-
04
Verify
Build and tests run outside the model. Failures re-enter the loop with evidence.
-
05
Review
A different model or human checks risk surfaces, auth, data, deploy.
-
06
Merge
Only after gates pass. Checkpoint everything you might need to unwind.
Deeperagentic workflow playbook, context engineering, orchestration patterns, multi-agent field guide.
Where tools fit
| Need | Often used |
|---|---|
| Single strong agent | Claude Code, Codex CLI, OpenCode |
| IDE-native loops | Cursor, Copilot agent modes |
| Local / open models | Ollama, open-weight APIs |
| Multi-agent verified crew | AI coding harness (e.g. TheVibeFather) |
FAQ
What is agentic coding?
Agentic coding is software development where AI agents plan, edit, run tools, and iterate across a repository with limited human supervision between steps — still under human goals and verification.
How is agentic coding different from vibe coding?
Vibe coding emphasizes natural-language intent and flow. Agentic coding emphasizes multi-step tool use and autonomy. Serious practice uses both, vibes for intent, agents for execution, harnesses for control.
What is agentic software engineering?
It is the broader discipline, agentic coding plus process — roles, reviews, CI, security, and ownership — so agent output becomes maintainable software.
What is an agentic workflow?
A defined loop such as plan → implement → test → review → merge, often with different models or tools on different steps and a hard stop when verification fails.
Do I need a harness for agentic coding?
For one small agent, maybe not. For multi-CLI, multi-model, long-running work with real verify gates, a harness is how you keep the system honest.
What is agentic context engineering?
It is designing what agents see and remember, files, memories, retrieval, and evolving context so self-improving loops stay useful instead of drifting.
Run it like a team
Agentic coding needs a harness when stakes rise
Coordinate Claude Code, Codex, Grok, and more with shared memory and a real verify gate.
The app behind this research
TheVibeFather is the multi-CLI AI coding harness
Run Claude Code, Codex CLI, OpenCode, Grok Build and other agents as one crew — shared project memory, roles, and a verify gate so your tests decide what ships. Bring your own keys.