Skip to Content
supedocs

Confirmations

Actions that can't be undone wait for a yes. Some wait for Face ID too.

Some tools do something you can't take back: send an email or SMS, place a call, rent a number. These never run on the first call. supe answers with a preview of exactly what would happen and what it costs, and waits.

You can also make supe ask first for anything over an amount you choose, under Limits.

What the agent does

With the CLI, the call exits with code 3 and prints the preview and the command to go ahead:

  1. The agent shows you the preview and the price.
  2. Only if you agree, it runs the command supe gave it, which is the same call with --confirm <id>.
  3. If the preview includes an approve link, you approve there with your passkey (Face ID or Touch ID). The confirm command waits for it.

The confirmation is tied to that exact input. If the agent changes anything, supe refuses it (confirmation_changed) and asks again.

Face ID

Under Controls → Approve with Face ID you choose when your passkey is needed:

SettingFace ID is needed for
OffNothing. A yes in chat is enough.
PermanentAnything that can't be undone.
Everything I'm askedEvery confirmation, including your ask-me-over amount.

With Face ID on, a yes in chat isn't enough: someone with your passkey has to approve. Changing this setting, adding a passkey or removing one also needs your passkey.

Over HTTP and MCP

  • HTTP: POST /v1/run returns 409 needs_confirmation. Show error.details.will_do and error.details.price to a person; if they agree, send the same request with "confirmation": error.details.confirmation. If it needs a passkey, the retry waits for it, or returns 409 awaiting_signature to try again.
  • MCP: execute_tool returns status: "needs_confirmation" with will_do and the price. The agent asks you, then calls again with confirmation.

On this page