Running a mission

A Mission is how you hand your AI team an open-ended, goal-driven assignment. This guide walks the loop.

1. Brief the work

Dashboard → Missions → Start a mission. Describe the assignment in plain language:

"Analyze last month's campaigns and build the client story. Tell us what changed, what matters, and what to recommend. Don't send anything."

Optionally pick a starting team (a mission template) and set the autonomy level (draft-only is the safe default).

2. The team plans

The lead agent turns your brief into a task graph — 4–8 tasks, each assigned to a teammate by role. You'll see the plan on the mission page before/while the team works.

3. The team works

Each task is dispatched to its owner agent, which uses its tools (search, browse, the knowledge base, image/artifact generation) and hands results to the next task. Artifacts (reports, charts, images) appear in the Artifacts panel.

4. Review & approve

If a task would take an external action and the mission's autonomy doesn't permit it, the mission pauses as awaiting review. Hit Approve & continue to proceed, or Cancel.

5. Coach

Give 👍/👎 on the result. Feedback becomes a scoped learning (this client / this team / this agent), so the team gets better without becoming unpredictable.

6. Promote

When a mission is the kind of thing you'll run again, Promote to workflow drafts a reusable Workflow from the task graph — refine it and activate it on a schedule.

Authoring a starting team (template)

Drop a YAML file in workspace/<org>/missions/ and run npm run workspace:apply:

slug: weekly-performance-report
name: Weekly Performance Report
goal: Explain what changed, what matters, and what to recommend — produce a client-ready report.
defaultTeam:
  lead: account-strategist
  members: [paid-media-analyst, lifecycle-analyst, creative-strategist, report-writer, qa-reviewer]
autonomyPolicy:
  level: 1
successCriteria:
  - Identify the most important changes and likely causes
  - Produce a client-ready summary with cited data
desiredArtifacts:
  - Client-ready report

The team's agents must exist in your workspace (workspace/<org>/agents/). Over MCP, start a mission with mission_start.