Find wallet signing settings
1
Open Settings
In the Aomi portal, click the gear icon in the top bar.
2
Select Account
In the Settings sidebar, click Account.
3
Find Wallet signing
Each row identifies the provider, a shortened wallet address, and its
current signing setting.
4
Expand the wallet you want to change
Match the address carefully. Your Ethereum and Solana wallets have separate
rows and separate settings.
What each control means
Enable automatic signing
This is the provider-authorization step. Clicking Enable asks Privy to add Aomi as a delegated requester. It does not immediately change every wallet to Bypass permissions. After the provider authorization succeeds, expand the specific eligible wallet and choose Bypass permissions. This two-step design lets you authorize the provider without silently changing the policy for every wallet on the account. For Para, unattended signing uses an explicitly provisioned Para agent wallet instead of the login wallet. The portal shows the provisioning action when the account has a Para login wallet but no agent wallet yet.Provider and wallet address
The row in the screenshot says Privy and shows a shortened Solana address. This tells you which provider controls the wallet interface and which wallet the setting applies to. Always match the address before changing a setting. Two Privy wallets on the same account can have different policies, and changing the Solana wallet does not change the Ethereum wallet below it.Manual
Choose Manual when you want a wallet popup for every transaction. Aomi builds and simulates, then waits for you. Rejecting the popup leaves the setting unchanged and submits nothing. This is the recommended starting point and the default for a newly linked wallet.Auto-approve
Choose Auto-approve when you want the connected wallet to sign each transaction without a separate popup. Aomi never receives the private key. This is best for repeated actions while you control the current wallet session. If the signing client is disconnected or unavailable, Aomi cannot silently replace it with another signer.Bypass permissions
Choose Bypass permissions for scheduled or background work that must continue while you are away. This option requires a separate provider authorization. In the screenshot, Bypass permissions is disabled because the one-time Privy delegation has not been completed. Click Enable, approve the Privy request, then return to this wallet row. For Para, Bypass permissions applies to the separately provisioned Para agent wallet, not the user-controlled login wallet.If you use AI coding tools, you already know this mode. It is the same idea as
Bypass permissions in Claude Code and Full access in ChatGPT’s Codex:
an explicit, clearly labeled opt-out of per-action approval that you turn on
deliberately — and can revoke. Aomi applies the same convention to wallet
signing, with one extra safeguard: every transaction is still simulated, and
policy guards still apply.
Claude Code: Bypass permissions is the deliberate no-prompt mode.
ChatGPT / Codex: Full access is the same convention.
Locked
Choose Locked to stop this wallet from signing through Aomi. The wallet stays linked to the account, but transactions cannot use it until you change the setting again. Use Locked when you want a clear stop without deleting account history or disconnecting your other wallets.Set up Bypass permissions with Privy
1
Open Settings → Account
Confirm that the eligible row is labeled Privy and matches the wallet
address you intend to use.
2
Click Enable automatic signing
Privy opens a one-time authorization request that adds Aomi as a delegated
requester for the embedded wallet.
3
Approve the Privy request
Read the provider prompt and approve it only if you want unattended signing
from this wallet.
4
Choose Bypass permissions on the wallet row
Expand the wallet, select Bypass permissions, and sign the policy change. Privy
will sign future approved transactions from this same wallet.
5
Verify the setting
The row should show Bypass permissions. If the delegation later expires or is
revoked, unattended signing stops even if the row still expresses that
preference.
Set up Bypass permissions with Para
Para separates the wallet you use to sign in from the wallet used for unattended work.1
Connect your Para account
Your Para login wallet remains the wallet you control for interactive
signing.
2
Provision the Para agent wallet
In Settings → Account, click Provision agent wallet when the action
appears. This creates a new provider-managed wallet for background signing.
3
Record and fund the new address
The agent wallet is a separate address. Send only the assets and gas it
needs for the work you intend to automate.
4
Choose Bypass permissions for the agent wallet
Expand the Para agent-wallet row, select Bypass permissions, and approve the
wallet-policy change.
5
Keep the login wallet separate
The Para login wallet remains user-controlled. Provisioning the agent wallet
does not silently arm the login wallet for unattended signing.
Change a wallet setting
Changing the selection is not an ordinary toggle. Aomi asks a wallet to sign a short-lived authorization describing the target address and new setting.- Select the new setting.
- Review the authorization in the wallet interface.
- Sign or reject it.
- Wait for the wallet row to show the committed setting.
Stop automatic signing
Choose the response that matches what you want:
Changing the wallet setting and revoking provider capability are separate
actions. Removing either one prevents Bypass permissions from signing.
Troubleshooting
Signing
See what the user experiences after choosing each setting.
Permission model
Understand why the wallet setting and provider capability are separate.