Skip to content
Zide Zide Zide

Safety & Permissions

The Safety & Permissions feature sets the security settings for Zide Assist. Safety & Permissions controls which tools Zide Assist has access to, how far the file tools can reach, and which actions to ask for your approval on before they run.

Safety & Permissions only sets the permissions for Zide Assist.

Navigate Safety & Permissions

Open Settings, then click Zide Assist > Safety & Permissions. Safety & Permissions has the following default presets for safety and permissions.

  • Lockdown: The Lockdown preset sets Zide Assist to always ask the user before making a change. Zide Assist does not have access to shell commands, web access, remote git commands, provider tools, or MCP tools.
  • Guarded: The default preset. The Guarded preset sets Zide Assist to always ask the user before making a change. All tools are available for Zide Assist.
  • Assisted: The Assisted preset sets Zide Assist to edit files and run local git commands without asking the user. Zide Assist will still ask before using a shell command.
  • Autonomous: The Autonomous preset sets Zide Assist to edit files and run local git and git host commands without asking the user. Zide Assist will still ask before using a shell command.
  • Danger Zone: The Danger Zone preset sets Zide Assist to edit any file and run any command without asking the user.

Each Zide Assist session is set to the default Safety & Permissions settings. Click the Safety & Permissions icon in the Zide Assist tab header to change the security settings for the session.

Changes to the security settings in a Zide Assist session take effect on the agent’s next turn, never in the middle of a turn.

Manual controls

You can manually set Zide Assist safety and permissions settings in the Advanced: Manual Controls section. You can set the Tool access setting and the Approvals setting for Zide Assist.

Tool access

Tool access controls which tools Zide Assist can use and where Zide Assist can use tools. You can set the Zide Assist access setting with the following options.

  • Locked: Zide Assist does not have access to shell commands, web access, remote git commands, provider tools, or MCP tools.
  • Project: Zide Assist has access to all tools. Zide Assist can only use file tools inside the project. Shell commands follow the Approvals setting.
  • Unlimited: Zide Assist has access to all tools and can use file tools anywhere.

Approvals

Approvals control which actions Zide Assist needs your confirmation for. You can set the Zide Assist approval setting with the following options.

  • Everything: Zide Assist will always ask for your confirmation before running a command or tool.
  • Local edits auto: Zide will not ask for your permission when editing local files. Zide Assist will ask for your confirmation for shell commands, MCP tools, git tools, and destructive operations.
  • Shell only: Zide will not ask for your permission when editing local files or running git tools. Zide Assist will ask for your confirmation for shell commands, MCP tools, and destructive operations.
  • Nothing: Zide Assist will not ask for your confirmation.

For Git tools, Zide records the repository state when it asks for your approval. If that state changes before the tool starts, Zide stops the tool. Zide Assist is told to read the current state and ask you before it tries again. See The repository changed before an action could start.

Danger Zone

When Safety & Permissions is set to Danger Zone, Zide Assist never asks for approval. Zide Assist can run any command and change or delete any file outside of the project. When you select Danger Zone, Zide notifies you about what Zide Assist does in Danger Zone. Select I have read and understand the above, and I accept full responsibility for what Zide Assist does in Danger Zone and click Enter Danger Zone.