More reliable task delivery
- Tasks survive a restart. A task that an agent received but never finished because Relay closed is queued again when Relay starts, and waiting tasks are delivered in the order they were sent. After a crash, an agent may occasionally be given the same task twice.
- Queued work arrives without a nudge. Tasks waiting for an agent are delivered as soon as its terminal is ready. Before, they could wait until someone sent another task. Several waiting tasks are now delivered one after another, not one per new send.
- An unavailable agent no longer loses work. If a task cannot be handed to its terminal yet, Relay retries for a short while and then waits. The task stays queued until the terminal comes back.
- If a terminal disappears while a task is being handed to it, the sender gets a clear failure with the reason instead of a task that never finishes.
Finishing a task
relay result, given the task ID and a short summary, is the only way to finish a task an agent was given. The task text agents receive and the bundled Relay skill now say this plainly: replying with relay ask sends an ordinary message and does not finish the task.
Your next build