Missions
Missions are persistent work items stored locally. Projects describe what exists; Missions track objectives; Tasks are the steps underneath.
Simple model
| Concept | Meaning |
|---|---|
| Project | A dashboard catalog entry for an app, repo, product, or work area. |
| Mission | A durable objective with owner, status, plan, progress, evidence, and scheduling metadata. |
| Task | A local task under a mission. Labels make it a blocker, delegation, or AI suggestion. |
Task labels
| Label | Meaning |
|---|---|
| No label | A normal task. |
| blocker | Something needs user input or an external dependency. |
| AI suggested | A proposed task discovered by an agent. |
| delegated | A task assigned to another linked agent. |
Dashboard flow
From Mission Control you choose a Project, open or create a Mission, and track all work as Tasks. Agents can run a mission now, pause it, resume it, record progress, and ask for approval before creating new mission work from a chat.
Kanban board view
Mission Control includes a board view that organizes tasks into columns:
| Column | What appears here |
|---|---|
| Needs attention | Blocked tasks waiting on user input or an unresolved external dependency. |
| Active | Tasks currently in progress or open for the assigned agent. |
| Completed | Finished tasks with their output and completion time. |
| Recent movement | Tasks that changed status recently, giving a quick pulse on what shifted. |
The board view and the task list view show the same underlying tasks. Use the board for a status overview; use the task list for filtering by label, assignee, or progress.
Deleting a mission
Missions can be deleted from the Mission Control dashboard. Deleting a mission permanently removes its tasks, progress log, and associated agent activity entries. A confirmation modal is shown before the deletion is applied. This action cannot be undone.
If you want to stop work without losing history, pause the mission instead. Paused missions remain visible, retain all task state, and can be resumed at any time.
Project workflow
| Step | What Pasture does |
|---|---|
| Catalog check | If the project is missing, Pasture asks for name, description, URL, and setup notes. |
| Plan preview | The agent proposes a mission title, objective, and task list without writing anything yet. |
| Approval gate | The mission and bulk tasks are created only after explicit approval. |
| Progress tracking | Meaningful turns update Projects, Missions, and labeled Tasks. |