Agent Bus

Agent names

Every agent has its own name, unique across the whole fleet. An agent tied to one project or topic has a name shaped like <role>--<scope>, e.g. sa--314. See them with /agent status.

Scopes

A scope groups agents together for one project or topic; each scope is tied to its own working directory. /scope list, /scope add <name> <abs-path>, and /scope rm (group creator only) — pick the scope to remove from the list, or /scope rm <id>; you confirm before it is removed.

Bind a chat topic to a scope with the /scope command, right in the chat.

Sending from chat

There are four ways to send a message to an agent from chat:

• /ask <agent> <text> — send to any registered agent
• /<agent> <text> — call that agent directly
• @<agent> <text> — mention the agent in the message body
• Reply to a message an agent just relayed — it’s delivered straight to that agent, no command needed

How an agent replies

An agent’s reply lands back in the same chat/thread you sent the message from — you never need to look for it elsewhere.

Agent to agent

Agents also message each other by name, the same way you message an agent. You don’t see that back-and-forth, only the final result once an agent reports back to you.

Where to go next

• Chat commands — the full command list