Guide · Agent communication · 8 min read

Agent Communication

Communication is infrastructure. It tells the user who owns a task, where evidence moved, and what needs review.

Communication surfaces

Kaptain Chat is the main supervisor conversation. Team Chat is the shared room for addressing agents and seeing team-level activity. MemberChat is a focused channel with a specific agent. These surfaces are different on purpose: they prevent every interaction from collapsing into one long undifferentiated thread.

Handoffs should be explicit

When work moves from a supervisor to an agent or from one model route to another, the handoff should be bounded. A good handoff includes the goal, relevant evidence, allowed tools, expected output, and review criteria. It should not blindly forward the entire conversation when a smaller evidence package is enough.

Continuity without clutter

Agent communication needs memory, but memory should not mean infinite transcript replay. Kaptain can retain recent messages, summaries, and agent context so continuity survives across turns. The user should still be able to tell what the current task is and what old material is being reused.

Useful patterns

• Supervisor first: use Kaptain Chat for ambiguous intake, then assign bounded work.
• Team room: use Team Chat when several agents need visible coordination.
• Private member work: use MemberChat for focused follow-up with one agent.
• Review loop: ask agents to return evidence and uncertainty, not only final claims.

Continue with Tasks and Delegation.