Skip to main content
A mission is a business goal plus a strictly serial chain of steps that your workspace carries out one step at a time — for example “summarize weekly sales and send the summary to my inbox”. Step 2 only starts once step 1 has succeeded, step 3 only after step 2, and so on to the end. Some steps run an agent, some wait for a person to approve, some pause or check a condition. Every run keeps a full history of what happened, what it cost, and every decision made along the way.
Missions were called Projects internally in an earlier version. You may still see a few project_* field names in exports and the API — they mean the same thing. Everywhere in the product it is a Mission.
Where: Sidebar › Missions. The badge on the entry shows how many approvals are waiting for you.

​
Mission or single agent?

Both run your agents — the difference is structure and control. A good rule of thumb: if you would describe the work as “first this, then that, but check with me before sending”, it’s a mission.

​
The Missions list

  • Lifecycle tabs: All / Active / Paused.
  • Stat cards: Total missions, Active, Needs attention, Avg success rate.
  • Filters: sort (Last active / Success rate / Avg cost / Name), operational-state toggles (Running / Waiting / Paused / Failed), and a department dropdown.
  • Toolbar: search, Group (Department / Status / No grouping), time range (All time / 7 / 30 / 90 days), view switcher (List / Compact / Board), Columns, and Export CSV.
  • An attention banner highlights missions with a pending approval or a failed last run.
  • Each row shows status, title, description, creator, step count, a success-rate sparkline, the latest run status, and live progress (“Step 2 of 5”) while a run is in flight.
If you are a Company Admin viewing a mission you don’t own or belong to, a “via admin access” badge marks that.

​
Creating a mission

Click New mission and choose:

​
Who sees a mission — membership & roles

Membership is the visibility boundary. Only the owner, the people added under Settings › Members, and Company Admins can see a mission at all. A mission’s department is a label, not an access rule.
Only owners and leads can start runs, change the flow, publish a draft, or resolve an approval. Members participate; viewers only read.

​
A map of the tabs

Every mission opens on a hero (progress ring, status, goal, creator) with these tabs:

​
Learn the mission chapter

Flow & Steps

The step editor, the seven step types, step contracts, the 20-step limit, and variables & templating.

Running & Approvals

Start a run, the one-active-run rule, the live view, pause / resume / cancel, budgets, and human approval gates.

Insights: Analytics & Economics

Success rate, per-step cost and failures, savings and ROI — and which panels are still rolling out.

Build: Passport, Genome, Manifest, Blueprint

The identity and export surfaces, plus Variables, Versions, pre-flight Test, and the auto-generated SOP.

Triggers & Drafts

Schedule and webhook triggers, the duplicate policy, and the safe draft → preview → validate → publish flow.
Driving missions from an AI client? Everything here is also operable over MCP. See the Mission Recipes for step-by-step operating flows, and the Missions API reference for the exact tools.