long-horizon-execution CAP-0029 · active

Completing tasks that take many steps or many hours

Whether an agent can carry a task through a long sequence of actions without losing the thread, compounding small errors, or stopping early; measured by how long a task, in human time or in steps, a model can finish reliably.

Tags: agentic, autonomous-agent, coding-agent

Filed from Russ's capability map (2026-09-12), with the METR time-horizon measurement as its anchor source: the length of task an agent completes at a given reliability, tracked over model generations. Several existing claims touch this (long-horizon tool calling, interactive environments, agent benchmarks) under the capability each paper exercised; this entry is for findings whose subject is horizon length itself and what limits it.

What counts as this capability

Scope boundary used when deciding whether a paper is really about this capability, rather than merely mentioning it.

In scope when the paper varies task length or step count and measures completion, or reports a time-horizon metric. NOT in scope for single-step tool use, for planning without execution, or for long-context comprehension where the input is long but the task is one step.

Claims

Techniques

  • Action guidance early, observation enrichment latetraining
    Modify the training environment's feedback rather than the agent: give explicit next-action hints in the first steps of an episode and the first half of training, then switch to richer state information in later steps and later training, ke
  • Budget reliability per step instead of reporting pass ratesprocess
    Fit a per-step reliability parameter from short-horizon runs and project it onto the target production horizon to predict success, instead of reporting aggregate benchmark pass rates.
  • Distill chunk boundaries from trajectory-induced programmatitraining
    Induce two-level programmatic skills (composite skills made of ordered subskill calls) from successful trajectories, expand each subskill call into an action chunk whose boundary becomes an off-policy supervision target, and train the primi
  • Externalize agent state onto a fact-intent DAGprocess
    Store verified environment observations as immutable fact nodes in a persistent graph and allow an action only as an intent edge whose preconditions are already-verified facts, replacing in-context state maintenance.
  • Gate between replaying retrieved winning episodes and fresh retrieval
    The agent stores successful past gameplay episodes, retrieves the few most similar to the current time and observation, and a gating rule decides whether to execute the retrieved action directly or reason anew by fusing the retrieved episod
  • Layered memory compression with four daily activity blocksprocess
    Replaces agent-managed scratchpads with a system-managed three-layer memory (full logs for recent weeks, ~200-word summaries, ~50-word milestones) and splits each simulated day into four plannable blocks.
  • Measure proactive monitoring and reflection-action gap from process
    Compute, from an agent's tool-call log, the share of non-infrastructure calls spent querying global state (PMR) and the fraction of commitments stated in its planning diary that are executed within the next K turns (RAG@K).
  • Persist a pseudo-code plan and restrict calls to itprocess
    Before any action, the agent generates an ordered pseudo-code sequence of tool calls, writes it to a scratchpad that persists across the whole episode, and the executor admits only the plan-specified tool at each step unless replanning is t
  • Replace conversation history with a rewritten execution statarchitecture
    At each step the model sees only the immutable skill spec, the current structured state and the latest observation, emits a JSON state patch plus an action, and has its reasoning trace discarded after the runtime validates and merges the pa
  • Require non-target files be byte-identical, not just task goprocess
    Score a task as successful only when all task-specific final-state evaluators pass and every pre-existing non-target file is unchanged between initial and final sandbox state.
  • Reward segments by reference reasoning points reachedtraining
    Split each sampled trajectory into segments and give each segment a reward equal to the increase in the count of reference-solution reasoning points it has reached, with credit shortcut so that reaching the goal counts all points.
  • Role-split physical agent loop with reflection feedbackprocess
    Splits long-horizon physical task management into deterministic perception agents, a synthesizing manager, a decision agent, an independent revision agent that may only adjust quantities, a deterministic safety guard, and a reflection agent
  • Roll back the environment, keep the distilled reflectionprocess
    On a triggered review, an agent restores a coarse-to-fine-selected earlier checkpoint while carrying forward a memory of objective, environment facts, past milestones and failure analysis, deliberately omitting current-state claims.
  • Route routine calls to a smaller modelprocess
    Send the short, structured, routine calls in an agent pipeline to a small cheap model and reserve a frontier model for the steps that need deep planning or sustained constraint tracking.
  • Score long-horizon agents on separate capability axes, not oprocess
    Alongside the accumulated primary score, measure negotiation surplus, fraud spend share, drawdown over peak, profit per tool call, controllable return rate, and repeat-order price discipline as separate ranked axes.
  • Stage the proof: explore, gate, decompose by dependency, re-process
    Allocates inference across explicit research stages — strategy exploration with a readiness gate, decomposition into a dependency graph of section-level subproblems solved in parallel, and global verification whose findings are routed back
  • Verify each intermediate step against domain constraints, thprocess
    After every tool call, a manager role re-reads structured global memory and classifies the output as pass/uncertain/fail on schema validity, sub-goal consistency and domain plausibility, replanning or re-routing on failure.

Sources

Every paper, post or observation behind this capability. Ones cited by a claim show the claim and its stance; ones filed directly are about the capability but have no claim drafted from them yet. Open one to add support or contest it.

Suggest a change

Capabilities are a way of carving up the subject, and carvings are arguable. Say so if this one is wrong — especially a proposed one, which a pipeline added because several papers used the same framing, not because anyone decided it was right.