What bounds what Ava can do — the Ava smart wallet Auto runs from, the agent permission you sign for it, and how to see and change it.
Ava can act in two ways, and each has its own boundary:
The rest of this page is about Auto, because that's where Ava acts without a signature each time.
Auto runs from an Ava smart wallet — a separate smart account that your main wallet owns. You fund it with only what you want Ava to use (Deposit on the Wallets page in Ava Studio) and Withdraw what's in it back to your main wallet anytime. Anything Auto has put into a protocol, such as Aave collateral, has to come out of that position first, and collateral backing a loan needs the loan repaid. Your main wallet is never upgraded or delegated, and Ava can't touch what stays in it.
Running Auto directly on your existing wallet isn't available yet. See Smart Wallets.
The standard permission. When an Auto action needs a permission, Ava offers the standard one: a single signature per smart wallet and chain. It lets Ava approve, send and revoke the main tokens on that chain (USDC, USDT, DAI, WETH, WBTC, LINK and UNI where available), wrap and unwrap ETH, swap on Uniswap V3 and use the Aave V3 pool from the smart wallet, with no spending limit, for 365 days.
Narrower permissions. If you'd rather set limits, turn off the standard permission on the Wallets page and choose permissions one by one: Send ERC-20 tokens, Uniswap V3 swaps and Aave V3. Each one has:
Either way, a permission is for one chain, and the smart wallet enforces it on-chain: a call to a contract it doesn't cover, spending past a limit it sets, or any use after it expires is refused by the chain, not just by Ava. Ava's job runner also refuses to run a job without a valid permission.
Signing a permission is a signature, not a transaction, so it costs no gas. Ava can't create or widen a permission itself — only your signature can.
That includes one-off actions you ask for in chat (you still tap Confirm) and standing jobs that run on a schedule without asking each time:
Revoke the permission and Ava stops using it for every job and action that relied on it.
A permission is scoped to an app, not to individual functions, and a job's amount isn't an on-chain limit:
The bound that always holds is the smart wallet's balance: Auto can only use what you put in it. Spending limits, where you set them, cap what Ava is authorized to spend. Neither caps losses on your DeFi positions, which carry market risk of their own.
In Ava Studio, open Wallets, pick your Ava smart wallet, and choose Edit permissions. The Agent permissions window shows the standard permission (what it covers and when it ends) or, for narrower permissions:
Each change is a new signature from your main wallet. Studio combines the permissions you enable on a wallet and network into one shared permission. Raising a limit, adding a capability or extending the expiry all mean signing again. To switch from the standard permission to narrower ones, turn the standard permission off first.
See Revoking Access for the step-by-step.