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)

• BOT_CONFIG_PATH — per-instance config file
• BOT_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.

Recommended: profiles (--profile)

Profiles auto-scope BOT_STATE_DIR + BOT_CONFIG_PATH and suffix service names.

# main
bot --profile main setup
bot --profile main gateway --port 18789

# rescue
bot --profile rescue setup
bot --profile rescue gateway --port 19001

Per-profile services:

bot --profile main gateway install
bot --profile rescue gateway install

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)

# Main bot (existing or fresh, without --profile param)
# Runs on port 18789 + Chrome CDC/Canvas/... Ports 
bot onboard
bot gateway install

# Rescue bot (isolated profile + ports)
bot --profile rescue onboard
# Notes: 
# - workspace name will be postfixed with -rescue per default
# - Port should be at least 18789 + 20 Ports, 
#   better choose completely different base port, like 19789,
# - rest of the onboarding is the same as normal

# To install the service (if not happened automatically during onboarding)
bot --profile rescue gateway install

Port mapping (derived)

Base port = gateway.port (or BOT_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

BOT_CONFIG_PATH=~/.bot/main.json \
BOT_STATE_DIR=~/.bot-main \
bot gateway --port 18789

BOT_CONFIG_PATH=~/.bot/rescue.json \
BOT_STATE_DIR=~/.bot-rescue \
bot gateway --port 19001

Quick checks

bot --profile main status
bot --profile rescue status
bot --profile rescue browser status