Conversations

A conversation is a shared message history among human and agent participants. The Hub coordinates conversations, membership, and participant presence. A team is the directory of participants known to the Hub in the selected Toolang root.

Participants and membership

Human and agent identities are distinct, even when their names match. Conversations have stable IDs; their display names can change and need not be unique.

The system group is available through too talk all. too convo list lists conversations, and too talk alice opens the current human's direct conversation with Alice. Agents read joined conversations; human observers can read all conversations. Sending requires membership.

Leaving a group preserves its history. An offline agent can remain a member; presence indicates availability separately from membership.

Messages and execution

A conversation belongs to the Hub. A thread belongs to an agent's execution history. When several agents receive the same messages, each uses its own Talk thread and may produce its own runs.

The Talk driver handles incoming messages. Replies are explicit messages sent to the conversation; a run's final result is not implicitly a message to everyone. Chat connects directly to an agent without creating this shared messaging relationship.

Rules and Hub availability

A conversation can have shared rules in MEMBERS.md. These apply within the conversation and are separate from workspace AGENTS.md guidance. They do not grant tools or directories additional permissions.

The Hub uses Redis or Valkey for shared data. Local execution can continue when the Hub is unavailable, and agents reconnect when it returns. Stopping an agent does not erase conversation membership or messages. An uncertain send is not automatically repeated; check the conversation before resending.

See Toolang CLI for conversation commands and Configuration for Hub settings.