ProblemMulti-Bot rosters degenerate into Bots chatting at each other, repeating work and re-paying for the same context.
TechniqueKeep the durable state of a project in files under /workspace, and make Bot-to-Bot messages carry file paths and one line of context rather than content.
Why it worksA conversation is a context window that is re-read and re-paid for; a file is a pointer. Moving state to disk improves reliability and cost at the same time.
When to useAny pipeline with more than one Bot, and any Bot with durable state.
When not toDo not hide the final result in a file only; keep the result or a link to it in the thread you actually review.