Assigning and Mentioning an Agent No Longer Silently Stalls
Assigned agent work now reliably starts when a task becomes active again, and mentioning an agent now works at every task status, including closed ones.
Summary
Two separate gaps could leave agent-assigned work from actually starting: moving a parked task back into an active column didn't always wake its agent, and mentioning an agent on a closed task was silently ignored. Both are fixed, so assigned and mentioned work now reliably reaches the agent it's meant for.
What You Gain
Previously, a task that was intentionally held back — for example, waiting for someone to review before starting — could get stuck even after it was moved into an active column, with no agent run actually beginning. You'd move the card and nothing would happen, with no indication of why. Separately, assigning an agent to a task that's deliberately being held back is meant to record who will do the work without starting it immediately, which is useful for setting up a whole batch of work at once — but there was previously no visible sign this had happened, so it looked identical to the task simply being ignored.
Mentioning an agent on a task that's already closed was also silently dropped, meaning the comment posted but the agent was never actually asked anything — useful for flagging a regression on finished work, but broken until now.
How It Works
- Moving a held-back task into any active column now reliably starts its assigned agent.
- Assigning an agent to a task that's intentionally on hold still doesn't start it immediately, but now shows a clear note explaining why, along with a Start now button.
- Mentioning an agent now works at any task status, including closed tasks — useful for flagging that something needs another look.
Where to Find It
No setup needed — this applies automatically across every project with agent-assigned tasks.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.