Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Start a secure remote browser tunnel for manual user authentication (solving Captchas, 2FA, logins) and capture session data. Built for AI Commander.
Start a secure remote browser tunnel for manual user authentication (solving Captchas, 2FA, logins) and capture session data. Built for AI Commander.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill allows the agent to request the user to perform a manual login on a website and then capture the session cookies/localStorage for further automated work.
We take security seriously. Below is how we address common concerns related to remote browser control:
Always Sandboxed: Chromium runs with the system sandbox ENABLED. There is no option to disable it in the code. This prevents a malicious website from escaping the browser and executing code on your host. Isolation Recommendation: We recommend running this skill within an isolated container (Docker) or a dedicated VM for an extra layer of protection.
Referrer Policy: The server enforces Referrer-Policy: no-referrer. This ensures that even if you navigate to an untrusted site, your secret AUTH_TOKEN is NEVER sent in the HTTP Referer header. URL Cleansing: The interface automatically clears the token parameter from your browser's address bar immediately after the page loads.
Session Artifacts: The session.json file contains active login cookies. Treat it with the same level of security as a password. Mandatory Cleanup: Always delete the session file immediately after the agent finishes its task. No Persistence: This skill does not store credentials long-term or exfiltrate them to external servers.
Default Local Bind: By default, the server binds to 127.0.0.1. Secure Access: If you need remote access, do not bind to 0.0.0.0 directly. Instead, use a secure tunnel like Tailscale, Cloudflare Tunnel (cloudflared), or an SSH tunnel.
When a website requires manual interaction to solve Captcha or 2FA. When bot detection prevents automated login. When you want to authorize an agent without sharing your password.
Request Auth: Start the tunnel using scripts/auth_server.js. Provide Link: Share the link (including token) with the intended user over a secure channel. Wait for Session: The user logs in and clicks DONE in the web UI. Verify: Use scripts/verify_session.js to confirm the session is valid. Cleanup: Delete the session file once the task is complete.
AUTH_HOST=127.0.0.1 AUTH_TOKEN=mysecret node scripts/auth_server.js <port> <session_file>
node scripts/verify_session.js <session_file> <target_url> <expected_text>
Requires: express, socket.io, playwright-core, and a system chromium-browser.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.