Academy
1. Studio vs Chat: When to Delegate
Understand when to use OUPI Studio instead of the chat, and how @oupi plans, executes, verifies and delivers a mission end to end.
OUPI gives you two ways to work with the same agent, @oupi. In the chat, you converse: ask a question, iterate on a document together, get a quick answer. In Studio, you delegate: describe a project, and @oupi plans it, executes each step with the right tools (documents, data, web, integrations, sandbox), verifies the result, and delivers files — all without you steering every move. The key distinction is autonomy. Chat is collaborative and turn-by-turn. Studio is agentic: hand over a goal, and @oupi owns the process end to end. Both entry points reach the same agent, and you can even hand a task to @oupi mid-conversation in the chat. Choose Studio when you want to keep a project alive over time, run it on a schedule, or trigger it from an external event — things a chat thread simply cannot do.
How a mission works, step by step. When you type a goal into the Studio mission box, @oupi follows a structured lifecycle:
- Plan — It reads your brief and builds a step-by-step plan.
- Clarify — If something essential is missing, it pauses and asks (one question or a short series). You answer from the mission page, the "To decide" list, or a notification. Nothing proceeds until you respond.
- Execute — Steps run one by one; a live timeline shows what @oupi is doing in plain language.
- Verify — A verification pass compares the deliverable to your original goal and returns a verdict: verified, failed, or could not be verified (meaning the checker couldn't read the output — not a failure, but a prompt for you to review it yourself).
- Deliver — Files appear in the outputs panel (preview, pin, download) and in your Atelier for editing and versioning.
You can stop at any time and keep what was produced so far.
Write missions like a brief, not a recipe. State the outcome ("a two-page competitive analysis"), the audience ("for the sales team"), and the format ("PDF with charts"). Let @oupi decide the steps — it plans better from a clear destination than from a long list of instructions.
When Studio wins over chat. Use Studio instead of the chat when:
• The task has multiple steps and tools — research, data processing, document formatting, verification. Studio orchestrates all of this in one run. • You need durability — Durable tasks keep their context, files, and run history across multiple executions. A weekly report or a client dossier builds on previous runs instead of starting from scratch. • You want it to run without you — Schedules ("every Monday at 8 AM") and triggers ("when a new issue appears in my connected source") let @oupi wake up and deliver autonomously. Each trigger carries a daily credit cap so an event storm can't drain your balance. • You want a verified deliverable — Every Studio mission ends with a verification verdict, giving you a quality gate before you use the result.
Stick with the chat for quick Q&A, brainstorming, or when you want to iterate on a document together in real time.
After delivery: follow up, don't start over. Once a mission finishes, you can reply directly from the mission page — "shorten it to one page", "add the 2025 figures", "same analysis for Germany". @oupi starts a follow-up that inherits the original goal and outcome as context, so you don't lose what was already done. Deliverables land in your files and open in the Atelier, where you can edit and save new versions without overwriting previous ones. For durable tasks, each scheduled run adds to the same folder, building a living archive of your recurring work.
Open Studio and launch a quick mission: describe a one-page summary of a topic you're working on, specifying the audience and format. Watch the plan appear, follow the live timeline, then read the verification verdict before opening the deliverable in the Atelier.
Chat = converse and iterate together. Studio = delegate a goal and let @oupi plan, execute, verify, and deliver autonomously. Missions follow a clear lifecycle (plan → clarify → execute → verify → deliver) and always end with a verdict. Use durable tasks for projects that persist, schedules for recurring work, and triggers for event-driven automation. Write outcome-focused briefs, review the verification verdict, and follow up from the mission page to keep context alive.