Autonomy modes
The autonomy mode decides how much workers do before they ask you. Auto is the default: internal work runs at once, and outside or risky actions wait for you.
The three modesLink to The three modes
- Ask first: waits for you on anything above low risk. Reads, searches and local edits run.
- Auto (the default): reads, code edits, commits, test runs and pushes to a feature branch run at once. Medium-risk work inside the platform, such as a package install, runs, and then the worker tells you. Pull requests, tickets, comments and messages outside the platform wait for you. It also asks before merges, deploys, spend above your limit and hires.
- Full autonomy: acts without asking, except the items on your Always ask list. Your policies still apply.
What applies in every modeLink to What applies in every mode
- The Always ask list. See The Always ask list.
- Your policies. See Policies.
- Critical-risk actions stay denied unless a policy requires an approval for them. See Risk tiers.
- Budgets and the kill switch.
Where to change itLink to Where to change it
Modes and levelsLink to Modes and levels
A mode works like a level cap: Ask first is level 0, Auto is level 1 and Full autonomy is level 2. A higher level that a worker earned in evaluations stays. See Levels and evaluations.
Checked against the product on 2026-10-13.
Was this helpful?
Related articles
- The Always ask listSome actions always wait for a person, whatever the mode or risk tier. By default the list has seven items.
- Risk tiersEach action has a risk tier: none, low, medium, high or critical. The tier and your autonomy mode decide whether a worker acts, acts and tells you, asks, or is stopped.
- ApprovalsActions that need a person wait in Approvals. An approver, admin or owner approves or denies each one, with an optional comment.
- PoliciesA policy says what workers may do with a tool: allow, notify, require approval or deny. The most specific policy wins.