#7807: Browser Relay: start server when launched via CLI
docs
cli
stale
Cluster:
Browser Enhancements and Fixes
Summary:
- When the Browser Relay is launched from the CLI, it now starts the relay server automatically (same behavior as the UI flow).
- This ensures the extension/browser can connect immediately without requiring a separate manual start step.
Notes:
- Behavior aligns with the existing Browser Relay flow.
- Implemented autonomously by the OpenClaw assistant to streamline the CLI UX.
- CC: @MajesteitBart
Most Similar PRs
#21314: feat: enhance browser relay with custom naming and diagnostic tools
by kelvinCB · 2026-02-19
62.3%
#21277: fix(browser): dedupe concurrent relay init and await shared startup...
by HOYALIM · 2026-02-19
60.3%
#23363: Browser: fallback to managed profile and improve runtime diagnostics
by isdoho · 2026-02-22
58.9%
#6193: fix(browser): default to openclaw profile instead of chrome extensi...
by mikezaoldyeck · 2026-02-01
55.1%
#14944: fix(browser): prefer openclaw profile in headless/noSandbox environ...
by BenediktSchackenberg · 2026-02-12
54.5%
#10390: fix(chrome-relay): sticky attach + auto-restore after disconnects
by Mokoby · 2026-02-06
54.2%
#7157: docs(browser): recommend openclaw managed profile as default
by AkashaBot · 2026-02-02
53.5%
#11692: feat: add standalone browser CLI for Linux users
by shipitirl · 2026-02-08
53.5%
#16743: fix: auto-reattach browser relay debugger after navigation
by jg-noncelogic · 2026-02-15
53.2%
#13568: Fix browser (OpenClaw-managed) launch fail by binding remote debugg...
by singlag · 2026-02-10
53.2%