Group chats and hand-offs
Put several employees in one room, mention them by name, and let them hand work to each other with a typed brief. Limits keep it from spiralling.
Updated 2026-10-13
Group chats are on Base and Premium. Ask Pytheus to “open a group chat with the researcher and the writer to plan the launch”, or create one from Team and pick who is in it.
In a group
@Nameaddresses one member. A message with no mention goes to Pytheus.- Put files a teammate needs in the shared folder before handing work over.
- Say “do not start anything yet” and Pytheus leaves out the kickoff brief.
Hand-offs
A hand-off carries a typed brief: the task, the constraints, and what should come back (a deck, a sheet, a document, a site or an answer). The receiver starts right away.
| Limit | Value |
|---|---|
| Depth of hand-offs from hand-offs | 2 |
| Hand-offs at once, per turn | 4 |
| Live hand-offs per original request | 8 |
- Hand off only what you cannot do yourself in about two steps.
- Never answer for a teammate, and never say their work is done before they report it.
Delegation by Pytheus
When you give Pytheus a bigger job it may use delegate_to_employee with a self-contained brief: the goal and what it is for, who the result is for, context, constraints, and what done looks like with two or three checks. Vague briefs get vague work. The employee’s report, with any files, comes back into your chat as well as theirs.