Teams and many Gateways
Connect many Gateways
The ways separate Gateways work together: agents handing each other tasks, private agent messages, one person reaching several Gateways, and shared sessions.
Read when: Your agent should work with another company's or another member's agent, or you run more than one Gateway.
OpenClaw has no single switch that joins Gateways into one system. Each Gateway owns its own agents, sessions and keys. What it has is a set of ways for separate Gateways to work together, each for a different job: agents on two Gateways handing each other tasks, private messages between agents owned by different people, one person or app reaching several Gateways, and one Gateway showing another's sessions.
Which one to use
| Way | Connects | Who dials whom | Status | On Urbicana today |
|---|---|---|---|---|
| A2A channel | An agent on one Gateway to an agent on another, or any A2A agent | The sender's Gateway posts to the receiver's /a2a/v1 | Released | Boostt → member Member → member |
| Reef | Agents owned by different people, end-to-end encrypted | Each Gateway connects to the Reef relay | Bundled | Guard sign-in |
| MCP Relay, native apps | One person or app to several Gateways | Each Gateway dials the relay, or the app dials each Gateway | Released | Not tried |
| Session Share | Read-only sessions from a source Gateway into a team Gateway | A node on the source dials the team Gateway | Off by default | Door refuses nodes |
| Deal rooms (Urbicana) | A member's agent and the people in a Boostt room | The Gateway reads the rooms from Boostt | Urbicana plugin | Works |
Several Gateways on one computer (OpenClaw profiles such as a rescue bot) share nothing and never talk to each other. The old experimental openclaw fleet command was removed, and nothing in the code federates Gateways.
Agent to agent: the A2A channel
The A2A channel is a bundled plugin that speaks the A2A 1.0 protocol. A Gateway publishes an Agent Card at /.well-known/agent-card.json (public, one skill per exposed agent) and takes tasks at POST /a2a/v1. Every caller is a named peer with its own bearer token; there is no anonymous mode. Each peer and conversation gets its own session on the receiving side, answered by the agent your bindings choose, with that agent's normal tools and approvals.
Configure two Gateways
Make two secrets: one Alice uses to call Bob, one Bob uses to call Alice. Alice's config:
channels: {
a2a: {
enabled: true,
advertisedUrl: "https://alice.example.com",
peers: {
bob: {
token: "${A2A_BOB_IN}",
url: "https://bob.example.com/a2a/v1",
outboundToken: "${A2A_BOB_OUT}",
},
},
},
}
Bob mirrors it with a peer alice. Or in the Control UI: Settings → Connections → Channels → A2A, with Advertised Gateway URL, Exposed Agent IDs, Inbound Bearer Token and Outbound Bearer Token, then Save. Restart after changing environment variables.
openclaw message send --channel a2a --target bob --message "Can you quote a kitchen renovation in Brooklyn?"
| Check | What you see |
|---|---|
curl https://bob.example.com/.well-known/agent-card.json | The card, with /a2a/v1 and one skill per exposed agent. |
A SendMessage without a token | 401 "Unauthorized; configure channels.a2a.peers with a matching Bearer token". |
openclaw channels status --probe | The A2A account running, with any missing token named. |
| Bob's Control UI after Alice sends | A new session from peer alice. |
| Limit | Value |
|---|---|
| Content | Text and JSON only: no files, streaming or push |
| Size | 1 MiB per request; 64 KiB of text |
| Rate | 30 requests per minute per peer by default |
| Slash commands | Refused: a peer cannot run /reset or other commands |
| Approvals | The task waits as WORKING until the owner decides in the Control UI or a chat |
| Finished tasks | Kept 24 hours, at most 500 |
From docs/channels/a2a.md and extensions/a2a/src/ (channel.ts, outbound.ts:44-85, inbound.ts).
Private agent-to-agent: Reef
Reef is an end-to-end-encrypted channel between OpenClaw agents owned by different people. Messages are sealed on your computer and screened by a guard model in both directions; the relay operator cannot read them. One handle is one claw; a person can hold several.
- Browser, then terminalSign up at reefwire.ai, then run
openclaw channels addand choose Reef. The wizard asks for the relay, your email, a handle, who may send requests, and the guard's credential. - The friend's chatThey run
/reef friend codeand send you the code. - Your chat
/reef friend request @friend CODE. - The friend's terminal
openclaw pairing approve reef <CODE> - Either sideThe agent sends to
reef:<handle>, oropenclaw message send --channel reef --target @friend --message "…".
Each friend gets an autonomy tier (notify-only, bounded, extended); messages the guard parks wait for /reef review approve. The guard signs in with an OpenAI account through Codex, or with an OpenAI or Anthropic API key.
One person, several Gateways
| Where | How |
|---|---|
| ChatGPT, Codex, Claude through MCP Relay | Link each Gateway (Sign in with Gateway or a pairing code); Your Gateways offers Open, Set primary (the one the conversation tools use) and Remove. Each Gateway keeps its own grant. |
| macOS app | Connection… → Gateways → Add Gateway; switch from the account card, Command-click to open one in a new window. |
| iOS | Settings → Gateway → Paired Gateways; Forget removes one. |
| Android | Settings → Gateway: Add Gateway, Manage Gateways. |
| OpenClaw ID (Labs) | One account can own several claws, each its own Gateway. |
Show sessions from another Gateway
Session Share (off by default) shows chosen sessions from a source Gateway in a team Gateway's sidebar, read-only, refreshed every 30 seconds. On the source, put sessions in a shared group (share.groups: ["Team"]). On the team Gateway, openclaw plugins enable session-share and openclaw devices join-code. On the source, connect with that code and the two session commands, then approve the device on the team Gateway.
openclaw connect <join-url> --service --commands openclaw.sessions.list.v1,openclaw.sessions.read.v1
On Urbicana today
Boostt to a member's computer
Each member computer runs the A2A channel with one peer, boostt, seeded at every boot. The door lets the card and /a2a/v1 through without a sign-in. Boostt publishes the member's card at geo.boostt.org/a2a/agents/<handle>/agent-card.json, pointing at Boostt's own router; a caller with a Boostt account token sends there, and the router forwards the task to the member's computer with the boostt token, waits for the result and returns it.
| Step | Today | Why |
|---|---|---|
Card and /a2a/v1 reachable | Yes | They pass the door without a session (agent-proxy/src/proxy.ts, isA2aPath). |
| Boostt forwards a caller's task | Works in code | The router adds "From <caller> requesting <skill>…" to the text, since OpenClaw drops message metadata. |
| Many callers at once | Check | Every caller is the peer boostt, so they share one 30-per-minute limit. |
| The computer's own card | Check | No exposeAgents is set, so my.<name>/.well-known/agent-card.json lists every agent ID. |
Deal rooms
The urbicana plugin's boostt channel turns Boostt deal rooms into Gateway conversations. Every 5 seconds the computer reads the member's rooms with the member's token; each room is one session, only the room's participants are admitted, and the agent's reply is posted to the same room under the member's account. Rooms are opened by Boostt (a quote, a booking, a service order); the agent sees a new room once it has an unread message.
Two members' computers directly
Not today. From the code:
| Blocker | Where |
|---|---|
The only peer is boostt, with no address to send to. | proxy.ts seed; outbound.ts:44-53 |
| Another member's computer holds no token this one accepts. | extensions/a2a/src/channel.ts |
| Peers added by hand are replaced at the next boot. | agent-proxy/fly/entrypoint.sh:140 |
The boostt token also signs every session out, so it cannot be shared. | proxy.ts, /session/revoke |
| Replies do not come back by themselves. | outbound.ts:72-85 |
A peer address must be https://my.<name>…/a2a/v1: outbound A2A refuses the redirect from the website address. | outbound.ts |
| Way forward | What it takes | State |
|---|---|---|
| Direct pairs | The boot keeps member-added peers beside boostt (small change at entrypoint.sh:140), plus a way to make per-pair tokens and swap addresses (Rails or the member's UI). | Not decided |
| Through Boostt's router | An outbound peer to the router with a Boostt token, which expires in 3 days, and a way to deliver the answer back. | Not decided |
| Deal rooms | Works today, through Boostt's rooms. | Works |
| Reef | Its guard has no Claude subscription sign-in; a Claude-only member cannot run it. | Blocked |
Videos to record
29 · Read a Gateway's card
Terminalcurl …/.well-known/agent-card.json.- Point at the
/a2a/v1address and the skills, one per agent. - Set Exposed Agent IDs, Save, curl again. Fewer skills.
30 · Two Gateways talk
Two Control UIs side by side- Add the peers on both.
- From Bob:
openclaw message send --channel a2a --target alice …. - A session from
bobappears on Alice's side and her agent answers. - Show that Bob sees the answer only when Alice's agent sends to
a2a:bob.
31 · Approval across A2A
Terminal and Control UI- Send a task that needs a shell command.
GetTask.WORKING.- Approve in the Control UI.
GetTask.COMPLETED.
32 · Reef friends
Two Gatewaysopenclaw channels add→ Reef on both./reef friend codeon B; request from A.openclaw pairing approve reefon B.- A's agent sends to
reef:@b.
33 · How another agent reaches my computer
Terminal and a member's computer- Open
geo.boostt.org/a2a/agents/<handle>/agent-card.json; point at the router address and "A Boostt account token". - Send a task with a test member's token.
- On the member's computer, an A2A session from
boosttstarting "From <caller>…". - Show the answer returned to the caller.
34 · A deal room my agent answers
The site as member B, the computer of member A- As member B, request a quote and write a message.
- Within about 5 seconds, member A's computer has a session for the room.
- The reply appears in B's messages under A's name.