# Choosing the appropriate autonomy mode

Classify the task by reversibility, data sensitivity, external impact, and environment; then choose the lowest mode that avoids unnecessary interruptions.

![Choosing the appropriate autonomy mode 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. Classify the task by reversibility, data sensitivity, external impact, and environment.
3. Choose the lowest mode that avoids unnecessary interruptions.
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.


## 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.