OpenClaw浏览器自动化配置

配置OpenClaw连接远程Chrome/CDP浏览器，实现无头浏览器自动化操作与管理。

Security Scan

The skill's instructions and requirements match its stated purpose (configuring OpenClaw to connect to a remote Chrome/CDP browser); nothing requested or instructed is out of scope or unexpectedly privileged.

Purpose & Capability

Name/description (connect OpenClaw to remote Chrome/CDP) align with the SKILL.md steps: run a headless Chrome container, verify CDP, add a browser profile to ~/.openclaw/openclaw.json, restart the OpenClaw gateway, and verify status. No unrelated credentials or tools are required.

Instruction Scope

Runtime instructions are limited to launching a Docker headless-shell, checking the CDP endpoint, editing OpenClaw config under the user's home (~/.openclaw/), restarting the user openclaw-gateway service, and running openclaw status — all are directly relevant to setting up remote browser automation. The optional browserless example includes an API token placeholder (expected). Instructions do not request unrelated files, system-wide secrets, or external exfiltration.

Install Mechanism

This is instruction-only (no install spec / no code). It suggests docker run chromedp/headless-shell:latest which will pull from Docker Hub — expected but you may want to pin an explicit image tag rather than using :latest to avoid unexpected image changes.

Credentials

The skill declares no environment variables or credentials. The only credential-like item is an optional browserless API key shown as a token in the cdpUrl, which is appropriate for that integration. No unrelated secrets or broad credentials are requested.

Persistence & Privilege

The skill does not request permanent/always-on privileges and does not modify other skills or system-wide settings beyond the user's OpenClaw config and restarting the per-user openclaw-gateway service — actions consistent with its purpose.

Assessment

This instruction-only skill appears coherent, but consider these practical cautions before applying it: (1) The Docker example uses the :latest tag — pin to a specific, trusted image digest or tag to avoid unexpected updates. (2) Running a CDP endpoint (port 9222) can expose browser control to the network — ensure it's bound to localhost or protected by a firewall and do not expose it publicly. (3) If you use browserless with a token, avoid embedding the token in source-controlled files or public URLs (the example places the token in the cdpUrl which may be logged); store secrets securely. (4) Restarting the user systemd service requires appropriate user permissions; verify the openclaw binary/service is the expected upstream. (5) Only pull container images from trusted sources and verify image provenance. If you want higher assurance, request a signed/verified install spec or a pinned Docker image reference from the skill author.

配置OpenClaw连接远程Chrome/CDP浏览器进行自动化操作。

适用场景

• 连接远程服务器的Chrome浏览器
• 使用Docker容器运行的无头浏览器
• 连接browserless.io云服务

配置步骤

1. 启动CDP浏览器容器

推荐使用 chromedp/headless-shell（轻量且保持会话）：

docker run -d --name browser-auto -p 9222:9222 --shm-size=512m chromedp/headless-shell:latest

验证CDP可用：

curl http://127.0.0.1:9222/json/version

2. 配置OpenClaw

在 ~/.openclaw/openclaw.json 中添加browser配置：

{
  "browser": {
    "enabled": true,
    "defaultProfile": "remote-chrome",
    "attachOnly": true,
    "profiles": {
      "remote-chrome": {
        "cdpUrl": "http://127.0.0.1:9222",
        "color": "#00AA00"
      }
    }
  }
}

3. 重启Gateway

systemctl --user restart openclaw-gateway

4. 验证

openclaw browser status

关键配置项

配置项	说明
browser.enabled	启用浏览器
browser.defaultProfile	默认使用的浏览器配置名
browser.attachOnly	true=不尝试启动本地浏览器，只连接远程
profiles.<name>.cdpUrl	远程CDP地址

云服务方案

Browserless.io（付费）

{
  "browser": {
    "defaultProfile": "browserless",
    "profiles": {
      "browserless": {
        "cdpUrl": "https://production-sfo.browserless.io?token=<API_KEY>"
      }
    }
  }
}

常见问题

1. 端口被占用 - 设置 attachOnly: true
2. 标签页丢失 - 使用 chromedp/headless-shell 而非 browserless/chrome
3. 环境变量不生效 - 需要修改systemd服务配置