Technical
Agent Development in 2025: What Agents Can and Cannot Do Yet
Every client asks me the same question at some point: can an AI agent just build my whole product? The honest answer requires setting expectations. Agents can do more than most people think and less than the marketing suggests. Here is the state of the art at the end of 2025.
What Agents Actually Do Well
- Scaffolding: creating file structures, boilerplate classes, config files
- Pattern replication: making component B follow the same shape as component A
- Focused refactors: renaming across files, extracting methods, reorganizing imports
- Test generation: writing unit tests from existing function signatures
- Documentation: docstrings, API docs, README sections
- Multi-step workflows with clear boundaries: deploy script, migration script, seeding
In these categories agents are often faster than me and the output is usually correct on the first try.
What Agents Still Struggle With
- Cross-system debugging: why is production slow when the logs look fine
- Architectural judgment: should this be a new service or a new module
- Prioritization: which of these five features matters to revenue
- Client communication: translating technical risk into business language
- Long-horizon planning: anticipating changes six months ahead
These require context that agents do not have and probably will not have soon.
The Honest Framing for Clients
I tell clients: an agent is like hiring a very fast junior developer who never sleeps, never complains, and never asks the right strategic questions. You still need the senior engineer to decide what to build. The agent accelerates the how.
The Orchestration Gap
The gap between a demo agent and a production agent is orchestration. A demo agent builds a todo app. A production agent needs to:
- Read existing conventions
- Match existing patterns
- Produce code that passes existing tests
- Not break existing deployments
- Commit with a message my team can parse
Orchestration is the work. The agent is the tool.
What Will Change in 2026
Better long-context handling. Cheaper parallel execution. More reliable tool use. I do not expect fundamental capability leaps. I expect the current capabilities to get cheaper and more reliable. That is enough to unlock a lot of work.
What to Tell Skeptical Stakeholders
When a client or stakeholder asks whether agents can build their product: yes, partially, with human orchestration. No, not end-to-end, without human judgment. That nuanced answer builds trust better than hype does. It also sets expectations that let you actually deliver.
The Honest Capability Ceiling
Today the ceiling is somewhere around a senior junior developer with infinite patience and no business context. That is a higher ceiling than last year. It will be higher again next year. But the ceiling is real and ignoring it leads to expensive mistakes.
For agent development patterns, see the Anthropic agent documentation.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read