Permissions
Choose what EvoX can do on your computer and when it must ask for approval.
Permission modes
Permission modes control approval of tool and computer actions. Start with step-by-step confirmation for unfamiliar folders or tools. Review the target and effects when an approval request appears. Ordinary text replies do not need individual approval.
Message EvoX…
Confirm every step
Requests confirmation for tool and computer actions requiring approval. Existing authorization and policy are reflected in the actual approval prompt; text replies do not pause sentence by sentence.
Enable permission modes
Choose a mode using the permission control below the composer. Additional modes depend on surface settings and organization policy. The “What AI can do” rules panel is currently for preview and simulation; it does not govern actual tool approval.
Permissions
Ask before tool and computer actions requiring approval.
Automatically review routine actions and ask when risk is elevated.
Automatically reviews routine actions; safety checks can reject destructive actions.
The permission control lists modes allowed by local configuration, platform capabilities, and organization policy; disallowed modes appear disabled.
How permissions work
Two controls work together:
Access boundary：Determines which files, applications, tools, commands, and network resources EvoX may use.
Approval policy：Determines when EvoX pauses before an action or sends the request for automatic review.
Changing who reviews a request does not expand its access boundary. For example, automatic review still applies the same workspace and resource limits; requests beyond those limits are reviewed before execution.
Use the permission control below the composer for desktop tasks. See Slash commands under Features for Code mode commands. Configure Evolver CLI boundaries separately rather than applying desktop modes to it.