Ava Studio Overview#

Ava Studio is the browser-based wallet-operations surface that backs the Telegram Guardian. It's where the security-sensitive actions — signing the transactions Ava prepares, upgrading your wallet for Auto or funding an Ava smart wallet, signing an agent permission — happen, because they need a full browser + wallet-extension context that a Telegram chat can't host.

How you reach Studio#

Most users never type the Studio URL. When Ava prepares a transaction in Telegram, it hands the signing off to the web: a Sign on web link opens Studio with the transaction on a confirm card. You tap Confirm, sign in your own wallet, and you're back in chat.

You can also open Studio directly at app.avaprotocol.org for:

• Wallets (/wallets) — the wallet Auto runs on and its agent permissions (Edit permissions); for a separate Ava smart wallet, Deposit and Withdraw too
• Running (/run) — pausing or resuming scheduled jobs, and turning Ava Guardian monitoring on or off
• Settings (/settings) — turning notification channels (Email, Discord, Telegram, Slack) on or off

Chat can't pause jobs, turn off monitoring, or revoke agent permissions — Ava points you to Studio for those.

Studio is reachable from the website footer or via "Launch App" links, and from the Sign on web links Ava sends in Telegram.

What lives in Studio#

• Smart Wallets — the separate Ava smart wallet Auto runs from: how you fund it, and how to withdraw.
• Agent Permissions — the window on the Wallets page where you see, change and turn off what Ava may do in Auto — one-off actions and standing jobs — from your Ava smart wallet.
• Workflow History — every run of your Auto jobs, with step-by-step details.
• Secrets — environment-style secrets for power users (typically not needed for the Guardian flows).

What does not live in Studio#

• Authoring "workflows" / "automations". The pre-pivot Studio was a workflow builder for power users. The new Studio is positioned as a wallet-operations console, not a no-code automation canvas. Pre-existing workflow tooling remains accessible for current users but is not the headline.
• Telegram chat. Conversation stays in Telegram.
• Anything that should be a tap in chat. If a flow is being done daily, it belongs in Telegram, not Studio.

When to use Studio vs Telegram#

Telegram (default)	Studio (when needed)
Day-to-day: scans, alerts, asking Ava for a fix	Confirming and signing the transactions Ava prepares
Anything read-only	Anything that needs a wallet-extension signing UI: upgrading your wallet, funding a smart wallet, signing an agent permission
Checking balances and active jobs (/portfolio, /status)	Changing or disabling agent permissions (Wallets)
Asking for a single action	Pausing jobs and turning monitoring on or off (Running); notification channels (Settings)

A reasonable mental model: Telegram is the cockpit; Studio is the hangar.