← Back to Skills Marketplace
80
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install browser-local-chrome
Description
Configure and manage local Chrome in debug mode for browser automation with OpenClaw, enabling SSRF whitelist and browser status checks.
README (SKILL.md)
浏览器自动化配置技能
配置 OpenClaw 使用本地 Chrome 调试模式进行浏览器自动化。
功能
- ✅ 一键启动 Chrome 调试模式
- ✅ 自动配置 OpenClaw 浏览器设置
- ✅ 启用 SSRF 白名单（允许访问任意网站）
- ✅ 检查浏览器状态
使用方法
一键配置（推荐）
node scripts/setup.js
这会自动完成所有步骤：启动 Chrome → 配置 OpenClaw → 验证状态
分步配置
1. 启动浏览器
node scripts/start-chrome.js
2. 配置 OpenClaw
node scripts/configure-browser.js
3. 重启 Gateway
openclaw gateway restart
4. 检查状态
node scripts/check-status.js
5. 关闭浏览器（使用完成后）
node scripts/stop-chrome.js
配置说明
CDP 端口
默认：9222
用户数据目录
默认：C:\chrome-debug-profile
SSRF 策略
dangerouslyAllowPrivateNetwork: true- 允许访问任意网站- 如需更严格的安全策略，可改用
hostnameAllowlist
故障排查
Chrome 无法启动
- 检查 Chrome 是否已安装：
C:\Program Files\Google\Chrome\Application\chrome.exe - 检查端口 9222 是否被占用
浏览器工具不可用
- 确认 Gateway 已重启
- 检查 CDP 连接：
curl http://127.0.0.1:9222/json/version
SSRF 错误
- 确认
openclaw.json中已配置ssrfPolicy - 重启 Gateway 使配置生效
适用场景
- 访问需要 JavaScript 渲染的网站
- 自动化网页操作（点击、填写表单等）
- 截图和页面分析
- 绕过 curl 无法处理的动态内容
注意事项
- Chrome 调试模式需要保持运行
- 使用完成后请关闭浏览器：
node scripts/stop-chrome.js - 重启后需要重新启动 Chrome
- 建议将启动脚本添加到开机自启
Usage Guidance
This skill appears to be what it claims, but it will modify your OpenClaw config to enable 'dangerouslyAllowPrivateNetwork', giving the browser access to internal and private network addresses. Before installing/running: 1) Back up your OpenClaw config (~/.openclaw/openclaw.json or %USERPROFILE%\.openclaw\openclaw.json). 2) Review and confirm you accept enabling private-network SSRF access (consider using hostnameAllowlist instead). 3) Inspect the scripts (they invoke Chrome, call kill/taskkill/killall, and execute openclaw gateway restart instructions). 4) Run them in a trusted environment only and close the debug Chrome when finished. 5) Note cross-platform caveats: configure-browser.js uses USERPROFILE (Windows) and some default chrome paths may not match your system—adjust _meta.json or the scripts as needed.
Capability Analysis
Type: OpenClaw Skill
Name: browser-local-chrome
Version: 1.1.0
This skill bundle automates the configuration of a local Chrome instance for debugging but introduces significant security risks by intentionally disabling SSRF protections. Specifically, `scripts/configure-browser.js` modifies the global `openclaw.json` configuration to set `dangerouslyAllowPrivateNetwork: true`, which allows the agent to access internal network resources. Additionally, the bundle includes scripts like `scripts/start-chrome.js` and `scripts/stop-chrome.js` that perform system-level operations, such as executing shell commands to manage browser processes and modifying files in the user's home directory. While these actions are consistent with the stated purpose of browser automation, the intentional weakening of security boundaries and the use of broad process termination logic are high-risk behaviors.
Capability Assessment
Purpose & Capability
Name/description match the implemented actions: scripts start/stop Chrome in CDP mode, configure OpenClaw to attach to the local CDP port, and provide status/troubleshooting tools. There are no unrelated credentials, external downloads, or unexpected network endpoints.
Instruction Scope
SKILL.md and the scripts instruct the agent/user to read and overwrite the user's OpenClaw configuration file (~/.openclaw/openclaw.json or %USERPROFILE%\.openclaw\openclaw.json) and to restart the gateway. This is necessary for the stated goal but is a system-level config change; the scripts also execute system commands (launching Chrome, taskkill/killall) which is expected for start/stop behavior.
Install Mechanism
No remote install or downloads are defined; this is an instruction-and-script skill shipped with source files. Packaging scripts exist but use local system zip/archiver tools—no external code fetches or URL downloads were observed.
Credentials
The skill requests no credentials or env vars, but it directly reads/writes the user's OpenClaw configuration and uses process.env.USERPROFILE (Windows-centric). The most important concern is that configure-browser.js sets ssrfPolicy.dangerouslyAllowPrivateNetwork = true, which intentionally broadens SSRF access to private networks — this is functionally justified by the skill but is a high-impact, security-sensitive change that should be explicitly authorized by the user/administrator.
Persistence & Privilege
The skill is not always-enabled and does not request special platform privileges, but it does modify a system-level OpenClaw configuration file (global browser/ssrf settings). That modification persists until reverted and affects other OpenClaw browser behavior, so it carries system-wide impact even though it's coherent with the skill's purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install browser-local-chrome - After installation, invoke the skill by name or use
/browser-local-chrome - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
跨平台支持 + 故障排查工具 + 混合方案
Metadata
Frequently Asked Questions
What is Browser Local Chrome?
Configure and manage local Chrome in debug mode for browser automation with OpenClaw, enabling SSRF whitelist and browser status checks. It is an AI Agent Skill for Claude Code / OpenClaw, with 80 downloads so far.
How do I install Browser Local Chrome?
Run "/install browser-local-chrome" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Browser Local Chrome free?
Yes, Browser Local Chrome is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Browser Local Chrome support?
Browser Local Chrome is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Browser Local Chrome?
It is built and maintained by Like Liu (@liulike); the current version is v1.1.0.
More Skills