openclaw - 💡(How to fix) Fix Bug: Sub-Agents connect to wrong port (18789 instead of 63333) [2 comments, 3 participants]

Sub-Agents spawned via sessions_spawn fail to connect with "pairing required" error because they attempt to connect to the Gateway Control UI port (18789) instead of the Main Agent port (63333). 3. Error occurs:

Fix Plan

To resolve the issue, we need to configure the sub-agents to connect to the Main Agent port (63333) instead of the Gateway Control UI port (18789).

Step-by-Step Solution

• Update the sessions_spawn command to specify the correct port:

  sessions_spawn --runtime subagent --model moonshot/kimi-code --task "test" --mode run --gateway-port 63333

• Alternatively, update the OpenClaw configuration to use the Main Agent port as the default for sub-agents:

  {
    "gateway": {
      "port": 63333,
      "mode": "local",
      "bind": "auto",
      "subagentPort": 63333, // Add this line
      "controlUi": {
        "allowInsecureAuth": true,
        "dangerouslyDisableDeviceAuth": true
      },
      "auth": {
        "mode": "token",
        "token": "REDACTED"
      }
    }
  }

• If the above configuration change is not possible, you can also use environment variables to override the gateway port for sub-agents:

  GATEWAY_PORT=63333 sessions_spawn --runtime subagent --model moonshot/kimi-code --task "test" --mode run

Verification

To verify that the fix worked, run the sessions_spawn command with the updated configuration or environment variable and check that the sub-agent connects to the correct port (63333) without requiring pairing.

Extra Tips

• Make sure to update the documentation and guides to reflect the correct port usage for sub-agents.
• Consider implementing a check in the OpenClaw configuration validation to ensure that the sub-agent port is set correctly.