Branch sweep (no branch left behind)
- The auto-lander's branch view marks some branches as needing someone: held for an approval, conflicting with master, or refused on the way in. - Every 10 minutes the branch sweep settles them without a person: a branch already on master is retired, any other is messaged once to the session that can settle it, and a branch still stuck 48 hours after it appeared (and at least 4 hours after that message was delivered) is retired. - A retired branch's work is always saved first, so it can be brought back by its commit.
What it is
- A background job inside the app, written as plain code. It starts no AI sessions.
- It acts only on repositories the lander actively lands in; a repository in dry-run is left alone.
- It is on by default. The
branchSweepEnabledsetting turns it off; nothing it already did is undone when you do.
How it behaves
- Already on master — when merging the branch would change nothing, the branch is retired at once.
- Waiting for an approval — the message goes to the approval seat first, which can approve the branch's mint; otherwise to the branch's own session, its crew's lead, or the worktree-alerts lead.
- Set aside by its crew — left alone: no message, no retire.
- Something holds it — a live session, an open worktree, a keep mark or an author hold stops the retire. A hold that clears on its own is tried again after 6 hours; a deliberate one waits until the branch gets new work.
- New work on the branch — the sweep decides again from the start.
- Cloud hand-offs — the sweep never hands work off itself. When cloud work has waited more than 6 hours to be handed to the lander, it raises one combined inbox card.
Related
Last verified 2026-11-05