concept · concepts/Agent Autonomy Spectrum.md

Agent Autonomy Spectrum

status: active · created 2026-06-02 · updated 2026-11-08 · 4 sources · #agents #harnesses #autonomy #workflow #ux

The range of how hands-off you are with an agent — from turn-based "assisted AI" through semi-synchronous harness work to mega-autonomy — with NLW arguing the productive sweet spot is settling in the middle.

Harnesses

A harness is "the interface through which we interact with agents." NLW credits 2026's agent breakthrough to model advances (late 2025) + a greater focus on harnesses. The harness, more than raw model capability, determines where on the autonomy spectrum a workflow lands.

The spectrum

  • Turn-based (assisted AI) — prompt → wait → review → prompt. Too much latency; "you sit around waiting for its response."
  • Semi-synchronous (the sweet spot) — harnesses like Codex and Claude Code where you spin up and steer multiple agent threads, see their work, and interrupt anytime. Lower latency between guidance and execution. Compressed further by steering features and voice input. (The Human Sandwich lives here.)
  • Mega-autonomy — OpenClaw-style: agents on a dedicated Mac mini/studio, interfaced via Telegram, driven by "heartbeats" (recurring timed self-reminders to keep progressing toward goals). Found to "not actually accomplish the things people wanted" and to "absolutely burn tokens" (Token Shortage).

Evidence of the migration

  • Matt Schumer wiped his OpenClaw Mac mini, repurposing it as an "always-on dev box to use with Codex Mobile."
  • Nick Bauman (OpenAI) runs Codex across phone + MacBook + always-on Mac mini, starting/resuming threads from any device — "semi-synchronous," "the shape of it feels very real."
  • Jason Liu (OpenAI)'s "nine tips for getting the most out of Codex" all reduce, NLW argues, to parallel processing and semi-synchronicity rather than a turn-based paradigm (AIDB — Nine Tips for Getting the Most Out of Codex #to-read).
  • Manus — in Ethan Mollick's testing, this Claude-based agent showed "a tendency to extrapolate answers without asking," a concrete argument for keeping a human in a semi-synchronous loop rather than going fully autonomous (Making AI Work — Leadership, Lab, and Crowd).

Measured autonomy (science usage, 2026)

Anthropic — How Scientists Use Claude measures autonomy instead of arguing for it.

  • Its survey scale (none → assistive → shared → delegated → autonomous) is a finer-grained version of this spectrum.
  • In biology and biomedicine, the share of sessions run with high AI autonomy is 23.7% on Claude (chat), 64.1% on Claude Code, and over 70% on the specialized Claude Science.
  • Higher-capability subfields hand over more autonomous work (AI Use Tracks AI Capability).
  • Its acceleration scenarios find today's gains limited because use is mostly assistive or shared. Bigger multiples (8–16×) require moving toward full automation of non-physical steps (AI-Accelerated Science).

So the good setting on the dial depends on the task: verifiable, capability-rich work moves toward autonomy, and the rest stays semi-synchronous.

A multi-agent harness in practice

Anthropic — Investigating Vault Particles with Claude describes an internal multi-agent harness with access to internal compute, used to set up and run RELION (cryo-EM processing) end to end — "hundreds of GPUs in parallel." The autonomy setting is the semi-synchronous middle, stated plainly: Claude ran each step while the humans "advised on the analysis decisions." The one time it ran ahead on its own — skipping a standard processing step — it produced a map blended with its mirror image, and the correction was an explicit narrowing of autonomy: "Please let's do normal things unless they don't work." That is the Manus "extrapolate without asking" failure mode, in a lab, with a measurable cost.

The hardware footnote cuts against mega-autonomy economics from a different direction than Token Shortage: the compute-heavy step was the only part of the project a typical lab couldn't reproduce.

Connections

Sources

The wiki is the source. This door reads it at build time and never writes to it.