Agent Tasks No Longer Build on Top of Each Other's Branches

Summary

Effigate Command Center previously let one task's branch build directly on top of whatever branch a different, unrelated task happened to leave open — a shortcut meant to avoid conflicts that could, in rare cases, cause a task's finished work to never actually reach your main branch. That shortcut is gone, replaced with a clearer, more predictable set of rules for how every task's work gets built and merged.

What You Gain

Before this change, if two tasks ran in quick succession, the second could end up branching from — and opening its pull request against — whatever branch the first task had just created, purely to avoid stepping on unfinished work. That worked most of the time, but it meant a task's fate was quietly tied to an unrelated task's branch. If that branch was abandoned once its own work merged, the second task's changes could be left stranded without ever reaching your main branch.

Now, related sub-tasks under the same parent task share one common branch that only merges into your main branch once at the end, after every sub-task's work is already on it. A standalone task always branches from a freshly updated, known-good starting point — either the base branch you've configured for the project, or your repository's real default branch — never from another task's branch. If an agent still opens a pull request against the wrong branch, Effigate Command Center now checks and automatically retargets it.

How It Works

• Sub-tasks under the same parent share one integration branch, which merges into your main branch only once, at the end, with every sub-task's work included.
• A standalone task always branches from an up-to-date, known starting point, never from another task that happens to be mid-flight.
• Every starting branch is refreshed from your repository before a task branches from it, so agents never build on something already out of date.
• If a task needs to retry, it reuses its own existing branch when earlier work on it is still unmerged, and rebuilds cleanly from the base branch when that work has already landed.
• If an agent opens a pull request against the wrong branch anyway, Effigate Command Center automatically retargets it to the right one.

Where to Find It

This applies automatically to every project with agent-assigned tasks, on both the desktop app and the standalone command-line tool — there's nothing to configure.

See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.