Multiple Gateways (same host)
Most setups should use one Gateway because a single Gateway can handle multiple messaging connections and agents. If you need stronger isolation or redundancy, run separate Gateways. Both are supported.Isolation checklist (required)
CLAWDBOT_CONFIG_PATH— per-instance config fileCLAWDBOT_STATE_DIR— per-instance sessions, creds, cachesagents.defaults.workspace— per-instance workspace rootgateway.port(or--port) — unique per instance- Derived ports (bridge/browser/canvas) must not overlap
Recommended: profiles (--profile)
Profiles auto-scope CLAWDBOT_STATE_DIR + CLAWDBOT_CONFIG_PATH and suffix service names.
Port mapping (derived)
Base port =gateway.port (or CLAWDBOT_GATEWAY_PORT / --port).
bridge.port = base + 1browser.controlUrl port = base + 2canvasHost.port = base + 4- Browser profile CDP ports auto-allocate from
browser.controlPort + 9 .. + 108
Browser/CDP notes (common footgun)
- Do not pin
browser.controlUrlorbrowser.cdpUrlto the same values on multiple instances. - Each instance needs its own browser control port and CDP range.
- If you need explicit CDP ports, set
browser.profiles.<name>.cdpPortper instance. - Remote Chrome: use
browser.profiles.<name>.cdpUrl(per profile, per instance).