Virtual Desktop — Universal Browser Execution

Full Computer Use for OpenClaw via kasmweb/chrome Docker sidecar. Navigate any website, click, type, fill forms, extract data, upload files, screenshot on an...

This skill appears to be internally consistent with its stated purpose, but it materially increases the risk that an agent (or an attacker who controls the agent) can act as logged-in users and access arbitrary sites using persisted sessions. Before installing: - Do not run on a production or multi-tenant host; deploy in an isolated VM/VPS or sandbox. - Review and set a strong VNC_PW in .env before starting; avoid the default 'CHANGE_ME_NOW'. - Avoid exposing ports 6901 (noVNC) and 9222 (Chrome CDP) to the public internet; restrict access via firewall/VPC or use SSH/VPN tunneling. - Understand optional API keys: CAPSOLVER (paid CAPTCHA solver) and BROWSERBASE (residential proxy) can enable bypassing anti-bot protections—only add them if you trust the provider and need the capability. - Confirm how Telegram notifications are delivered; if you do not want Telegram notifications, remove TELEGRAM_BOT_TOKEN and verify behavior. - Audit browser_control.py and SKILL.md yourself (or have a developer review) for any hardcoded endpoints or unexpected network calls; the code does call api.capsolver.com and api.anthropic.com as advertised. - If you must use it, limit the agent's permissions, rotate or revoke sessions regularly, and consider making browser profiles ephemeral instead of permanent to reduce long-term exposure.

Type: OpenClaw Skill Name: virtual-desktop Version: 1.0.7 The 'virtual-desktop' skill bundle provides extensive browser automation capabilities by deploying a kasmweb/chrome Docker sidecar. It performs high-risk setup actions, including programmatically modifying the host's docker-compose.yml and .env files, opening port 6901 for remote VNC access, and using docker exec to install dependencies. While these actions are aligned with the stated goal of enabling 'Computer Use' for the agent, the broad permissions, modification of system-level configurations, and exposure of a remote desktop port constitute a significant security risk. No clear evidence of intentional malice was found, and the documentation includes appropriate security warnings regarding the VNC password and firewalling.