Branch strategy & Autopilot

Branch strategy

Set this per project in Settings → Projects & repository:

• Branch per ticket (the default): each ticket ships on its own branch and opens a draft pull request, so two tickets in flight get two branches and two PRs. Good for teams that review changes before they merge.
• Single working branch: every ticket ships straight to one shared branch. Good for a solo developer or a team that trusts the pipeline's checks over a review step.

Either way, protected-branch rules still apply: the agent can't force-push, rewrite history, or push directly to a branch you've protected.

Autopilot

Autopilot is a per-project toggle (Queue → Autopilot) that runs the queue without you clicking Run now on each ticket.

When it's on and idle, it picks up the highest-priority Ready ticket whose dependencies have all shipped, using the same ordering as the Ready column. A few things keep it predictable:

• It only runs within the working hours you set for the project. Nothing starts outside them.
• A ticket blocked by an unshipped dependency is skipped, with the reason shown on the ticket.
• If the project has hit a budget cap, Autopilot enqueues nothing until it's raised or the next period resets. It doesn't queue up work and wait, it just stays idle. See Budgets and cost control.
• Only one ticket runs per project at a time.

Turning Autopilot off at any point leaves whatever's currently Running to finish; it just stops picking up the next one.