Approvals

A bot can act, so it asks first. When it reaches a step that changes something in a connected app or could damage its computer, it parks the action and shows an approval widget in the conversation. The widget names the tool and what it is about to do.

The three choices

Choice	What happens
Allow	Runs the parked action, this once
Deny	Does not run it. The bot continues without that step and can propose something else.
Always	Runs it, and remembers the choice for the next time this same kind of step appears

Always is scoped to that kind of step — not a blanket for every tool the bot has. Confirming runs the parked action; it is not a preview.

What parks

Category	Examples
Connected-app changes	Creating or editing records, sending messages, anything that writes through a plugin
Dangerous computer steps	Deleting files, installing software, commands with broad effect

Reading, browsing, and taking screenshots do not park; they are how the bot works.

Read before you choose

Read the tool name and the description

The widget says which tool wants to run and what it will do.

Look at the Computer rail if it helps

The live desktop shows the state the bot is in. See Computer.

Choose

Allow, Deny, or Always. The bot waits; a parked step never times out into a silent yes.

Approvals elsewhere

Surface	Control
Code	Modes — Ask and Plan withhold mutating tools entirely. See Ask, Plan, Agent
CLI	Numbered prompts before consequential commands, plus `/permissions` and a sandbox policy. See Modes and permissions

Tools — what can be parked.
How Bot works — approvals as user-visible rows.

⌘I

Getting started

Core guides

Desktop

Advanced

The three choices

What parks

Read before you choose

Approvals elsewhere

​The three choices

​What parks

​Read before you choose

​Approvals elsewhere

​Related

The three choices

What parks

Read before you choose

Approvals elsewhere

Related