Academy
4. Durable Tasks: Projects That Remember
Create and manage durable tasks that preserve context, files and run history across multiple executions, so each run builds on the previous ones.
A durable task is a persistent project folder in OUPI Studio that retains its context, files, and the full history of every run. Unlike a quick mission — which is a one-off job — a durable task is designed for work that repeats or evolves over time: a weekly report, a monthly SEO article, a client dossier. Each new execution builds on everything that came before, so @oupi never starts from scratch. It already knows the previous deliverables, the decisions you made, and the accumulated context. Schedules and triggers attach to a durable task as their destination, meaning automated runs always land in the right folder and add to the same history.
Every run inside a durable task produces deliverables that appear in the task's folder. You can preview, pin, and download them from the outputs panel on the mission page. Each 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 — the file keeps its identity across versions. This means you always have a clear trail: run 1 produced v1 of the report, run 4 refined it to v4, and every intermediate version is still accessible.
Because a durable task preserves context, it is the natural destination for automation. You can attach a schedule ("every Monday at 9 AM") or a trigger ("whenever a new email matches this rule") to it. Each automated run delivers into the same folder, can email you the files, and logs its cost and verification verdict in the task's history. If @oupi needs your input during an automated run, the mission pauses and appears in "To decide" — nothing is sent or published while it waits. You can pause, resume, or "fire now" any schedule for a live test.
When you create a durable task, write the brief as if you're onboarding a colleague who will do this job every week. State the outcome, the audience, and the format clearly. Because the context persists, @oupi will refine its approach over successive runs — but a strong initial brief sets the right trajectory from run one.
After each run, check the verification verdict (verified / failed / could not be verified) before using the result. "Could not be verified" is not a failure — it means the checker couldn't fully read the output (e.g., a binary file) and hands it to you for review. Use the follow-up feature on the mission page to correct or extend the result while keeping all context intact.
Go to Studio → Durable Tasks. Create a new durable task for a deliverable you produce regularly (e.g., a weekly status summary). Write a clear brief with the outcome, audience, and format. Run it once manually, review the deliverable and the verification verdict, then attach a schedule so it runs automatically next week.
Durable tasks are persistent project folders that keep context, files, and run history across every execution. Each run builds on the last, making them ideal for recurring deliverables. Attach schedules or triggers to automate runs; deliverables are versioned in the Atelier so nothing is lost. Always check the verification verdict before using a result, and use follow-ups to refine without losing context. A clear initial brief is the foundation for every run that follows.