Skip to main content

​
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 (e.g., a rescue bot), run separate Gateways with isolated profiles/ports.

​
Isolation checklist (required)

  • CLAWDIA_CONFIG_PATH — per-instance config file
  • CLAWDIA_STATE_DIR — per-instance sessions, creds, caches
  • agents.defaults.workspace — per-instance workspace root
  • gateway.port (or --port) — unique per instance
  • Derived ports (browser/canvas) must not overlap
If these are shared, you will hit config races and port conflicts. Profiles auto-scope CLAWDIA_STATE_DIR + CLAWDIA_CONFIG_PATH and suffix service names.
Per-profile services:

​
Rescue-bot guide

Run a second Gateway on the same host with its own:
  • profile/config
  • state dir
  • workspace
  • base port (plus derived ports)
This keeps the rescue bot isolated from the main bot so it can debug or apply config changes if the primary bot is down. Port spacing: leave at least 20 ports between base ports so the derived browser/canvas/CDP ports never collide.

​
How to install (rescue bot)

​
Port mapping (derived)

Base port = gateway.port (or CLAWDIA_GATEWAY_PORT / --port).
  • browser.controlUrl port = base + 2
  • canvasHost.port = base + 4
  • Browser profile CDP ports auto-allocate from browser.controlPort + 9 .. + 108
If you override any of these in config or env, you must keep them unique per instance.

​
Browser/CDP notes (common footgun)

  • Do not pin browser.controlUrl or browser.cdpUrl to 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>.cdpPort per instance.
  • Remote Chrome: use browser.profiles.<name>.cdpUrl (per profile, per instance).

​
Manual env example

​
Quick checks