Set the autonomy level

The autonomy slider controls how independently SupaCloud’s delivery engine picks up work, asks you questions, and merges results. You set it on three scopes — workspace, project, and agent profile — and a task takes the first level explicitly set, walking agent profile → project → workspace. If you only need the concepts, read Autonomy and the delivery engine first.

Note

The workspace slider is admin-only — the card is hidden for members and viewers. Project and profile autonomy fields appear wherever you can already edit that project or profile.

Set the workspace autonomy level

The workspace is the root of the chain — every project and profile inherits this level unless it overrides it.

1. Open Settings → Workspace.
2. Find the Autonomy card.
3. Drag the slider to one of the five stops: Manual, Assisted, Supervised, Autonomous, or Unleashed. The active stop name and a one-line description update as you move.
4. The change saves automatically — there is no separate save button. The resolved-policy preview refreshes to show what the engine will now do.

Stops above your plan are out of reach

The slider physically cannot select a stop above your plan ceiling, and it is clamped to the onboarding cap (level 25) while the workspace is still onboarding. If a ceiling is biting, the line under the slider says so — see Read the resolved-policy preview.

Set autonomy for a project or agent profile

A narrower scope can override the level it would otherwise inherit.

Project

1. Open the project and go to its Automation settings.
2. In the Autonomy field, move the slider to set a project-specific level.
3. The field shows where the value comes from — Inherits from workspace = N while unset, or Set here: N once you move it.
4. To go back to inheriting the workspace level, use Reset to inherit.

Agent profile

1. Open Settings → Profiles and select the profile.
2. On the Form tab, find the Autonomy slider.
3. Move it to set a profile-specific level. The profile is the most specific scope, so its level wins for any task that uses this profile.
4. Use Reset to inherit to fall back to the project or workspace level.

Reset to inherit

The Reset to inherit link only appears on a scope that has a parent (project and profile sliders) and only when that scope currently has its own value. Resetting clears the scope’s level so it inherits again — it does not change any parent scope.

Read the resolved-policy preview

Every slider shows a live preview of the resolved effective policy — what the engine will actually do after inheritance and the ceilings are applied. It has four chips:

Chip	What it shows
Dispatch	On (the engine may pick up work) or Manual only
Asks	Every flagged tool, Risky tools only, or Never
Effort	Economical, Balanced, or Generous — preview only; not yet consumed by the router (routing effort is currently derived from item severity)
Merge	Pull request only, Auto-merge on green, or Full auto-merge

Below the chips, an inheritance line tells you the full story:

• Inherits from {scope} = {level} — this scope is unset and takes its value from a parent, or Set here: {level} — this scope has its own value.
• Capped by plan: {level} or Capped during onboarding: {level} — shown only when a ceiling actually lowers the value.
• Effective: {level} — the final level the engine acts at, after the chain and both ceilings.

Tip

If the Effective level is lower than the stop you selected, a ceiling is clamping it. Raise your plan to lift the plan ceiling, or finish onboarding the workspace to lift the onboarding cap — the slider value itself is already set.

Use Advanced overrides

For control between the named stops, expand the Advanced overrides panel under any slider.

1. Click Advanced overrides to expand the panel.
2. In Level override, type an exact level from 0 to 100. This explicit value wins over the slider’s snap point.
3. Leave the box empty (or clear it) to go back to using the slider value.

Caution

A level override is still clamped by the plan ceiling and the onboarding cap — it can refine within your entitlement but can never push the effective level above it. The merge behaviour likewise stays a ceiling: an override can only restrict a project’s own merge policy, never escalate it.

See also

• Autonomy and the delivery engine
• Entitlements and the MCP tool tiers
• Runs and tasks