Problem

OpenClaw's browser service defaults its CDP port range to 18800, derived from:

gatewayPort (18789) + 2 + 9 = 18800

Clawline's default network port is also 18800. Anyone running both OpenClaw and the Clawline iOS companion on the same machine will have a silent port conflict — the browser service and Clawline can't both bind to 18800.

This is a natural use case: Clawline is the companion app for the same gateway, so running both on the same machine is expected.

Proposed Fix

Two options (either or both would help):

Option A — Change the default CDP range start to something that doesn't collide with Clawline's default, e.g. 19000 or a clearly separated range.

Option B — Add a config override in openclaw.json so users can set their own browser CDP port start:

{
  "browser": {
    "cdpPortRangeStart": 19000
  }
}

Option B gives flexibility; Option A fixes the out-of-the-box experience for everyone. Ideally both.

Context

• Gateway port: 18789 (default)
• Clawline network port: 18800 (default)
• Browser CDP start: 18800 (derived from gateway port via hardcoded offset)
• Workaround: manually configure Clawline to a different port, or patch locally

The defaults should coexist without conflict when both are installed on the same machine.