Ava Studio Overview#

Ava Studio is the browser-based wallet-operations surface that backs the Telegram Guardian. It's where the heavy, security-sensitive actions — creating a smart wallet, signing a one-time delegation, raising spend caps — happen, because they need a full browser + wallet-extension context (MetaMask, Frame, Rabby) that a Telegram chat can't host.

How you reach Studio#

Most users never type the Studio URL. When the Telegram flow needs a signature — "to authorize the Liquidation Guard, sign here" — Ava sends a precise deep link that opens Studio with the right prompt pre-filled. You sign, you close the tab, you're back in chat.

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

• Returning to manage existing permissions
• Reviewing transaction history
• Power-user controls not exposed in chat

Studio is reachable from the website footer or via "Launch App" links. It is not a top-bar product alongside the Guardian — see Design_website_3.0.md §4. Studio is a deep-funnel signing surface, not a marketing entry point.

What lives in Studio#

• Smart Wallets — creating, viewing, and managing the smart-wallet account Ava operates inside.
• Permissions & Caps (Advanced) — full read/write on the on-chain policies. The chat surface gives you the safe defaults; Studio gives you the full controls.
• Workflow History — every action Ava took (and proposed but you declined), with transaction hashes.
• 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, confirming actions	One-time setup: creating a smart wallet, signing a policy
Anything reversible or read-only	Anything that needs a wallet-extension signing UI
Quick caps adjustments via chat prompt	Detailed, multi-field policy editing
Single, single-asset, single-protocol actions	Multi-permission overview

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