Commits

When and how the worker commits — task branches, what goes into a commit, and what is kept out.

With COMMIT or stronger, the worker commits only after verification passes.

The commit is made on the task branch — the prefix, the task title as a slug and the end of the task id, for example ao/validate-email-on-sign-up-3f9c1a — created from the branch the task started on. With policy NONE or workOnBranch: false no task branch is created. Every repository of a multi-repository project gets the same task branch.
It contains the task's changes only. Uncommitted work that existed before the task is never committed.
.agent-orchestration/ and agent caches (such as Aider's .aider.tags.cache.v4/) are excluded through .git/info/exclude.
Author: the worker's Git author setting, or the user's Git configuration.

The task's Git tab shows the branch, the commit and the files changed; the completion report repeats them.

Review and plan tasks

Review and plan tasks never commit: they run in a separate worktree and must not change files.

With COMMIT or stronger, the worker commits only after verification passes.

The commit is made on the task branch — the prefix, the task title as a slug and the end of the task id, for example ao/validate-email-on-sign-up-3f9c1a — created from the branch the task started on. With policy NONE or workOnBranch: false no task branch is created. Every repository of a multi-repository project gets the same task branch.
It contains the task's changes only. Uncommitted work that existed before the task is never committed.
.agent-orchestration/ and agent caches (such as Aider's .aider.tags.cache.v4/) are excluded through .git/info/exclude.
Author: the worker's Git author setting, or the user's Git configuration.

The task's Git tab shows the branch, the commit and the files changed; the completion report repeats them.

Review and plan tasks never commit: they run in a separate worktree and must not change files.