Git & pull requests.

Every agent works on its own branch, commits in small steps, and opens a pull request for review. This page covers the branching model, how to inspect the diff, and how to merge or send it back.

Branch per task

When you start a task, Agent Manager cuts a branch from your project's default branch and points the agent at it. The branch name follows the pattern below — the slug is derived from the task title.

am/<task-id-short>-<slug>

For example, a task with id abc123 and title "Add login" lands on am/abc123-add-login. The branch name shows up on the task card and the task detail so you can check it out locally if you want to poke around.

What the engine does for you

• Start — create the branch from main (or your project's default branch).
• Complete — commit the agent's changes with the message am: <task title>.
• Block — commit any partial changes as a WIP so nothing the agent produced is lost.
• Merge — merge the branch into the default branch, then delete it.

Works against any local git repo

Git automation runs against whatever local repository the project is pointed at. Add a project with the path to your existing repo and Agent Manager handles branching and commits there — no remote configuration, no extra tooling. If the directory isn't a git repo yet, the engine inits one for you.

No CI pipeline needed

Agent Manager is the review surface. You read the diff in the UI, leave comments, and merge from the same screen. There's nothing to wire up — no GitHub Actions, no webhooks, no build server.

If you do want CI in front of merges, run it against your repo the way you normally would. Agent Manager doesn't intercept your pipeline or change how remote refs behave.

Reviewing the diff

Once the agent completes, the card parks in In Review with the diff one click away. View Diff opens a side-by-side viewer with the changed files, collapsible sections, line numbers, syntax highlighting, and a copy button per file.

Merging from the UI

When the diff looks right, click Merge & Close. The branch merges into the project's default branch and is deleted. The card moves to Done, and the task lands in whatever logs or history your repo keeps.

Sending it back

If something needs another pass, leave a comment on the task with what to change. The agent resumes from the same branch. To start fresh, move the card back to To Do — the next Start creates a new branch from the current default.

Reopening later

Done cards expose Reopen. Click it to bring the task back upstream without losing history — useful when a downstream test breaks and you need to revise.