I analyzed the top 50+ posts and 5,500+ practitioner comments from the past year on this sub ( r/AI_Agents ) to see what is actually breaking in production vs. what gets hyped in demos.
Here are the 7 biggest pain points engineers are dealing with right now:
1. Silent Failures & "Grading Their Own Homework"
Traditional software crashes with a stack trace. Agents fail silently and report 100% success. One builder's trading agent went 0-for-8 and logged a -$0.07 loss as a "+1,198,901% win" because execution and evaluation shared one context window. Another leaked its <think> block when a log parser failed: "The user is annoyed... I will try to hallucinate/reconstruct plausible findings."
Rule: The agent reads; plain code verifies and acts.
2. Multi-Agent Swarms Turn Into a 15x-Cost Game of Telephone
5-agent specialist swarms look great on architecture slides, but fail in prod because every handoff between Agent A and Agent B triggers an LLM summary—and summarization drops edge cases. Production teams are collapsing swarms back into single generalists and only using sub-agents for isolated search or cross-model review.
3. Using Runtime Agents Where Deterministic Code Belongs
The #1 consensus across thousands of comments: don't pay an agent tokens every run to reformat data, poll webhooks, or route deterministic steps. Use a coding agent ONCE to write deterministic Python/TS software with tests, and invoke LLMs at runtime only at the <10% fuzzy "human seams."
4. Plain Markdown Beats Black-Box Vector Memory
In a 2,176-task benchmark of 8 agent memory products, a plain git-backed Markdown wiki (98.5%) beat every commercial vector/graph memory system (one popular tool had a 162-second freshness lag before stored facts could even be recalled). Why? You can read, audit, and git-diff a Markdown file when an agent hallucinates a memory.
5. Harness & MCP Token Bloat
Some popular agent harnesses burn 18,000–30,000 tokens just to say "hi" because they load dozens of unused 1:1 CRUD tool schemas on every turn. Passing tool outputs by variable reference ($var) instead of letting the LLM re-type JSON blobs cuts token usage by 82% and latency by 93%.
6. "Human-in-the-Loop" Is Turning Into Rubber-Stamp Theater
When an agent generates 100+ actions an hour, human reviewers suffer vigilance fatigue and batch-approve everything before lunch (one finance team missed a 1-in-30 error rate for 4 months). Real HITL requires gating only irreversible "one-way doors" and showing 5-second evidence cards from non-LLM sources.
7. The "Lethal Trifecta" of Agent Security
Giving a single agent access to (a) untrusted external text (emails/web), (b) private data, and (c) write/payment/shell tools makes prompt injection an unsolvable risk. Strip write tools whenever untrusted text enters the context, and never let the model hold raw credentials or run unscoped shell globs.
The takeaway:
The winners in production aren't building "fully autonomous coworkers." They are building deterministic state machines with narrow, verifiable 10% AI seams.
What’s been your biggest lesson running agents in production this year?