Goals & missions
Goals are persistent work items, not one-off chat replies. They have an owner agent, status, plan steps, and optional schedules.
Lifecycle
| Status | Meaning |
|---|---|
| active | Running on schedule or on demand |
| paused | Temporarily stopped |
| completed | Done |
| blocked | Waiting on you or an external dependency |
Dashboard
From Team → Goals you can create a goal, run it now, pause, or resume. Agents see active goals in system context and can attach delegations as subgoals with owners and due dates.
Link to projects
The Projects tracker catalogs repos and apps. When you ask an agent to work on a project, the project-workflow skill can propose missions (goals) and subgoals after your approval.
Conversation to mission flow
| Step | What Pasture does |
|---|---|
| Catalog check | If the project is missing, the agent asks for name, description, optional URL, and setup notes before doing work. |
| Health check | For known projects, it checks URL, description, setup notes, progress log, and linked mission. |
| 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 such as 'yes' or 'go ahead'. |
| Progress tracking | Meaningful turns are logged to Projects, Missions, and task/subgoal status as work moves. |
Scheduled and persistent work
- Goals can run on demand or on a schedule.
- Goal context can include plan steps, progress, evidence, memory anchors, and next run timestamps.
- agent-send can create assigned subgoals for linked specialist agents when a goal is active.
- Cron is used for reminders and scheduled checks; Goals represent the larger mission being advanced.