after a year of shipping with AI agents, here's what they still reliably get wrong
Summary
A developer shares consistent failure modes of AI agents after a year of shipping code with them, including confidently wrong code, inability to maintain cross-file architecture, lacking pushback on bad decisions, and security edge case issues.
Similar Articles
What actually breaks when you ship AI agents for real service businesses (a year in)
A year-long reflection on the hard parts of shipping AI agents for real service businesses, highlighting that infrastructure and edge cases matter more than the AI layer.
AI agents fail in ways nobody writes about. Here's what I've actually seen.
The article highlights practical system-level failures in AI agent workflows, such as context bleed and hallucinated details, arguing that these are often infrastructure issues rather than model defects.
Something I keep seeing with AI projects that nobody talks about openly
This article highlights that many AI agent projects fail in production not because of model quality, but because teams launch without clearly defining what constitutes failure, missing critical edge cases that lead to confident incorrect outputs.
Building AI agents gets weird once real users show up
An experienced developer reflects on the gap between AI agent demos and real-world performance, highlighting issues like poor documentation, naive permission expectations, and the misconception that probabilistic software becomes deterministic in production.
I've built AI agents for dozens of clients. Here's why most of them fail in production (and it's not the model)
A developer shares three common reasons AI agents fail in production: poor RAG chunking, demo-only prompts, and lack of fallback logic, emphasizing that model quality is rarely the main issue.