Skip to content

[v2026.3.24] Two regressions: browser tabs CLI syntax break + gateway cycling after doctor --fix #55563

Description

@Owlock

OpenClaw version: 2026.3.24 (cff6dc9)
OS: Windows 10 + WSL2
Reported by: @Owlock (contributor, PR #39407 merged, issue #54669)


Regression 1 — browser tabs CLI syntax changed without changelog entry

Before (v2026.3.13):
openclaw browser tabs --browser-profile remote
→ worked correctly ✅

After (v2026.3.24):
openclaw browser tabs --browser-profile remote
→ error: unknown option '--browser-profile'

Working syntax in v2026.3.24:
openclaw browser --browser-profile remote tabs

This is a silent breaking change. The troubleshooting guide in PR #39407 uses the old syntax and will now fail for users on v2026.3.24. No mention of this change appears in the changelog or migration notes.

Impact: Every user following existing WSL2 + CDP documentation gets an error that looks like a config problem, not a CLI syntax change.


Regression 2 — Gateway cycling loop after openclaw doctor --fix

After running openclaw doctor --fix, the gateway enters a silent cycling loop:
◇ Gateway ── Gateway not running.
Restarted systemd service: openclaw-gateway.service
◇ Gateway ── Gateway not running.
└ Doctor complete.

The doctor reports the gateway as "not running" both before and after its own restart attempt, then exits without resolving it. The gateway was actually failing to start due to the systemd service unit pointing to a nvm-managed Node path.

Manual fix required:

systemctl --user stop openclaw-gateway
systemctl --user reset-failed openclaw-gateway
openclaw gateway install --force
systemctl --user start openclaw-gateway

After this the gateway starts correctly with active (running).

Root cause: The service unit uses the nvm Node path which can be unstable. Doctor does not detect or fix this — it just restarts the broken unit.


Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm 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.impact:crash-loopCrash, hang, restart loop, or process-level availability failure.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions