A Merged Pull Request Now Closes Only Its Own Task
Merging a pull request used to mark every task it mentioned as Done; it now closes only the task the pull request actually belongs to.
Summary
Merging a pull request previously marked every task mentioned anywhere in it as Done — including tasks it simply referenced, not just the one it was actually for. A merge now closes only the pull request's own task, alongside several other fixes that make long or busy agent runs more reliable.
What You Gain
Before this fix, mentioning a related task in a pull request's description — even just a note like "follow-up to" another task — could cause that other task to be marked Done the moment the pull request merged, whether or not its actual work was finished. For a sub-task whose description names its larger parent task, this could even mark the parent Done before its own work was complete.
Now a merge affects only the one task the pull request is actually for, sharpening the original rule that only a merged pull request closes a task. Tasks it merely mentions stay exactly as they are, still linked to the pull request for reference, with a note recorded so it's clear they were referenced but not closed.
How It Works
- A merge closes only its own task — the one named in the pull request's branch, falling back to its title or description only if the branch doesn't name one.
- Tasks that are only mentioned are left untouched, with a visible note that they were referenced.
- Long-running agent work no longer loses access partway through. Previously, a run's access could expire after an hour even if it was still actively working; it now stays valid for as long as the run is alive, so a long run can still report back when it finishes.
- Cancelling a parent task's run no longer accidentally starts its sub-tasks. The task clearly shows how many sub-tasks are being held, and resuming the parent's work picks them back up.
- Machines running an older app version are flagged, so if a run happens on an outdated machine, that's visible on the task rather than a silent mystery.
Where to Find It
This applies automatically to every project — there's nothing to configure. Keeping the desktop app and CLI up to date ensures you get the full benefit of the reliability improvements.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.