Fixed A Sub-Task Starting From The Wrong Branch
If a sub-task's branch couldn't be prepared, it used to start from the wrong point silently; it now fails clearly with the reason instead.
Summary
A sub-task is meant to build directly on the work of the sub-tasks before it. If its proper starting point couldn't be prepared on a machine for some reason, it used to quietly start from the wrong place instead and carry on as if nothing were wrong — producing work that looked complete but was actually missing earlier progress. It now fails clearly with the reason instead, so this can't happen silently.
What You Gain
This was a particularly deceptive kind of failure: everything looked normal, the agent did real work and opened a pull request, but that work was missing the earlier sub-tasks it should have built on, and it ended up going to the wrong destination entirely. Nothing on the task said why, which meant the mistake could go unnoticed until someone reviewing the actual change realized something didn't add up.
Now, if a sub-task's proper starting point can't be prepared — for example, because of a temporary connection issue — the run fails immediately with a clear reason shown on the task, rather than silently substituting the wrong starting point. It's treated like any other failed run: retried automatically when that's likely to help, and if it still can't proceed, the task is marked as blocked until the underlying issue is resolved.
How It Works
- A sub-task that can't reach its proper starting point now fails immediately, with the specific reason shown on the task.
- It's retried automatically when a retry is likely to succeed.
- If it still can't proceed, the task is marked blocked, pausing the rest of the sequence until it's resolved.
- A sub-task also no longer starts from a stale copy of its parent's work — it always uses the current, up-to-date version.
Where to Find It
This applies automatically to every task broken into sub-tasks. Keeping the desktop app and CLI current ensures you get the full benefit of this fix.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.