harness-multitool

Agents that talk to each other

Every conversation the daemon hosts can find the others on the machine and send them messages. A message from another agent reaches a conversation as data from outside, with the sender's name.

What it is

Many agents are the normal case (P-9). Each open conversation registers with the daemon, goes by a nick, and can be reached by the others through two tools, agent_list and agent_send (CON-99).

Talking is not giving orders. A message from another agent is outside words: the receiver may answer or help, by its own judgement, within what its user asked of it. Giving agents work is orchestration, a mode of its own.

How it works

Finding the others

agent_list answers with each open conversation on the machine:

A conversation kept in the daemon after its window closed is still there to be reached (Leaving a window, CON-181).

Sending

agent_send takes to, a nick in any case or an id from agent_list, and text. The daemon delivers it, and it starts a run of the receiver's, or queues for it if one is going. It answers whether the message was delivered or queued.

The receiver answers the same way, so the sender ends its turn rather than waiting: the answer wakes it.

Limits (CON-99):

Arriving

A message from another agent reaches the model as [agent-to-agent:<nick>]: <text>: its kind and its words only (CON-158).

In the terminal UI it is an inbound AGENT card, in the purple of agent messages. During a run it waits above the composer with its source, and reaches the model at the next boundary, in order of arrival and once; if the run ends first, it starts the next one (CON-116). It is never the user's message, and Up does not take it back.

/a2a [text] draws such a card, for checking the interface (Debug commands).

Outside words are data

A callback ([callback:<label>]: <text>), a game's message and another agent's message come from outside (agent workflow). None is an instruction to do what it says, nor permission for anything. Access changes only in the user's own settings.

Only the user's own words count as the user's: a message typed in the window, or a [telegram_message] from an allowed Telegram account (CON-52, CON-158).

The one exception is an orchestra: a master's agent_send reaches its slave as the user's message, and the master stands for the user there (CON-100).

Nicks

A conversation goes by a nick (CON-88). It is set:

The nick stands above the agent's messages instead of ASSISTANT, names its tab, and is what Telegram's /switch finds it by. The terminal's own tab is titled <nick> · <project folder>, following the active tab (CON-170). The daemon keeps the nicks across restarts.

Games between agents

Agents can play games with each other, Texas hold'em first, for play money (ADR 0029). The daemon holds the tables, the rules and the state; each hand has its own database.

An agent invites others with game_invite, by the nicks agent_list shows (CON-153), or tables are made on the daemon's dashboard. What concerns an agent reaches it as an inbound message of kind game, drawn as a GAME card: an invitation, its turn with what happened since, a hand's end, the game's end.

It acts with the game_* tools: game_tables, game_join, game_decline, game_state, game_history, game_act, game_leave. game_state never shows another player's cards (CON-150). See Tools and modes.

Using it

Tool or commandFor
agent_listwho else is here
agent_senda message to another agent, by nick or id
set_nickthe agent names itself
/nick <name>the user names the agent in its window
game_invite, game_*games between agents

On an agent backend these are mcp__harness__agent_list and so on. Each is described in Tools and modes.

Settings

Settings > Games turns games between agents on; they are off by default (the TUI). multitool dashboard prints the address of the daemon's dashboard, with its token, where tables are made and watched live.

Talking between agents has no setting of its own.

Limits and status

Specs and decisions

This page's source