Back to blog

What breaks when your agents run for days?

Thắng Đoàn
Thắng Đoàn

Your agents no longer clock out at the end of a task. They run for hours, sometimes unsupervised for days, and the platform coordinating them was likely built for jobs that finish in minutes.

Frameworks built for minutes, not days

VentureBeat reports that most orchestration frameworks were built for agents that run for seconds or minutes. Now that agents run for hours, and in some cases days, those frameworks are starting to crack. Most orchestration frameworks were not designed for this type of continuous, stateful execution. The longer your agents run, the further you drift from your control plane's core assumptions.

  • Anthropic and OpenAI added multi-session tasks and background execution, but still assume bounded-time workflows, per

Ownership sits above the model

Infoworld notes that the orchestration layer, not the model, is what adds routing, shared state, guardrails, governance, and observability. Two standards do the wiring. MCP, or Model Context Protocol, is a way to give agents governed access to tools and data. A2A, or Agent2Agent, lets agents find and delegate work to each other. Ownership of an autonomous workflow is therefore an orchestration question. If your platform cannot hold state across days, no model upgrade will save you.

The platform market is still young

Infoworld calls AI orchestration possibly the hottest AI technology of the year, with a crowded field of commercial and open source platforms competing to be your control plane. That means the layer you would rely on to own agent behavior is itself an immature market. Autonomy claims, like those Semiengineering reports around AI agents in ASIC design workflows, assume an orchestration layer that actually holds up. Treat such claims as contingent on infrastructure you may not have yet.

What this does not solve

The sources here cover frameworks and standards, not accountability. Nothing supplied establishes who is liable when a days-long agent causes harm, or how governance maps to regulators. CNBC reports surging demand for AI-related skills in finance, but skill demand is not the same as clear ownership rules. Do not confuse a working control plane with answered accountability.

If one of your agents ran unattended for days, who in your org could explain every action it took?
Which of your current workflows quietly assume agents finish in minutes?

List your agent workflows and mark each one by its longest expected runtime.

Sources

VentureBeat: Kimi K2.6 runs agents for days

InfoWorld: Five ways to evaluate AI agent orchestration platforms

Semiengineering: AI Agent Orchestration For ASIC Autonomy

CNBC: How AI is redefining Wall Street jobs

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.