File operation approval

Blaze CLI shows a confirmation prompt before changing files or making changes that affect your org. How strict that confirmation is depends on which of three modes you’re in.

The three modes

• Safe mode (default) — confirms every operation that has an effect, including file changes and terminal commands. The safest mode

• Approval mode — only confirms destructive Salesforce commands that change your org, such as deploys and deletes. Regular file operations and read-only operations proceed without a prompt

• Trust mode — auto-approves everything. Meant for CI/CD and other unattended environments

Switching modes

Press Shift + Tab in the interactive screen to cycle safe mode → approval mode → trust mode. The current mode is shown at the top of the screen.

You can also set the mode at launch:

blaze --approval-mode

blaze --trusts-everything

--approval-mode and --trusts-everything can’t be used together.

How to read a confirmation prompt

When the AI tries to make a change, you’ll see:

• What it’s about to do

• The target file, org, or metadata

• The change content

API keys, tokens, and passwords appearing in the command are masked before display.

Use the keyboard to choose:

• Allow — allow this one operation

• Always allow — allow this kind of operation without future prompts (safe mode confirmations only; destructive-command confirmations in approval mode always ask again)

• Deny — cancel this operation

When run with --json, approval requests are emitted as JSON Lines and then automatically denied, since there’s no one to answer interactively.

Recommendations

• Stick with safe mode while you’re getting used to Blaze

• Work against production orgs in safe mode or approval mode

• Switch to approval mode only for repetitive routine work, and reserve trust mode for fully unattended CI/CD runs