Goals
A Goal turns a larger objective into durable per-conversation mission state. LlamaBoss can draft success criteria, continue across tool turns, collect evidence, and run a separate verification pass before declaring completion.
Create a Goal
Use the Goal menu or write a command such as:
Make this a goal: Audit this C++ project for critical correctness bugs, fix confirmed issues, build it, and report the verification evidence.You can also use /goal <objective>. One conversation holds one current Goal. Goal state is saved with the conversation.
Success criteria and evidence
LlamaBoss can draft a Goal contract containing:
- Success criteria
- Constraints
- Evidence checks
If contract drafting fails or is stopped, the objective can remain active with objective-only verification.
Goal controls
| Command | Action |
|---|---|
/goal status | Show objective, status, contract, continuation usage, and verifier notes. |
/goal pause | Pause automatic Goal work. |
/goal resume | Resume a paused or interrupted Goal. |
/goal continue | Continue work, including after the Goal waited for user information. |
/goal verify | Run verification now. |
/goal rebuild contract | Draft the success criteria and evidence plan again. |
/goal clear | Remove the Goal from this conversation. |
Natural-language controls such as “pause the goal,” “continue the goal,” and “verify the goal” are also recognized when sent as standalone messages.
Verification is separate from doing
The worker may believe the task is complete. The Goal verifier reviews the objective, contract, tool evidence, artifacts, and recent conversation to decide whether completion is supported. A failed verification can send the Goal back for more work instead of accepting an unsupported claim.
Verification is only as strong as the available evidence. Ask for concrete checks—build output, file existence, spreadsheet row counts, PDF field inspection, tests, hashes, or other task-appropriate proof.
Automatic continuation budget
Goals have a bounded number of automatic continuation turns. The status view shows how many were used. Reaching the budget stops automatic continuation without deleting the Goal; you can inspect the state and explicitly resume or continue.