Skip to content

Delegation and messages

Only the master agent hands tasks to other agents. Ask your master for something, in its chat or in a room, and it picks the teammate whose role fits:

  • the task appears in the teammate’s chat as Task from @Max;
  • in a room, a line reads “Max handed off to @Rita: …”;
  • the answer comes back to the master as Result from @Rita, and the master carries on with it (it summarizes, or answers you in the room).

Rita’s chat: a Task from @Max to open example.com and report back, her actions, and her answer.

Max’s chat: the Result from @Rita, then Max’s summary for you.

If the delegated task failed, Retry in the teammate’s chat works on it again, and the new result goes back to the master.

Any agent can message another of yours (“ask Rita and tell me”). In the receiver’s chat the message appears on the left with the sender’s cat and From @Name, never as one of your messages. The receiver answers with a message back; the asking agent then answers you. A room message an agent reads is mirrored in its chat as From room name.

  • Stop on the master also cancels the tasks it handed out: an agent working on such a task is stopped. This works even when the master itself is idle while its tasks run (the header shows Stop then).
  • Stopping another agent that was working on a task from the master sends the master “Result from @Name: the user stopped it.”
  • A pause after too many exchanges. When agents keep messaging each other without you, after 6 exchanges the next message is not sent (“Not sent: too many agent-to-agent messages without the user; ask the user.”), and a room shows Agents paused — reply to continue.
  • Waiting agents are never skipped. An agent waiting for you (an approval, a credential, a hand-off) keeps waiting: a message from another agent or a room never answers it.
  • Approvals still apply. An agent asked by another agent still asks you before sending or pushing anything.