See Which Agent's on a Task, and Stop It Cleanly
A live banner now shows which agent is working on a task and how many runs are queued, while merging its pull request stops any agent still working on it.
Summary
It's now clearer when a task already has an agent working on it, so you don't accidentally queue a duplicate run — and merging the pull request now stops any agent still working on it, instead of letting it run on after the work is done.
What You Gain
Before this update, there was no clear signal that a task already had an agent working on it. It was easy to mention the agent again, not realizing that queued a second, redundant run — one that could fail long after the first finished, leaving a completed task looking stuck or broken. And once a pull request merged, any agent still technically "working" on it kept going anyway, wasting time and causing confusing failures on work already done.
Now, open a task with an agent on it and you'll see a live banner naming the agent, when it started, and how many runs are queued behind it, on web and mobile, updating in real time. If you mention that agent again or send feedback while it's working, Effigate warns you that this starts another run, with a one-tap option to leave a note instead. The moment the pull request merges, anything its agents were still doing is stopped automatically, with the task recording what was stopped.
How It Works
- A live status banner on the task shows the working agent, when it started, and how many runs are queued.
- A warning before you duplicate work. Mentioning a busy agent flags that this queues another run, with a quick way to post a note instead.
- Clear run status on every comment that triggered one: Queued, Running, Done, Failed, or Stopped.
- Merging stops leftover work. Once a pull request merges, any agent still working on the task is stopped, and the task records what was cut short.
- Stopping a run really stops it, immediately, from the task, a chat, or a merge — it can't resurface as a failure.
Where to Find It
The status banner and warnings appear automatically on any task with an active or queued run. The improved stop-on-merge behaviour needs the latest desktop app and CLI to take full effect on runs on your own machines.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.