Approvals

Some actions wait for you. The agent shows a card and does nothing until you answer:

• a plan before a bigger task,
• an email, a forward or a sent draft to an address you did not type in the chat, the cc or bcc of a reply, a calendar guest, a Gmail filter that forwards or deletes mail, or a saved key sent to a website,
• a destructive change to a published project's live database,
• copying data into production, or over a database that already has rows,
• publishing to an address another of your projects is using,
• a command on a server you deployed that could destroy its data, or deleting that server,
• a new version of a tool you shared, which reaches everyone who installed it and follows its updates.

Moving onto your own Chrome has its own card, set by the chat's browser setting. See Browser.

Answering a cardCopy Anchor Link

Approve & run does that one action and Reject stops it. On a plan the buttons are Approve and Revise. The arrow next to the approve button offers two more choices: approve, and from then on allow that kind of action In this chat or In every chat. The agent then does it without asking. On the own-Chrome card, the same choices set the browser setting to Auto.

Several emails or several tool updates in one reply show as one card with Approve all and Reject all.

Changing what is allowedCopy Anchor Link

In Account Settings, the Approvals card has Allow everything without asking and a switch for each kind of action above. It also lists what you allowed in single chats, with a way to take each back. Your own Chrome is not there: it is the browser setting of each chat.

The agent panel shows, under Approvals, what is allowed in the chat you are in, with a way to take each back.

What allowing changesCopy Anchor Link

• An automation cannot answer a card. An email it sends to an address that is not in its own instructions is held back, unless sending is allowed.
• On a canvas set to Auto-pilot, a model answers a worker's cards for you, or leaves one for you when it matters. See Canvas.
• Text the agent reads, such as an email or a web page, can lead it to an action. Once that action is allowed, nothing stops to show it to you first.
• When plans are always approved, the agent is told that the approval covers building only, and that going live needs your own words.
• A command that wipes a server's disk or whole file system is never run, whatever is allowed.