Review, continue, and accept work

A READY ticket is waiting for your judgment. Delegator is designed for work that a human will review. It’s up to you decide whether the work meets the ticket’s requirements.

Inspect the branch and worktree

Use your actual ticket ID in place of 42. Leave the default ID out of the command to default to the first READY ticket for the project. From the project’s primary checkout:

ticket_id=42
dg show "$ticket_id"
worktree=$(dg show "$ticket_id" --worktree-only)
branch=$(dg show "$ticket_id" --branch-only)
git -C "$worktree" status --short
git -C "$worktree" log -5 --oneline
git diff HEAD..."$branch"

Compare the diff with the ticket’s scope. Run the relevant tests and build commands in the worktree. Check any behavior a passing test suite does not cover, such as an interface or a migration.

Continue the agent session

When the agent supports terminal resume, reopen the ticket’s existing session:

dg chat "$ticket_id"

This will resume the session that the agent used to complete the work. This is where you can ask the agent for corrections without needing a new context session.

ID is optional. With no ID, it will default to the first READY ticket for the project.

It requires a recorded session, an existing worktree, and a registered resume command; it cannot attach while the ticket is RUNNING.

Review the new diff and repeat the relevant checks. You can exit the chat session after the revised work is complete.

Merge the approved result

From the primary checkout on the intended receiving branch:

git merge "$branch"
dg accept "$ticket_id"

Acceptance checks the branch has been incorporated into the project’s current HEAD and refuses to remove a dirty worktree. It then marks the ticket DONE, removes its worktree, and gives eligible queued work a chance to start.

Keep the acceptance checks

dg accept --force skips the merge and clean-worktree checks. Removing a dirty worktree can discard uncommitted changes. Resolve the reason for a refused acceptance instead of treating force as the normal next step.

Stop work you no longer need

dg cancel "$ticket_id"

Cancellation stops the running agent when necessary and closes the ticket as CANCELLED. It keeps the worktree for inspection if work has started.

Dependent tickets still need their prerequisites resolved. If you cancel a ticket that blocks others, you will need to remove the dependency for the blocked work to start.

For a failed run you want to continue, see recovery steps.

Reference: dg show, dg chat, dg finish, dg accept.