Hand off a task. Get reviewed work back.

Autopilot runs a coding task for you from start to finish. A planner agent maps out the change, a developer agent builds it, reviewer agents check it, and the developer fixes what they find until every reviewer approves. You decide what lands in your repo.

How a session runs

• You describe the task. In Autopilot, click New task, pick the repo, write what you want, and launch. Templates get you started.
• Or just ask your agent. In Claude Code, the /autopilot-manager skill turns a plain description into the launch, or into a schedule, so you don't fill in the form yourself.
• A developer agent builds it in its own copy of your repo. It can be one of your own agents. Autopilot creates a git worktree on a new branch. Your checkout and your uncommitted work aren't touched.
• Reviewer agents check the change. The repo reviewer reads your repo's CLAUDE.md, and your own specialists can review too. The developer fixes their findings, and the loop repeats until every reviewer approves. Then Autopilot commits the work on its own branch.
• You stage it and commit. Read the report, then click Stage into dev (the button names your base branch). The changes land in your repo staged, not committed. Look them over and commit yourself, or run a Review + revise task first for a cold-eyes review of the staged changes. That one works in your checkout itself and stages its fixes there.

What stays in your hands

• Risky steps come to you. Safe steps inside the worktree are approved for you. An overseer agent weighs the riskier ones, and anything it can't clear waits for you in the Responder.
• You can watch every step. Each session shows its phase, the reviewers' verdicts and a timeline. Open in terminal takes you to the agents' panes.
• Nothing from a Full dev run reaches your repo until you stage it, and nothing is committed to your branches until you commit.

Four ways to run it

• Full dev: plan, develop, review, revise. The complete pipeline. Can run on a schedule.
• Review + revise: a fresh review of changes you already staged (or committed on a branch), in your checkout itself. The developer fixes what the reviewers flag and stages the fixes there.
• Plan only: writes a plan and stops. No code changes.
• Ops: read-only work in the repo itself, no worktree, and a report at the end. Can run on a schedule.

What you need

• ACTower Premium. See Pricing.
• tmux, Claude Code, and a git repo. Any repo works. actower doctor checks your setup.

Next: Your first Autopilot task.