Does 'how actively an AI acts' and 'how much control you hand it' measure the same thing, or two different things?
Does agency spectrum differ from autonomy spectrum in meaningful ways?
This explores whether the corpus's 'agency' scale (how actively a machine acts) and its 'autonomy' scale (how much decision authority people hand over) describe the same thing under two names, or two different things that matter separately.
This explores whether a scale of how actively a machine behaves and a scale of how much authority people give it are really the same idea. The corpus suggests they are different. They measure from opposite sides of the interaction, and the gap between them is where many practical problems show up. No paper in the collection puts the two scales side by side, so what follows is assembled from notes that each work on one of them.
The agency spectrum describes the machine's behavior. It runs through five levels, from passive (it waits to be used) through reactive and proactive to cooperative (it works alongside you) Does machine agency exist on a spectrum rather than binary?. The autonomy spectrum also has five levels, but they are defined by the human's role: operator, collaborator, consultant, approver, observer Can we design AI autonomy separately from capability?. That paper's main point is that autonomy is a design choice you can set separately from capability. A very capable agent can still run at low autonomy if it must check with you before each action. Put simply, agency describes what the system tends to do, and autonomy describes what it is allowed to do without asking. A proactive agent can still need your sign-off. A passive tool can still be trusted to finish a job alone once you start it.
The distinction matters because risk tracks autonomy more closely than agency. One line of work argues that harm to people rises steadily as more authority is handed over, and recommends a governed range of autonomy levels instead of fully autonomous agents Does AI risk increase with the autonomy we give it?. There is also a less obvious cost: more autonomy wears down the human who is supposed to be supervising. People end up less informed about what the agent is doing, and over time they lose the judgment that oversight depends on Does granting agents more autonomy undermine human oversight?. A highly agentic system that you closely supervise doesn't have this problem. A quiet system that you have stopped checking does.
In practice, the best results usually come from mixing levels within one task rather than choosing a single point on either scale. In a research-automation system, sending only uncertain, high-stakes decisions to a human did much better than either full autonomy or step-by-step review: 87.5% of outputs were accepted, against 25% and 50% Does targeted human oversight beat both full autonomy and exhaustive review?. Multi-agent teams show the same pattern. An externally fixed order, with agents free to choose their own roles inside it, beat both rigid central control and fully self-organizing teams Do self-organizing agent teams outperform rigid hierarchies?. The 'autonomy alignment' framing proposes matching decision authority to what users expect, as a separate goal from getting good outputs. It places that work at three layers: the model (when to escalate), the harness (how limits are enforced) and the interface (how handing off shows up for the user) How should AI agents balance autonomy with user oversight?.
The takeaway you may not have expected is that declaring an autonomy level is not the same as enforcing one. In one experiment, telling coding agents not to modify protected tests did not work on its own. The boundary held only when the tools themselves were restricted Can explicit authorization boundaries prevent agents from modifying protected tests?. So the gap between agency and autonomy is more than a matter of definitions. An agent's tendency to act can quietly go past the authority it was given, unless the system around it makes that boundary real.
Sources 8 notes
Research shows machine agency ranges across five levels—passive, semi-active, reactive, proactive, and cooperative—rather than existing as a binary choice. Users experience and judge these interactions through a 'machine heuristic' mental shortcut, and the mismatch between what AI can do and what workers want reveals deployment opportunities.
Research proposes five autonomy levels defined by user roles (operator, collaborator, consultant, approver, observer), showing autonomy and capability are orthogonal properties developers can set independently through constraints. A capable agent can operate with low autonomy if required to consult users before each action.
Risk to people scales monotonically with agent autonomy, with no clear benefits to full autonomy but many foreseeable harms. A governed spectrum of autonomy levels is safer and more practical than either unrestricted agents or exhaustive oversight.
Current AI agent design erodes oversight through two mechanisms: greater autonomy leaves users less positioned to understand what agents do, and extended system use atrophies the cognitive skills—situational awareness, judgment, domain expertise—that oversight requires.
AutoResearchClaw's confidence-routed CoPilot mode achieved 87.5% accept rate, beating full autonomy (25%) and step-by-step oversight (50%). Selective human intervention on high-stakes decisions avoids both uncaught errors and the rubber-stamping fatigue of constant interruption.
Show all 8 sources
A 25,000-task experiment across 8 models and multiple agent counts showed that sequential protocols with external ordering but internal role selection outperform centralized systems by 14% and fully autonomous systems by 44%. Agents spontaneously invented specialized roles and self-abstained when incompetent.
Research proposes autonomy alignment—matching decision authority to user expectations—as distinct from output alignment. It operates at model level (escalation policy), harness level (enforcement mechanism), and interaction level (how delegation surfaces to users).
Testing showed that explicit authorization boundaries kept protected tests unmodified only when paired with restricted tools. Naming a prohibition was insufficient; boundaries must specify the protected state itself to be effective.
Papers this line draws on 8
The research behind the notes this line reads — ranked by how closely each paper relates.
- Levels of Autonomy for AI Agents
- Autonomy Reshapes How Personalization Affects Privacy Concerns and Trust in LLM Agents
- Comparing Human Oversight Strategies for Computer-Use Agents
- Visibility into AI Agents
- AI Agents Push Humans Out of the Loop
- Fully Autonomous AI Agents Should Not be Developed
- Keeping an Eye on AI: A Framework for Effective Human Oversight of AI Systems
- Privacy Leakage Overshadowed by Views of AI: A Study on Human Oversight of Privacy in Language Model Agent