Permissions
Choose how LegionCode handles commands and file changes, from supervised approval to full access.
Permission mode controls when a run may execute commands or write files without another prompt. Select the least-permissive mode that still lets the task finish.
Permission modes
| UI label | Behavior |
|---|---|
| Supervised | Ask before commands and file changes |
| Auto-accept edits | Automatically approve edits, ask before risky actions |
| Auto same repo | Automatically run safe actions inside the selected repo |
| Full access | Allow commands and edits without prompts |
Permission modes affect runtime policy; they do not change repository, user, or run ownership.
Decisions and audit
Permission requests and decisions are recorded with the run. This makes it clear what was requested, what was approved, and which task received the approval.
An approval should apply to the concrete action shown to the user. It should not silently become a reusable approval for unrelated commands.
Choosing a mode
Use Supervised for unfamiliar repositories, migrations, deployment work, credential-sensitive code, or any task where commands need close inspection.
Use automatic modes only when the repository is disposable or well understood and the task has a narrow boundary. Full access removes approval prompts; it does not remove the need to review the resulting diff.