Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [v2026.3.24] Two regressions: browser tabs CLI syntax break + gateway cycling after doctor --fix [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#55563•Fetched 2026-04-08 01:37:58
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
OwlockOwlock
Participants
OwlockOwlock
Timeline (top)
cross-referenced ×1mentioned ×1subscribed ×1

Error Message

→ error: unknown option '--browser-profile' Impact: Every user following existing WSL2 + CDP documentation gets an error that looks like a config problem, not a CLI syntax change.

Root Cause

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.

Fix Action

Fixed

PR fix notes

PR #55567: fix(browser): restore browser tabs action syntax compatibility

Description (problem / solution / changelog)

Summary

  • restore support for the legacy syntax
  • keep the current syntax working unchanged
  • add focused CLI tests covering both action syntaxes and verify plain No tabs (browser closed or no targets). still lists tabs

Testing

  • pnpm test -- extensions/browser/src/cli/browser-cli-manage.test.ts extensions/browser/src/cli/browser-cli-manage.timeout-option.test.ts (fails in this environment because node_modules is missing)
  • pnpm install (fails in this environment due npm DNS/network error: EAI_AGAIN to registry.npmjs.org)

Closes #55563

Changed files

  • extensions/browser/src/cli/browser-cli-manage.test.ts (modified, +55/-0)
  • extensions/browser/src/cli/browser-cli-manage.ts (modified, +85/-36)

Code Example

systemctl --user stop openclaw-gateway
systemctl --user reset-failed openclaw-gateway
openclaw gateway install --force
systemctl --user start openclaw-gateway
RAW_BUFFERClick to expand / collapse

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

  • PR #39407 — WSL2 + Windows remote Chrome CDP troubleshooting guide (affected by Regression 1)
  • Issue #54669 — Chrome 136+ IPv6 binding fix (same setup)

extent analysis

Fix Plan

To address the regressions, follow these steps:

Regression 1 — browser tabs CLI syntax change

  1. Update documentation: Modify the troubleshooting guide in PR #39407 to reflect the new syntax.
  2. Use new syntax: Replace openclaw browser tabs --browser-profile remote with openclaw browser --browser-profile remote tabs in all relevant documentation and user guides.

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

  1. Stop and reset gateway service:

systemctl --user stop openclaw-gateway systemctl --user reset-failed openclaw-gateway

2. **Reinstall gateway**:
   ```bash
openclaw gateway install --force
  1. Start gateway service:

systemctl --user start openclaw-gateway

4. **Update systemd service unit**: Modify the service unit to use a stable Node path instead of the nvm-managed path.

### Verification
- Verify that the `openclaw browser --browser-profile remote tabs` command works as expected.
- Check that the gateway service is running and stable after applying the manual fix.

### Extra Tips
- Ensure that all documentation and user guides are updated to reflect the new CLI syntax.
- Consider adding a check to the `openclaw doctor` command to detect and fix the unstable Node path issue in the systemd service unit.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#embedding generation#cache error#pipeline error#runtime error#dependency conflict

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING