EdTech Tracker

← Coding lens

long running agents

architecture judged 87% likely a named technique or architecture

First seen
2025-10-15
Independent sources
7
Articles
10
Last 4 weeks vs prior
0 vs 3

See how it has spread across media tiers

Mentions over time

Articles per week (by publish date) using the term, in any spelling.
01.532025-W412026-W252026-W40
Table view
WeekArticlesSources
2025-W4111
2026-W1131
2026-W1511
2026-W2511
2026-W3711
2026-W3922
2026-W4011

In their words

Pattern Storage Best Use Case Primary Tradeoff In-process (working only) Context window Single-session assistants, one-off tasks No persistence across sessions Flat external vector store Vector database Cross-session recall with minimal complexity Retrieval quality degrades as memory grows Tiered memory (episodic + semantic) Separate vector stores or indexes Long-running agents that learn over tim

We discuss: Why OpenAI thinks Computer Use has changed dramatically in just the last few months Dots and what changes when every agent gets its own Linux computer Why Computer Use can now complete some tasks faster than the average human The path from human-level to “literally superhuman” computer use Why modern agents are much better at debugging and recovering from failure How screenshots, acces

Lower token costs Long-running agents can accumulate a lot of information.

This is because a long-running agent often spins off other agents to do other things, reducing the surface area that you, as a human, have to manage.” “Awareness overhang” is another cause of the rapid adoption, the Codex team believes.

Durable execution : @ai-sdk/workflow introduces WorkflowAgent for long-running agents.

OpenAI updates the Agents SDK with native sandbox execution and a model-native harness, helping developers build secure, long-running agents across files and tools.

This ambiguity is a primary driver of infinite loops — the agent keeps retrying a tool that failed, mistaking silence for “no results found.” Pattern 3: Checkpoint-Based Recovery Section titled “Pattern 3: Checkpoint-Based Recovery” For long-running agents, implement checkpointing so the agent can resume from a known-good state after a failure rather than restarting from scratch.

Long-running agents hit context limits — the LLM runs out of space to reason.