# Overview

Understand the four task autonomy modes, their approval boundaries, and the separate `/plan` command.

![Autonomy & Approvals in Foxora v5.0.3](/docs/images/v5.0.3/workspace/autonomy-picker.webp)

## Where this lives

Open the autonomy control beside the composer.

Autonomy is set per task: Ask Permissions, Accept Edits, Auto, or Bypass Permissions. It controls when Foxora pauses before file, command, and consequential actions.

> **Safety:** Autonomy does not make external actions reversible. Publishing, sending, purchasing, deleting, and production changes require deliberate review.

## Steps

1. Open the autonomy control beside the composer.
2. Understand the four task autonomy modes, their approval boundaries, and the separate `/plan` command.
3. Start with the lowest mode that permits the workflow, read each approval request, and raise autonomy only after the task and environment are understood.
4. **Confirm the result.** Confirm that safe actions proceed at the intended level and that gated actions stop with a clear approval card.

## Choose the right path

- Ask Permissions for unfamiliar or sensitive work.
- Accept Edits for supervised coding.
- Auto for trusted, bounded tasks.
- Bypass Permissions only in disposable or tightly controlled environments.

## Mode comparison

| Mode | Best for | Expected behavior |
| --- | --- | --- |
| Ask Permissions | Unfamiliar, sensitive, or high-impact work | Pauses for approval before actions that need permission. |
| Accept Edits | Supervised building and coding | Allows routine edits while retaining gates for commands and riskier actions. |
| Auto | Trusted, bounded execution | Proceeds independently within the available tools and permissions. |
| Bypass Permissions | Disposable or tightly controlled environments | Removes normal approval pauses; external effects remain real and may be irreversible. |

> **Plan is not an autonomy mode.** Use `/plan` when you want Foxora to outline and track the work before acting.


## Confirm it worked

- Confirm that safe actions proceed at the intended level and that gated actions stop with a clear approval card.
- The screen, command, file, run, or destination named in this guide reflects the expected state.