Agentic AI — systems where language models plan, execute multi-step tasks, and use tools autonomously — is the dominant topic at every AI conference, vendor pitch, and engineering blog. The hype is intense. The production deployments are real but narrower than the hype suggests.
After two years of agent frameworks, agent benchmarks, and agent startups, a clear picture is emerging of where agents work, where they do not, and what the gap between the two looks like.
Where Agents Are Working in Production
Three categories of agentic AI have crossed the threshold from demo to production:
Code generation and modification agents. Agents that write code, run tests, fix errors, and submit pull requests are the most mature production use case. GitHub Copilot Workspace, Cursor’s agent mode, and open-source coding agents are used daily by thousands of developers. They work because the feedback loop is tight (code compiles or it does not, tests pass or they do not) and the cost of failure is low (a bad pull request is caught in review).
Customer support triage and resolution. Agents that read support tickets, retrieve relevant knowledge base articles, draft responses, and either send the response or escalate to a human are deployed at scale by multiple SaaS companies. They work because the task scope is bounded (support tickets have a known structure), the knowledge base is finite, and the human fallback is always available.
Data pipeline orchestration. Agents that monitor data pipelines, diagnose failures, apply fixes (restart a task, adjust a configuration, rerun with modified parameters), and report outcomes are operational at several large data platforms. They work because pipeline failures have a finite set of root causes and the agent’s actions are reversible.
Where Agents Are Not Working
The failures are equally instructive:
Open-ended research tasks. Agents that are asked to “research a topic and produce a report” perform poorly in production. The task scope is unbounded, the quality criteria are subjective, and the agent has no reliable way to evaluate whether its output is complete or correct. These agents produce output that looks impressive but requires heavy human editing.
Multi-system orchestration with irreversible actions. Agents that need to coordinate across multiple external systems (place orders, modify production databases, send communications) fail in production because error handling across system boundaries is brittle. When one step in a five-step process fails, the agent must either roll back the previous steps (which may not be possible) or proceed with partial completion (which creates inconsistency).
Autonomous decision-making in high-stakes domains. Agents that make decisions with significant financial, legal, or safety consequences (investment trades, medical diagnoses, legal filings) are not production-ready because the cost of a single error is too high relative to the current reliability of agent systems.
The Reliability Problem
The core limitation of production agents is reliability. A coding agent that produces correct code 85% of the time is useful because the developer reviews the output. A customer support agent that produces correct responses 85% of the time is useful because the human fallback handles the remaining 15%. An agent that makes autonomous decisions with irreversible consequences 85% of the time is dangerous because the 15% failure rate is unacceptable.
The reliability gap is not primarily a model capability problem. Current frontier models are capable enough to handle most agent tasks in theory. The reliability gap is an engineering problem: error handling, state management, tool integration, and evaluation. Building a reliable agent system requires the same engineering discipline as building a reliable distributed system, and most agent frameworks do not provide it.
What Production Teams Are Doing Differently
The teams running agents in production share three practices:
Bounded task scope. Every agent has a clearly defined set of tasks it can perform, a clearly defined set of tools it can use, and a clearly defined escalation path when it encounters something outside its scope. Unbounded agents fail. Bounded agents succeed.
Continuous evaluation. Agent outputs are evaluated against a test suite on every change — prompt changes, model upgrades, tool modifications. The evaluation suite catches regressions before they reach production. Teams without evaluation suites discover agent failures from user complaints.
Human-in-the-loop by default. Production agents start with human review of every action. As trust builds and evaluation data confirms reliability, the human review scope narrows. But the starting point is always human oversight, not autonomy.
Bounded Recommendation
If you are building agentic AI, start with a bounded task that has a tight feedback loop and a human fallback. Measure reliability quantitatively. Expand the agent’s scope only when the evaluation data supports it. The teams that succeed with agents are not the teams that build the most capable agents. They are the teams that define the most appropriate boundaries.