Confirming Actions#

For every action you ask Ava for, the Confirm tap is the gate between a proposal and an on-chain transaction — nothing runs without it. Here's exactly what it does.

(Standing jobs you set up in Auto mode — health-factor protection, weekly pay, weekly swap, token claims — are different: they run on a schedule with no per-run prompt, inside the agent permission you signed. See Permissions & Limits.)

What "Confirm" actually does#

When Ava has a proposal ready:

1. Ava prepares the transaction and sends you a Sign on web link in Telegram. It opens a confirm card in Ava Studio (app.avaprotocol.org).
2. You tap Confirm on the card. Nothing runs without that tap.
3. What happens next depends on your mode:
   • Manual (the default): before you sign, Ava runs a best-effort decode, security screen and simulation of the transaction, so you can see what it does. Then you sign in your own wallet and pay the gas from it. Ava holds no keys to your wallet.
   • Auto (optional): the action runs under the agent permission you signed — on your own wallet after its one-time upgrade (EIP-7702: same address, same keys), or from a separate Ava smart wallet you fund.

What gets checked before sending#

• Security screen (Manual). The best-effort decode, security screen and simulation above. It can be skipped in some cases — for example, when a token approval has to come first — and it never blocks you.
• Spending limit (Auto). An Auto action must fit inside the agent permission's total spending limit per token — a running total over the permission's life, not refilled. Past it, your wallet refuses the call on-chain.
• Allowed contracts (Auto). An agent permission covers the capabilities you enable — Send tokens, Trade on Uniswap V3, Aave V3, Claim — on one chain, and lists the contracts each may call. Calls outside the permission's contracts and functions are refused on-chain by the wallet itself, not just by Ava. (The Send-tokens permission is not tied to a recipient on-chain.)
• Expiry (Auto). Every agent permission expires — after 1 day, 7 days, 30 days (the default) or a custom period. After that, the wallet refuses to use it.

In Manual mode there's no permission to check: you see and sign each transaction yourself.

After confirmation#

Once it goes through, Ava keeps watching the position and warns you if risk rises again.

You can:

• Ask Ava to redo or change something — it prepares a fresh transaction, with a fresh confirm.
• Manage Auto mode in Ava Studio, not in chat: pause a standing job on the Running page, disable an agent permission on the Wallets page (every job and action that used it stops), or undo your wallet's upgrade to stop Auto on that network. Chat can't pause jobs or revoke permissions — Ava points you to the web. See Revoking Access.

What if the transaction fails?#

• Refused or reverted. If the transaction reverts — or, in Auto mode, your wallet refuses it because it's outside the permission's contracts, past its spending limit, or after its expiry — nothing is transferred. Ask Ava to prepare it again with different parameters.
• Stuck (Manual). You signed it in your own wallet, so speeding it up or cancelling it happens there, like any other transaction you send.

What confirmation isn't#

• Not handing over keys. Confirming never involves your seed phrase, and Ava holds no keys to your wallet. In Manual mode, Confirm leads to a normal signature in your own wallet; in Auto mode, it runs one action within the agent permission you signed.
• Not "auto-approve everything in the future." Each action you ask for is its own confirm gate. The agent permission you sign in Auto mode sets the on-chain limits for every Auto action — Ava still needs your Confirm for each one you ask for. Standing jobs are the exception: once you set one up, it runs on schedule inside that permission until you pause it on the Running page or disable the permission.
• Not financial advice. Confirming is your decision. Ava can be wrong; you have the final word.