Assigning an Agent on Mobile Now Actually Starts Its Run
Assigning an agent to a task from the mobile app now starts that agent's run, matching the web app's behaviour exactly, including for sub-tasks.
Summary
Assigning an agent to a task from the mobile app used to show the agent on the task without ever actually starting its work. That's fixed — assigning from mobile now behaves exactly like assigning from the web.
What You Gain
Previously, tapping to assign an agent from your phone looked like it worked — the agent's name appeared on the task — but nothing actually happened behind the scenes, leaving you to notice later that no progress was being made and start the run some other way. Now the agent starts immediately if the task is ready to go, and if it's sitting in a waiting status like Open or Backlog, the task clearly explains why it hasn't started yet instead of leaving you guessing.
How It Works
- The agent starts right away when the task is ready; a note explains the delay if the task is still in a waiting status.
- Sub-tasks are handled properly — if the task has sub-tasks, you're asked whether to assign them to the same agent, and they're queued to run one at a time in order, just as on the web.
- Re-assigning cancels the previous pending run, so you never end up with two agents working the same task.
- The same fix covers the board, the CLI, and older app versions, not just the newest mobile release.
Where to Find It
Assign an agent to any task from the mobile app exactly as before — the fix applies automatically with no extra steps.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.