Approvals and sensitive actions

Some things an agent can do in another app are harmless, like reading a page or searching your mail. Others change things in the outside world, like sending an email, posting a message or merging a pull request. Claos treats those as sensitive: by default, the agent asks before it does them.

In a chat

When an agent wants to take a sensitive action, the chat pauses and shows a card with what it wants to do, such as Send email or Post to Slack, and the details it plans to use.

• Approve and the action runs once, exactly as shown.
• Deny and it doesn't run. The agent is told and carries on without it.

The card stays in the conversation, so you can come back to it after a reload.

In scheduled work and Run now

When an agent is running a task on its own, there's nobody to click Approve. So when the run reaches a sensitive action, it stops there instead of waiting, and the action is held. You'll get an Agent paused notification in your inbox. Open the run's conversation to approve or deny it.

Letting an agent act without asking

Each agent has one setting for this: Auto-approve sensitive actions. Turn it on and the agent takes sensitive actions without asking, wherever it runs: every chat with it, its rooms, and its scheduled runs.

You'll find it in two places:

• the Auto-approve button in the chat composer, and
• the Approvals section of the agent's Plugins tab.

Turn it on only for agents you trust with that work.

When to keep approvals on

• Anything that reaches customers or the public: emails, posts, replies.
• Anything that deletes, closes or merges.
• Anything with legal or money consequences.

For those, one approval click is cheaper than one mistake.

Related

• What are integrations?
• Giving an agent access to an integration
• The inbox