Confirmations

Not available yet

Confirmation requests are not an object of the API yet. This page describes how they will work. Today the platform draws the line with the agent token’s class: class production may only read, and a change it asks for is refused with agent-token-production-readonly until a person makes it with their own key or in the console.

Why only irreversible steps

An agent that asks before every action is an agent nobody uses. So Rytiv sorts every action into two kinds:

• Reversible: it can be undone. It runs right away.
• Irreversible: it cannot be undone. It waits for you.

What counts as irreversible

The planned list:

• deleting a production database, volume or app,
• DROP or TRUNCATE in production,
• moving a domain,
• sending mail to many real recipients,
• going over your budget.

How a confirmation works

1. Your agent asks for the step. Rytiv does not run it, it creates a confirmation request with a number, what will happen, and a preview link.
2. You open the request and confirm it with your passkey, or reject it.
3. Only then does the step run.

A confirmation can never be given with the agent’s own key. The approval comes from you, not from the conversation.