Academy
2. Launching a Quick Mission
Write an effective mission brief, follow the live timeline, interpret the verification verdict, and retrieve deliverables from the outputs panel.
A quick mission is a one-off job you delegate to @oupi. Open Studio, type your goal into the mission box, and send. Behind the scenes, @oupi reads your brief, builds a plan, executes each step using the right tools (documents, data, web search, integrations, sandbox), runs a verification pass on the result, and delivers the finished files — all without you managing the steps. The entire flow is: brief → plan → live execution → verification verdict → deliverables.
Write your brief around three anchors: the outcome (what you need), the audience (who will read or use it), and the format (document, spreadsheet, slide deck…). Add hard constraints like sources to use or things to avoid. Describe the destination, not the route — @oupi decides the steps itself. A clear, well-scoped brief produces better results and costs fewer credits.
Once you send the brief, a live timeline appears. Each step is described in plain language so you always know what @oupi is doing. If something essential is missing or ambiguous, the mission pauses and asks you — a clarification or an approval request. You can answer directly on the mission page, from the "To decide" section in the Assistant, or from the notification. Nothing is sent or published while the mission waits for you. You can also stop the mission at any time and keep whatever was produced so far.
Before delivering, @oupi runs a verification pass that reads the full deliverable and compares it to your original goal. The verdict is one of three values:
• Verified — the result matches the goal. • Failed — something is wrong; review the details. • Could not be verified — the checker could not read the output (e.g., a binary file or an external action). This is not a failure; it means you should check it yourself.
Always read the verdict on the mission page before using or sharing the result.
Deliverables appear in the outputs panel of the mission workspace. From there you can preview each file, pin the ones you want to keep handy, and download them. Every file also lands in your personal files and opens in the Atelier, where you can edit it and save a new version without losing the previous one. If you need to refine the result, reply to @oupi from the mission page — it starts a follow-up mission that inherits the full context of the original run, so you don't start from scratch.
Open Studio, type a quick mission brief (e.g., "Write a one-page executive summary of [topic] for my management team, as a document"), and send it. Watch the live timeline, read the verification verdict when it appears, then open the outputs panel to preview and download your deliverable.
To launch a quick mission: write a brief that states the outcome, audience, and format. Send it from Studio and follow the live timeline. Answer any clarification if the mission pauses. When execution finishes, read the verification verdict (verified / failed / could not be verified) before using the result. Retrieve your files from the outputs panel — preview, pin, or download — and refine them in the Atelier or via a follow-up reply if needed.