---
title: "Operations that need approval"
description: "Every step asks first, and you can auto-approve low-risk actions."
lang: en
---

By default, **every action the agent takes needs your approval**, including reading a file. Control starts with you; you decide which operations can skip confirmation.

Making Bi smoother is a matter of approving specific low-risk actions, not lowering the overall security level.

## Confirmed by default

Out of the box, every step raises a confirmation prompt:

- Reading or searching files
- Creating or modifying files
- Running commands

You can approve or reject each one.

## Auto-approval

If you approve the same kind of action repeatedly and are confident it is safe, set it to auto-approve in Settings. Common choices:

- Read-only inspection, such as viewing files and listing directories
- Test or check commands

Writes and command execution carry more risk; keep them confirmed.

## Relation to intercept rules

Beyond per-action approval, Bi intercepts a set of clearly dangerous commands (deleting, pushing code, changing permissions). Those are refused outright rather than prompted. See [Dangerous command interception](/docs/advanced/intercept-rules).

## Workspace boundary

Whatever the approval settings, file operations stay inside the workspace you chose; paths outside it are refused. This is a separate layer that settings cannot relax. See [Workspace](/docs/using-bi/workspace).