Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-03

Actions: the agent proposes, you authorize

No agent action happens on its own: it proposes it on a card, you authorize with one click, and the AI → Approvals queue gathers everything waiting for a decision.

On this page (6)

No action happens because the agent wrote that it was going to do it. It proposes, a card appears in the conversation, and only your click executes it.

What it looks like in practice#

You: did the ERP pipeline fail? If so, reprocess it. Agent: the last ERP run failed at 2:20 PM on tb_erp_pedidos. [card] Reprocess ERP (PostgreSQL) — Authorize · Reject

Until you click, nothing has happened. If it writes "I've already reprocessed it," that's just text — the real run only exists after the click.

Saying "go ahead" in the conversation does not count as authorization. Authorization is the click on the card.

Why it works this way#

A language model writes convincing sentences, including "the user authorized it." A sentence is not a permission. The click is an application event, tied to your session, and it is recorded with your name.

Where to decide everything at once: AI → Approvals#

The conversation shows the card to whoever is chatting at that moment. But an agent that runs on its own (scheduled) also proposes actions — and those sit waiting with no one at the screen. The queue of all requests, from all agents, is in AI → Approvals.

What the screen shows, one row per request:

  • the name of the agent that asked (clicking it takes you to its Activity)
  • how long it has been waiting, and when it stops being valid (expires in)
  • the entire request: the title, What will happen, and Impact
  • the Authorize and run and Cancel buttons, and the Why do I need to authorize? link

At the top, the Runs dashboard button takes you to the Agents dashboard, which shows volume, cost, and failures. The reverse path also exists: in the dashboard's Awaiting authorization section, the Decide now button brings you here.

When you decide, the row leaves the queue and becomes the result — no need to reload the page. And the Agents list warns you, above the cards, when an action is waiting.

If a request shows up without the buttons

You are seeing a request that you can't authorize — the screen states the reason in place of the button. It stays on the list on purpose: that way you know it exists and can let whoever decides know. A gray button with no explanation would make you hunt for a bug in the system.

Who can authorize#

Whoever has permission for that specific action — being able to chat with the agent is not enough. Authorizing a reprocess requires the same permission as reprocessing from the menu.

And no one authorizes their own proposal when the action is high-risk: it requires another person.

The request expires#

An old card stops being valid. A request from yesterday, authorized today, would act on a situation that has already changed.

Where to see what happened#

In Activity, inside the agent: every run, with the steps, what was proposed, who authorized it, and the result.

Related links