Autonomy Slider
Expose agent autonomy as a continuous adjustable parameter so the same codebase can span scripted assistant to fully autonomous worker without re-architecting.
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.
Solution
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.
When to use
- One agent codebase needs to serve materially different autonomy contexts.
- Operators need to dial autonomy down quickly without redeploy.
- Users should be able to opt into higher autonomy explicitly.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.