Permissions and approvals

Control which files, tools and actions a chat can use.

Applies to Bridge rc.32

Start with a boundary

Open the intended project and review the chat’s permission mode before asking Bridge to work. A model selection does not grant access to every folder, shell command, browser or application.

Read an action before approving it

Check the exact files, command, destination and effect in an approval request. A question asking you to choose an option is not necessarily authorization for a separate action. Managed policy and sandbox restrictions can still block an operation.

Review changes and output

Inspect file changes and run appropriate checks before committing, publishing or sending anything. Tool availability is not proof an operation succeeded. Read the returned result and resolve an uncertain outcome before retrying a change.

Computer use is separate

Application observation and actions have their own scope and exclusions. A paired phone or a connected browser does not bypass those gates. Do not grant broad access just to hide a configuration error.