VIII · Safety & ControlEmerging★

Autonomy Slider

also known as Autonomy Dial, Continuous Autonomy Control

Expose agent autonomy as a continuous adjustable parameter so the same codebase can span scripted assistant to fully autonomous worker without re-architecting.

Context

A product team owns one agent codebase but several deployment contexts: a free tier that should not act unsupervised, a paid tier where the user has opted into automation, an internal beta where engineers want full autonomy to stress-test. Hard-coding the autonomy level per build forks the codebase or branches the prompt.

Problem

Binary 'workflow vs agent' framings collapse the design space to two points. Most real deployments want a position between — autonomous on some axes (information gathering), supervised on others (irreversible action). Without a control surface for autonomy, each new context forces an ad-hoc fork in code or in prompt, and the team loses the ability to dial the same agent across users, contexts, or risk profiles.

Forces

  • Different users and contexts justify different default autonomy.
  • Autonomy is multidimensional — read vs write, internal vs external, reversible vs not.
  • The control must be runtime-mutable so it can dial without redeploy.
  • Operators need to inspect and audit the current setting.

Example

A coding-assistant product ships with an autonomy slider: at 0, the agent only suggests; at 1, it edits files; at 2, it runs tests; at 3, it commits and pushes. New users default to 1; power users opt into 3 per repository. A bug-bash mode drops the entire fleet to 1 within a release while the team investigates a regression.

Diagram

Solution

Therefore:

Define an autonomy parameter (scalar or vector) the runtime consults before each action. At one end the agent only emits suggestions a human acts on; at the other it acts directly and reports. Intermediate values gate by action type, confidence, or user opt-in. Persist the setting per-tenant or per-user. Surface the current value in the UI so users and operators see at a glance how autonomous the agent currently is.

What this pattern forbids. The agent must not act at an autonomy level the runtime parameter does not currently authorise; autonomy is decided by the parameter, not by the agent's own reasoning.

And the patterns that stand alongside it, or against it —

  • alternative-to[crawl-walk-run-automation-gating]
  • complementsCost-Aware Action Delegation★— Classify every agent action by risk/cost and route each tier to a different approval policy, bounding the autonomy surface per-action instead of by one global flag.
  • complementsProgressive Delegation★— Stage the human-to-agent handoff over time: the agent starts producing drafts a human always reviews; its autonomy expands action-by-action as measured trust accrues.
  • complementsApproval Queue★★— Queue agent-proposed actions for asynchronous human review while the agent continues other work.
  • complementsHuman-in-the-Loop★★— Require explicit human approval at defined points before the agent performs an action.
  • complementsKill Switch★— Provide an out-of-band control plane to halt running agent instances without redeploy.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

Used in recipes

References

Provenance