Long-Running AI Agents: Technical Approaches, Core Bottlenecks, and Industry Impact — A Deep Dive

Self-evaluation is the core bottleneck blocking long-running AI agents — and solving it may be tantamount to achieving AGI.
A Reddit discussion on long-running AI coding agents surfaced two key findings: the orchestrator-critic loop offers a viable technical path, but relies on costly prompt engineering rather than native training; and LLM self-evaluation is the system's weakest link — AI cannot reliably judge its own output, and solving this would mean closing a self-improvement loop that essentially equates to a critical step toward AGI. The debate also highlighted the need to distinguish between AI's strength in automating execution-level deliverables and the higher-order value of strategy and client insight that remains harder to replicate.
A Reddit Community Debate About Long-Running AI Agents
Recently, a discussion on Reddit about the next generation of AI coding agents sparked widespread attention. The focus was on a compelling yet controversial idea: could AI agents run continuously for days or even weeks, self-correcting and autonomously advancing complex software projects?
The heart of the debate can be captured by one commenter's quip — "hopefully it doesn't run for 5 days, burn $50,000 in tokens, and come back with 'you're absolutely right.'" That line perfectly nails the two biggest pain points for long-running agents today: runaway costs and the reliability of self-evaluation.

This article draws on multiple perspectives from that community discussion to dig into the technical approaches, real-world limitations, and concrete industry impact of long-running AI agents.
Technical Architecture and Implementation Paths for Long-Running AI Agents
The Orchestrator-Critic Loop Pattern
One technical architecture mentioned repeatedly throughout the discussion is worth highlighting. A commenter offered what they called a "wild guess": the system might use relatively "weak or cheap" models to handle specific feature development, scale through massive agent parallelism, and deploy "critic" agents to identify areas needing improvement — keeping the entire loop running for days.
This describes an orchestrator-critic loop pattern. The community consensus was that this isn't a new concept — "you can basically do this with existing models already, it just gets expensive fast."
From Prompt Engineering to Native Training
Another participant drew an analogy to chain-of-thought (COT) prompting before reasoning models existed:
"It works, but it's not the same thing as an actual reasoning model. Right now you can have Claude act as an orchestrator and get impressive results, but if a model is specifically trained for this, I can imagine it going much further."
This analogy hits the mark. Current approaches that have Claude act as orchestrator are highly dependent on prompt quality — "it doesn't natively know how to orchestrate in an optimal way by default." If future models are trained from the ground up with agentic orchestration as an objective, their performance could improve fundamentally. In other words, the community anticipates a future where "agentic orchestration works out of the box," without complex hand-crafted prompt scaffolding.
The Biggest Bottleneck for AI Agents: Self-Evaluation Capability
The Gap Between LLMs and Humans as Judges
If long-running AI agents have one fatal weakness, it's self-evaluation. A commenter with extensive hands-on testing offered a sharp assessment:
"Based on extensive testing I've done, and a number of papers on the subject, LLMs are nowhere near as effective as humans when used as judges and validators. Honestly, that's their biggest weakness right now."
This cuts to the core. The entire logic of long-running agents is built on "self-correction" — the AI must accurately judge the quality of its own output in order to keep iterating without human intervention. The commenter went further to draw out the deeper implication:
"If they actually solve this, it's basically AGI. Because once you can correctly evaluate, you can feed the results back into yourself without any friction, with no human in the loop required at all."
This surfaces a critical logical chain: reliable self-evaluation = closed-loop self-improvement = a core step toward AGI. And this is precisely where current AI is stuck.
Specific Limitations in Perceptual Capability
That said, some people were genuinely impressed by what current models can do. One developer shared a hands-on experience: "I pulled this off tonight with a 1-shot prompt — it ran 18 agents in one go," generating a small simulated virtual community scene.
But they also pointed to a specific perceptual bottleneck:
"I genuinely think that if you could improve its ability to review the scene — beyond just screenshots — the results would be incredible. It needs to actually 'see' a video of its own work."
Current AI "perception" of its own work is often limited to static screenshots or text logs, lacking a complete understanding of dynamic, continuous scenes. This is one of the technical root causes behind its inability to effectively evaluate its own output.
The Real Industry Impact of AI: Which Jobs Are Changing?
Another thread of the discussion turned to AI's actual effects on specific professions, with notably divergent views.
Accounting vs. Advertising: Two Very Different Stories
Someone asked about the state of accounting and bookkeeping, arguing these fields "should have been among the first to be disrupted by AI." In advertising, one commenter painted an even more dramatic picture:
"A parts manufacturer used to need to go to an ad agency to build out their brand image, banner ads, and content portfolio. Now Claude Code plus an intern with a broccoli haircut can knock that out between other tasks."
The Core Divide: Execution Output vs. Core Industry Value
This claim was quickly challenged, exposing a gap in how people perceive the scope of AI's impact:
"But that's not advertising — that's graphic design / content creation, which is just a small part of the value a real agency should be providing."
This pushback is worth taking seriously. It's a reminder that AI tends to excel at visible, execution-level deliverables (like design assets), not higher-order value like strategy, insight, and client relationships. Equating "content production being automated" with "an entire industry collapsing" may be a classic cognitive bias.
Conclusion: A Grounded View of Long-Running AI Agent Prospects
Pulling together the threads of this discussion, a few clear-eyed takeaways emerge:
First, the technical architecture has a clear path but isn't mature yet. The orchestrator-critic loop provides a viable framework for long-running agents, but today it's mostly held together by prompt engineering — expensive and brittle.
Second, self-evaluation is the biggest bottleneck. This isn't just an engineering problem; it's the core challenge on the road to AGI. Until AI can reliably "act as judge" the way humans can, truly unattended long-running operation remains an aspiration.
Third, assessing industry impact requires distinguishing "execution output" from "core value." AI is rapidly displacing standardized execution work, but the moat around strategic thinking, client insight, and high-level judgment remains intact.
As one commenter put it — "sounds great in theory" — but there's still a significant distance between theory and reliable real-world deployment.
Related articles

Catalyst: A Vision for an Enzyme-Like Testing Framework for AI Agents
A developer shared Catalyst on Reddit, an Enzyme-inspired framework for AI Agents, exploring why agents need observable, testable dev tools and the design philosophy behind them.

The Real Capability of AI Coding Agents: Best Models Complete Only 35% of Feature Development Tasks
The 'Agents on Rails' benchmark finds top AI models complete only 35% of feature development tasks. What this means for coding agents and developer teams.

How to Prevent Duplicate Refunds After an AI Agent Crashes: CellaFlow's Durable Execution Approach
How can AI agents avoid duplicate refunds after a crash without deadlocking workflows? CellaFlow uses durable execution, shared work identity, leases, and fencing to solve safety and liveness in multi-agent systems.