Permissions and approvals
Aru can edit files, run commands, control the browser, and use connected services. When an approval request appears, review the action and target before allowing it.
Ask for approval and Full access
The permission menu in the composer controls the current task.
| Mode | Behavior |
|---|---|
| Ask for approval | Shows permission requests so you can respond to each one. |
| Full access | Automatically approves eligible requests in the current task. |
Start with Ask for approval for an unfamiliar project or external service. Permission mode is task-specific.
With Full access, file changes and commands may be approved automatically. Check the working folder and connected-service permissions first. This setting does not override operating-system permissions or organization policy.
Respond to a request card
- Review the tool and action on the Permission Required card.
- Check file paths, working directory, command, or service action.
- Select Allow Once, Always Allow when available, or Deny.
- Confirm that the task continues as expected.
Allow Once answers the current request. Before choosing Always Allow, review the permission pattern on the card; it may apply to later matching requests. Deny prevents the action, after which you can ask for another approach.
Check before execution
- File edits: Is this the intended project and file? Will it overwrite the source?
- Commands: What command and directory will be used? Could it delete, install, or deploy anything?
- External services: Is the action read-only, or will it create, change, or delete data? Which account and target are involved?
- Browser: Which site will be controlled, and what will be submitted?
Drafting an email and sending it have different effects. To review first, say: Draft the email and ask me before sending it.
After denying a request or changing permissions
Describe an alternative or narrow the scope. To stop automatic approval, switch the permission menu to Ask for approval.
Changing permissions or stopping a task does not undo completed actions. Review file changes in Review changes and inspect external-service state in that service.
Organization policy and OS permissions
App approval cannot enable models or MCP tools blocked by organization policy. Operating-system prompts—such as macOS folder, Keychain, or Accessibility access—must also be handled separately.
See Troubleshooting if an approved task does not continue.