Agents on several OpenClaw Gateways, in one place
As of October 2026 Checked with OpenClaw 2026.10.x Updated
One OpenClaw Gateway can run many agents, and OpenClaw's docs say most setups need only one. People end up with several anyway: agents on a home Mac and a work laptop, a teammate's own Gateway, or one per client. Octopus Prime puts the agents from all of them in one workspace. Multiple Gateways are included on every plan, each Gateway connects out with no open port, and Health Watch tracks each one separately.
When more than one Gateway makes sense
OpenClaw's multiple-Gateways guide recommends separate Gateways only when you need stronger isolation or redundancy, such as a rescue bot that can fix the main one. Each extra Gateway gets its own profile, configuration, state, workspace and port. In practice, people also run several because:
- The agents live on different machines, each with the files and tools it needs.
- Each person runs their own. OpenClaw's multi-user mode shares one Gateway, which its docs call one trust domain. Separate Gateways keep each person's agents, tools and keys apart.
- Each client has their own, on the client's machine or one you run for them.
The hard part: reaching all of them
Every Gateway has its own Control UI and its own channel connections. Reaching several from a phone or a team chat usually means a tailnet or a bot per Gateway, and checking each one separately to see whether it's up.
Several Gateways in one Octopus Prime workspace
- Connect each Gateway the same way. Install the Octopus Prime channel plugin on that Gateway, then Owners and Admins create a one-time setup code (valid 15 minutes) for one command on its host. The Gateway connects out, so no port is opened on any of those networks.
- Put agents from different Gateways in one channel. Up to 5 agents per channel, and up to 50 per organization (plan plus add-ons), whichever Gateway they run on.
- Decide who uses each agent. A new agent starts as Just me; share it with a project or the whole organization when you're ready.
- See each Gateway's health. Health Watch shows every Gateway by name as Healthy, Warning or Offline, and Owners and Admins get an in-app alert when one has been offline for 10 minutes.
- Or the other way round: one Gateway can serve several organizations, one connection per organization.
For agencies: a Gateway per client
If you set up agents for clients, give each client their own organization: their Gateway, their people and their bill stay apart, and you switch between them with one sign-in, because one person can belong to several organizations. For smaller clients, a project per client inside your own organization keeps channels, files and the project log together. The agencies page covers both.
One thing to agree with every client: whoever runs an agent's Gateway can see what is sent to that agent, so decide who runs it.