OpenClaw

browser-control

Remote browser access for login, 2FA, captcha, and manual verification. Protected by Google OAuth - only the configured email can access. Use when you need the user to log into a website, complete 2FA/MFA, solve a captcha, or do any manual browser action.

felipegoulu0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install felipegoulu/browser-control

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Browser Control

Remote browser access for login, 2FA, captcha, and manual verification. Protected by Google OAuth - the user must login with their Google account.

Installation (First Time Only)

Before using this skill, run the installer to configure ngrok and Google OAuth:

bash ~/.openclaw/skills/browser-control/install.sh

The installer will:

Install dependencies (VNC, noVNC, ngrok)
Ask for your ngrok authtoken (get it from https://dashboard.ngrok.com/get-started/your-authtoken)
Verify your Google account (only this email will be able to access the browser)

This only needs to be done once per machine.

When to use

When you need the user to:

Log into a website
Complete 2FA / MFA
Solve a captcha
Do any manual browser action

Check if running

~/.openclaw/skills/browser-control/status.sh

Returns JSON with status of VNC, noVNC, and ngrok tunnel.

Start if not running

~/.openclaw/skills/browser-control/start-tunnel.sh

Starts VNC + noVNC + ngrok tunnel with Google OAuth. Takes ~30 seconds.

Get URL

⚠️ ALWAYS read this file fresh before sending the URL to the user. Never use cached values.

cat ~/.openclaw/skills/browser-control/config.json

Returns:

{
  "novncUrl": "https://xxx.ngrok.app/vnc.html?password=xxx&autoconnect=true",
  "tunnelUrl": "https://xxx.ngrok.app",
  "allowedEmail": "user@gmail.com",
  "cdpUrl": "http://localhost:9222"
}

The URL changes every time the tunnel restarts. Always read the file, don't trust memory.

Workflow

Check status with status.sh
If not running, start with start-tunnel.sh
Read config.json NOW (not from memory!) for URL
Send user the link
User logs in with their Google account
User does the manual action (login, 2FA, etc.)
Wait for user to say "done"
Continue using browser via CDP (localhost:9222)

Important: The tunnel URL changes frequently. Always cat config.json right before...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/felipegoulu/browser-control
Version: —
Commit: ab9b44fdfb96f960f9aa166020007294ae040ea3
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Browser Control

Remote browser access for login, 2FA, captcha, and manual verification.
Protected by Google OAuth - the user must login with their Google account.

## Installation (First Time Only)

Before using this skill, run the installer to configure ngrok and Google OAuth:

```bash
bash ~/.openclaw/skills/browser-control/install.sh
```

The installer will:
1. Install dependencies (VNC, noVNC, ngrok)
2. Ask for your **ngrok authtoken** (get it from https://dashboard.ngrok.com/get-started/your-authtoken)
3. Verify your **Google account** (only this email will be able to access the browser)

This only needs to be done once per machine.

## When to use

When you need the user to:
- Log into a website
- Complete 2FA / MFA
- Solve a captcha
- Do any manual browser action

## Check if running

```bash
~/.openclaw/skills/browser-control/status.sh
```

Returns JSON with status of VNC, noVNC, and ngrok tunnel.

## Start if not running

```bash
~/.openclaw/skills/browser-control/start-tunnel.sh
```

Starts VNC + noVNC + ngrok tunnel with Google OAuth. Takes ~30 seconds.

## Get URL

**⚠️ ALWAYS read this file fresh before sending the URL to the user. Never use cached values.**

```bash
cat ~/.openclaw/skills/browser-control/config.json
```

Returns:
```json
{
"novncUrl": "https://xxx.ngrok.app/vnc.html?password=xxx&autoconnect=true",
"tunnelUrl": "https://xxx.ngrok.app",
"allowedEmail": "user@gmail.com",
"cdpUrl": "http://localhost:9222"
}
```

The URL changes every time the tunnel restarts. Always read the file, don't trust memory.

## Workflow

1. Check status with `status.sh`
2. If not running, start with `start-tunnel.sh`
3. **Read `config.json` NOW** (not from memory!) for URL
4. Send user the link
5. User logs in with their Google account
6. User does the manual action (login, 2FA, etc.)
7. Wait for user to say "done"
8. Continue using browser via CDP (localhost:9222)

**Important:** The tunnel URL changes frequently. Always `cat config.json` right before...

搜索