Skip to content

[Bug]: [Regression] Gateway 5.18+ shows empty Caps for all node versions on Windows/Docker #86987

Description

@dabase

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Problem:

  • Gateway Web UI shows "paired · connected" but Caps column is empty
  • Cannot execute any node commands (browser, file, system, exec)
  • Downgrading gateway to 5.12 immediately fixes the issue

Regression point: 5.12 gateway works perfectly; 5.18+ breaks.

Steps to reproduce

NOT_ENOUGH_INFO

Expected behavior

Environment:

  • Gateway: 5.18/5.20/5.22/5.24_beta1/5.25_beta1 (Docker on Synology)
  • Node: 5.12/5.20/5.22 (Windows native, npm global)
  • Node connects successfully, WebSocket handshake normal

Problem:

  • Gateway Web UI shows "paired · connected" but Caps column is empty
  • Cannot execute any node commands (browser, file, system, exec)
  • Downgrading gateway to 5.12 immediately fixes the issue

Tests performed:

  1. Fresh Docker container with empty data dir — Caps blank
  2. Fresh container with last-good config — Caps blank
  3. Multiple gateway versions (5.18 through 5.25_beta1) — all blank
  4. Multiple node versions (5.12, 5.20, 5.22) — all blank with 5.18+ gateway
  5. WebSocket frame analysis: node response lacks caps/commands fields

Regression point: 5.12 gateway works perfectly; 5.18+ breaks.

Actual behavior

NOT_ENOUGH_INFO

OpenClaw version

2026.5.12

Operating system

gateway(synology),node(windows10)

Install method

node(npm -g),gateway(docker)

Model

kimi-moonshot

Provider / routing chain

openclaw-router-kimi-moonshot

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Environment:

  • Gateway: 5.18/5.20/5.22/5.24_beta1/5.25_beta1 (Docker on Synology)
  • Node: 5.12/5.20/5.22 (Windows native, npm global)
  • Node connects successfully, WebSocket handshake normal

Problem:

  • Gateway Web UI shows "paired · connected" but Caps column is empty
  • Cannot execute any node commands (browser, file, system, exec)
  • Downgrading gateway to 5.12 immediately fixes the issue

Tests performed:

  1. Fresh Docker container with empty data dir — Caps blank
  2. Fresh container with last-good config — Caps blank
  3. Multiple gateway versions (5.18 through 5.25_beta1) — all blank
  4. Multiple node versions (5.12, 5.20, 5.22) — all blank with 5.18+ gateway
  5. WebSocket frame analysis: node response lacks caps/commands fields

Regression point: 5.12 gateway works perfectly; 5.18+ breaks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingclawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions