LlamaBoss

Documentation

Goals

A goal is an objective LlamaBoss keeps working toward — across multiple steps, tool runs, and check-ins — and verifies against real evidence before calling it done. It is the difference between asking for something once and assigning a job.

Setting a goal

There are three equivalent ways to start one:

Once set, the status strip shows the goal and its current state, so you always know what the app is working toward in this conversation.

How a goal runs

When you set a goal, LlamaBoss turns the objective into a working contract and pursues it through the agent — reading files, running scripts, writing outputs, all under the same approval rules as any other tool use. Nothing gets extra permissions just because a goal is active.

If the goal needs something only you can answer — a missing path, a choice between two approaches — it asks, and your next plain reply is taken as the answer. The work then continues from there.

Verification

This is what makes goals different from a long prompt. As the agent works, LlamaBoss keeps a structured record of what actually happened — which tools ran, which files were created or edited, which scripts succeeded. When the work looks complete, a verification pass reviews that evidence against the objective. The model saying “done” is not enough; the evidence has to back it up.

You can force a check at any time with Verify Now in the goal menu, or by typing /goal verify.

Pause, resume, and clear

From the [ Goal ▾ ] menu — or with /goal pause, /goal resume, /goal status, and /goal clear — you can suspend a goal, pick it back up later, check its details, or drop it entirely. A paused goal keeps its progress; clearing one ends it without deleting any files the work produced.

Getting good results

← Projects & Skills FAQ →