docs(browser-control): document OPENCLAW_EAGER_BROWSER_CONTROL_SERVER… · openclaw/openclaw@a823cc3
liuhao1024
·
2026-06-14
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -13,7 +13,12 @@ CLI, and scripting patterns (snapshots, refs, waits, debug flows).
|
13 | 13 | |
14 | 14 | ## Control API (optional) |
15 | 15 | |
16 | | -For local integrations only, the Gateway exposes a small loopback HTTP API: |
| 16 | +For local integrations only, the Gateway exposes a small loopback HTTP API. |
| 17 | +This standalone server is opt-in — set the environment variable |
| 18 | +`OPENCLAW_EAGER_BROWSER_CONTROL_SERVER=1` in the gateway service environment |
| 19 | +and restart the gateway before the HTTP endpoints become available. Without |
| 20 | +this variable the browser control runtime still works through the CLI and |
| 21 | +agent tools, but nothing listens on the loopback control port. |
17 | 22 | |
18 | 23 | - Status/start/stop: `GET /`, `POST /start`, `POST /stop` |
19 | 24 | - Tabs: `GET /tabs`, `POST /tabs/open`, `POST /tabs/focus`, `DELETE /tabs/:targetId` |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
