Concern 977 · Working draft · editorial review in progress
Long-horizon autonomy
Long-horizon autonomy means carrying out a lengthy chain of work with limited human help, while keeping track of the goal and earlier decisions.
Understanding the concern
Finishing one useful step is different from completing a whole project. Errors can build up, circumstances can change, and a system may need to recognize when to ask for help. Tests of longer tasks help researchers study this gap, but results depend on the task, tools and required success rate.
A relay team must complete every leg, not just run the first one quickly. METR measures task length using how long a human would need, rather than how long the AI runs. Strong results on selected software tasks do not establish reliability in every workplace. Permissions and checkpoints should reflect what a system can actually do consistently.
An example
An agent completes the first parts of a software project but fails to notice that a later decision invalidates earlier work.
Illustrative unless identified as a documented case.
Words in plain English
- AI
- Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.
Evidence and its limits
Time horizons use estimated human task duration and a specified success rate. They are not a general measure of safe, uninterrupted AI operation.
METR · living research page · Research benchmark
Task-Completion Time Horizons of Frontier AI Models ↗ (opens in a new tab)Task lengths are measured in estimated human work time at stated success rates, not uninterrupted AI running time or reliability in every field.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
A question to discuss
How long can this system work reliably on our kind of task before a person needs to check its progress?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Humility
Humility means recognizing the limits of our knowledge and being willing to learn from others. Expertise can be valuable without answering every question.
State where evidence is weak, invite criticism, and listen to people with different experience. Leave room to revise a decision when new information appears.
Ask together: What might we be missing, and who could help us see it?
Stewardship
Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.
Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.
Ask together: What are we responsible for caring for over time?
Hope
Hope means seeing worthwhile possibilities and taking steps toward them, even when the outcome is uncertain. It does not require ignoring harm or promising that everything will work out.
Name the improvement you want in people's lives, then identify one realistic action and the conditions it needs. Keep room to revise the approach when evidence changes.
Ask together: What better outcome is worth working toward, and what can we do next?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.