AI agents can't yet reliably run long multi-step tasks unwatched, handle situations outside their training, act inside your real tools without breaking, know when they're wrong, make high-stakes judgment calls, or work with information they weren't given. This guide maps all six limits and what to do about each.
What AI agents can't do: the short version
That's the whole list, in one pass: (1) run a long chain of steps unwatched without drifting, (2) handle a situation it hasn't seen before, (3) act reliably inside your real email, calendar, CRM, and accounts, (4) know when its own output is wrong, (5) make a high-stakes call, and (6) work with information it wasn't fed live.
Here's the framing that runs through this piece: most of these are “can't do it reliably YET,” not “can't ever.” A couple, accountability and physical-world action, aren't a software update away. This isn't an anti-agent piece. Knowing exactly where the edge sits is what makes you good at using these tools.
First, what AI agents CAN do reliably (so the boundary is fair)
Before the limits: agents are genuinely good at bounded, well-defined work, the kind with a clear start and a clear finish. Triage a queue, draft from a template, pull data and summarize it.
Agents are insanely good at tasks with clear inputs and outputs
The flip side is the whole point of this article: the fuzzier and longer the task, the faster an agent falls off. Full definition: what an AI agent actually is.
The 6 things AI agents can't do reliably (the map)
Here's the map: six categories, each with why it breaks and what to do about it.
1. Run a long, multi-step task without drifting
METR's latest benchmark (Time Horizon 1.1, Jan 29, 2026) puts even Claude Opus 4.5 at a 320-minute, 50%-success time horizon (range 170 to 729 minutes), doubling roughly every 89 to 131 days. As of that date, it's hours, not days, of unsupervised work.
Why it breaks: error compounds. Pascal Bornet, co-author of “Agentic AI,” notes that at 90% accuracy per step, ten steps in a row drops overall accuracy to roughly 35% (LinkedIn, Apr 2025). One flag on the numbers people quote here: a Reddit r/AI_Agents thread titled “why 90% of AI agents still fail” (Nov 2025) is a thread title, not a statistic. Worth knowing the difference.
At 90% accuracy per step, ten steps in a row drops overall accuracy to roughly 35%. Long unwatched chains drift because per-step error compounds.
What to do: keep tasks short and checkpointed, add a human approval step where a mistake gets expensive.
2. Handle a situation it was not trained for
Compounding error is one failure mode. Novelty is another. Agents pattern-match against what they've seen, and genuine novelty gets them improvising badly, or guessing confidently. Replicant, a contact-center AI vendor, names it directly: an agent “can't improvise in complex scenarios” the way a person can (Jun 26, 2025).
Gregory Terzian adds the build-side version: an agent's output on a complex task “is only as good as that of the human guiding them and reviewing their output,” or it becomes what he calls “slop” (Medium, Feb 8, 2026).
What to do: only hand an agent tasks that look like something in its training or your examples. Keep a human on the genuinely weird cases.
3. Act reliably inside your real tools and accounts
An agent can reason its way to the right plan and still stumble on doing it inside your real email, calendar, or CRM. Nylas, an email and calendar API vendor, is blunt: agents “can't reliably interact with the systems where people actually coordinate work” (Mar 10, 2026).
Real users describe the same gap. Across AgentsExplained's compilation of 510 Trustpilot reviews spanning 5 tools (collected Jun 2026), one n8n reviewer noted: “credential connections expire quickly, making requests start failing.” Engineer Santiago (svpino) flags a related edge: “giving agents over-privileged access to resources” (X, Oct 7, 2025).
What to do: scope permissions tightly and add a real audit step. See the real security and data risks.
4. Know when it is wrong
None of the first three problems matter as much if the agent can flag its own mistakes. It can't, not reliably. A language model has no built-in sense of “I'm not sure.” It predicts likely text and states a wrong answer as confidently as a right one. OpenAI explains why: training “rewards guessing over acknowledging uncertainty,” and “accuracy will never reach 100%... some real-world questions are inherently unanswerable” (OpenAI, “Why language models hallucinate,” Sep 5, 2025).
Honestly scoped note: in one hands-on run comparing an agent to a plain chatbot (AgentsExplained, 2026-06-24), the chatbot just answered while the agent, using live search, flagged what it couldn't verify. One run, not a study, but a real example of the gap.
What to do: never trust unverified output on anything that matters, and add a verification step. See how to keep an agent from confidently making things up.
5. Make a high-stakes judgment call
Not knowing you're wrong is one problem. Being wrong on something that costs money or worse is a bigger one. Where a wrong move is expensive or irreversible, money out the door, a legal filing, a medical call, an agent has no real stake and no domain judgment, just a plausible-sounding output. Terzian: “adding a legal plugin, just another guidance text, to an agent a lawyer does not make” (Medium, Feb 8, 2026). Craig Pearson names “tasks requiring human judgment” as a clear red flag (Apr 9, 2026).
This is the structural side of the boundary, not the moving one.
What to do: keep a human as the actual decision-maker. The agent drafts and gathers; a person signs off.
6. Work with current, real-time information it was not given
A model knows what it was trained on up to a cutoff, plus whatever you feed it live. It can't “just know” today's price or a fact from after training ended. Nylas frames it as agents struggling to “react to real-time events” (Mar 10, 2026). The same hands-on run above showed the mechanic: the chatbot's cutoff left it unable to answer a question about the last 90 days, while agent mode with live search found the current answer.
Related: memory across a long task isn't reliable either, part of why categories 1 and 6 show up together.
What to do: give the agent the fresh data explicitly. Don't assume it already knows.
| What agents can't do reliably | Why it breaks | What it means for your task |
|---|---|---|
| Run a long task unwatched | Per-step error compounds (0.9^10 is about 0.35, Bornet); METR's Jan 2026 horizon is still hours, not days, for frontier models | Keep tasks short and checkpointed; add a human approval step |
| Handle a situation it wasn't trained for | Pattern-matches on what it has seen; novelty gets improvised or guessed with confidence | Only trust it on tasks that look like its training; keep a human on the weird cases |
| Act reliably inside your real tools and accounts | Real email, calendar, CRM, and identity systems need continuity and live permissions demos don't test | Scope permissions tightly; add a real audit step |
| Know when it is wrong | Trained to predict likely text, not to check facts; training rewards guessing over saying “I don't know” | Never trust unverified output on anything that matters; add a verification step |
| Make a high-stakes judgment call | No real stake or accountability; a prompt doesn't replace domain expertise | Keep a human as the decision-maker; the agent drafts, the human decides |
| Work with current information it wasn't given | Knows its training cutoff, plus only what you feed it live; can't “just know” today's fact | Give it the fresh data explicitly; don't assume it knows |
We flag one of these limits against a real tool every few weeks; that's what lands in the newsletter, no pressure either way.
Why these limits exist (the reason under the symptom)
Two mechanics explain almost everything above. First: a language model predicts the next likely word, it doesn't “know” facts or check them. Second: reliability compounds, so many correct steps in a row stays fragile even when each step is usually right, the math behind category 1.
Adding more agents often doesn't fix this either. Researcher Ofir Press: “multi-agent systems don't solve anything that single-agent systems can't” (X, May 29, 2026).
Can't ever vs can't yet: which limits are moving
Split the six into two buckets. Moving: long-task reliability, acting inside real tools, handling novelty, and current information are all improving on a measurable schedule. METR's task-length horizon has been doubling roughly every 89 to 131 days, as of Jan 29, 2026. Re-check that number before you bet a workflow on “it can't do that”: a limit stated today is a limit stated as of today, not a permanent law.
Structural: real accountability on a high-stakes call, and physical-world action, aren't a patch away. Agents have no hands, so anything physical still needs a person, or a robot.
So which of your tasks is safe to hand an agent?
Turn the map into a rule for your own to-do list. The more long, novel, high-stakes, or unwatched a task is, the more it belongs to a human or a plain automation. The shorter and better-checked, the safer to hand over.
Three honest responses, not one default: keep a human in the loop on high-stakes work; use a plain automation instead when the path is fixed and predictable (a plain automation is more reliable); or trust the agent with a guardrail, tight scope, tight permissions.
Still deciding for one task? Whether you actually need an agent at all answers that directly. The operators who get value from agents know exactly where the edge is, and stop before it.
What AI agents can't do: FAQ
What are the limitations of AI agents?They can't reliably run long unwatched tasks, handle genuine novelty, act inside real accounts cleanly, know when their output is wrong, make high-stakes calls, or work with information they weren't given. See the map above for the mechanism and fix behind each.
When should you not use an AI agent?Skip one when stakes are high, the process is fixed and predictable (a plain automation is more reliable), or your data is weak or fragmented. Craig Pearson: gaps in your systems “will reflect” in the output (Apr 9, 2026).
What are the three things AI can't do?A popular framing (Ralph Grayden, LinkedIn, May 9, 2025): AI “can't write something and know it's wrong, but 100% right,” and “can't leap” to a genuinely new idea, mapping onto categories 4 and 2 above.
What are the 5 things AI cannot do?The viral version, empathy, presence, judgment, creativity, hope, is a humans-versus-AI framing, not a task-boundary map. It won't tell you if your Tuesday invoice task is safe to hand over; the six categories above do.
Can AI agents do coding? Yes, for bounded work: a defined function, a fix in a known codebase. They struggle on large, unguided projects without a human reviewing (Terzian, Medium, Feb 8, 2026).
What can't AI agents do, according to Reddit? Threads (r/GrowthHacking, r/AI_Agents, r/AgentsOfAI) are full of real frustration, but no structure or “so what do I do about it.” That gap is why this article exists as a map instead.
The short version (and where to go next)
Six limits: agents can't reliably run long unwatched tasks, handle genuine novelty, act inside your real tools cleanly, know when they're wrong, make high-stakes calls, or work with information they weren't given. Four are moving targets; two, accountability and physical-world action, are structural. Match your task: human, plain automation, or a guardrailed agent.
Want more? What an AI agent actually is, whether you need one, and the real security and data risks are the natural next reads, covered above.
We write about exactly this, real limits, real sources, no sales pitch, roughly once a week. That's the newsletter, if useful.