Skip to main content

Tools, Permissions, and Sandbox

Agents use tools to inspect projects, change files, run commands, access connected services, and delegate work. Permission rules decide whether a requested operation can run immediately or must wait for your response.

One operation, one decision​

A permission request can show a command, path, URL, diff, or external resource. Before allowing it, confirm that the operation is necessary, its target is correct, and its scope is no broader than the task requires.

Reject unclear operations and explain the safer or narrower action you expect. See Questions and Permissions for the Chat procedure.

Persistent rules​

Auto-Approve can allow recurring operation types without another prompt. Persistent rules affect future matching requests, so keep write, shell, external-directory, network, and service access constrained to environments where they are expected.

Configure these rules under Settings → Auto-Approve.

Sandbox​

When available, sandboxing limits where supported execution can have an effect. Permission and sandbox controls answer different questions:

  • a permission determines whether the operation may be attempted;
  • a sandbox limits the filesystem or network boundary available to supported execution.

Sandboxing is conditional on the current platform and configuration. Do not assume that a missing Sandboxing area is an error.