Models & learning
Long-horizon task
A long-horizon task is a temporally extended robot task whose success depends on maintaining reliable behaviour across many actions, phases, or dependent subtasks. The term has no universal step-count threshold: it usually signals sequential dependencies, accumulating execution error, delayed outcomes, changing object state, or information that must be remembered beyond the current observation.
Also known as: long horizon task, long-horizon tasks, extended-horizon task
Updated
“Long” describes structure as well as duration
Some papers define a horizon by environment steps or elapsed time. Others use the term for tasks composed of dependent phases such as opening a drawer, retrieving an item and placing it elsewhere. A 2026 scoping review found substantial variation and treats temporally extended decision-making across dependent actions, skills or contacts as the common structure.
A task can therefore be difficult over a long horizon even when each local movement is simple. Failure in an early phase may make every later action impossible.
Execution and memory create different failures
Small pose, timing or contact errors can accumulate across repeated actions. Other tasks are partially observable: the current image may not reveal which objects were already handled or which instruction phase is active.
LongBench separates fully observable long execution from context-dependent tasks that require historical information. This distinction prevents every long-horizon failure from being attributed to missing memory when the real cause is unreliable physical execution.
Episode design changes what can be learned
CALVIN evaluates sequences of language-conditioned manipulation tasks rather than isolated single skills. Training data for such problems should preserve subtask order, intermediate object state, corrections, failures, recovery and the language or goal active at each phase.
Trimming episodes into successful short clips can remove the dependencies that define the task. Evaluation should report complete-sequence success and per-phase failure, with reset rules and maximum horizon stated explicitly.
Sources
Related terms
Data & collection
Trajectory
A trajectory is a time-ordered sequence of states or observations, actions and, where applicable, rewards generated as an agent or robot evolves. A complete episode or policy rollout often yields a trajectory, but the terms are not universally identical: trajectories may be partial, while episodes have dataset- or environment-defined boundaries.
Models & learning
Action chunking
Action chunking is a policy design in which one observation is used to predict a sequence of several future robot actions rather than a single next action. The chunk can capture short-term motion structure and reduce the effective number of sequential predictions, while its execution and replanning schedule determine how quickly the robot can react to new observations.
Models & learning
World model
A world model is a learned predictive model of how an environment changes, often conditioned on a robot’s current state and candidate actions. It may forecast pixels, latent states, rewards or other task-relevant quantities. A policy or planner can use those predictions to compare possible futures before commanding the physical robot.
Data & collection
Language annotation
A language annotation is natural-language metadata attached to a robot-data sample, segment, or episode. It may state the instruction given before execution, describe what happened afterward, name a task or subtask, identify objects, record a correction, or explain an outcome. These annotation types are not interchangeable because they contain different information and may be available at different times.
Hardware & control
Robot manipulation
Robot manipulation is a robot's controlled physical interaction with objects or its environment to change or maintain their state. It includes grasping, carrying, pushing, pulling, inserting, wiping, folding, tool use, and other tasks performed through selective contact. Manipulation can use a gripper, hand, tool, arm, or another part of the robot.