Skip to content
OverlordThe Docs

Review deliveries

The delivery is more than a completion message. It brings together the original objective, progress history, artifacts, changed files, and the agent’s reason for meaningful changes. Review from the mission so you have that context in one place.

What to check

Section titled “What to check”
  • Does the delivery address the objective that was actually requested?
  • Did the agent record an important limitation, decision, or follow-up?
  • Do the reported file changes make sense for the task?
  • Does the rationale explain why the important changes were needed?
  • Are tests, screenshots, links, or other artifacts available when relevant?

File changes and checkpoints

Section titled “File changes and checkpoints”

When an agent edits files, Overlord stores file-level change records — a short title, summary, why the change was made, and optional diff hints — so you get more than a wall of terminal output. Those records are the durable story of the patch, separate from chat narrative, and they link back to the mission and objective that produced them.

Each delivery is anchored to a checkpoint: a snapshot of the working tree captured after meaningful edits. The checkpoint tells the review UI exactly which tree was live when the rationales were recorded, so diffs open with the right context. In the desktop app you can inspect these diffs hunk-by-hunk with the attached rationale in the Current Changes view.

Inspect a delivery from the terminal

Section titled “Inspect a delivery from the terminal”
Terminal window
ovld mission context <mission-id>
ovld mission deliveries <mission-id>
ovld mission artifacts <mission-id>
ovld mission rationales <mission-id>
ovld changes status --mission-id <mission-id>

Use ovld changes rationales --mission-id <mission-id> when you only need the recorded explanations for file changes.

Continue instead of restarting

Section titled “Continue instead of restarting”

If the delivery needs another pass, add a follow-up objective to the same mission. The next agent inherits the prior objective history, shared context, and review record. Use a new mission only when the goal itself is unrelated.

This is especially useful when one agent plans a change and another implements or reviews it.