← All use cases

Follow a goal

Hand ZeroTwo one lasting objective for long-running work.

Reach for `/goal` when ZeroTwo should persist across several turns until a stopping condition you can verify is met.

Advanced
Long-running

Starter prompt

/goal Move this project from [legacy stack] to [target stack] and verify the result with the Playwright plugin.

Introduction

/goal <objective> keeps a Work or Code task on one durable objective across turns without steering. Run /goal alone to see the objective, status and usage, and use /goal edit <text>, /goal pause, /goal resume or /goal clear to change it. The goal is stored on the server and continues automatically after a turn ends, so it survives closing the client; a goal on a local task is picked up again only by the desktop app that started it.

A goal shows one of six states: active, paused, stalled, usage limited, limited by budget, or complete. The objective can be up to 4,000 characters. Goal mode cannot be combined with Plan mode in the same composer, and it does not change your permission preset.

Choose the right work

Pick work larger than a prompt but smaller than a backlog, with defined achievement, limits, validation and stopping point.

Set up the loop

Name one objective and stop condition, the files to read, proving commands, checkpoints and a progress log. The contract defining "done" matters most.

Let the agent work independently

Request compact status: checkpoint, verification, remainder, blockers. If the status is vague, tighten the goal. The goal completes when the agent judges the stopping condition met, and it goes to stalled if it hits a blocker it cannot resolve.

Example goals

Migrations

Move a project to a new stack while screens stay identical.

Prototype creation

Implement a PLAN.md with tests per milestone.

Prompt optimization

Iterate prompts against an eval suite until a target score or a need for policy guidance.

Related use cases