Fix Remote Browser Automation with OpenClaw Node Setup

If you've been struggling with browser automation on a remote VPS—CDP port issues, headless screenshots, profile management—there's a simpler approach: run OpenClaw as a node on your personal machine, not as a gateway. The gateway VPS handles LLM processing and agent orchestration; your local node runs the actual browser.
Setup
On your local computer, install OpenClaw normally but don't set it as gateway. Configure headless mode off and a dedicated profile:
openclaw config set browser.headless false --json openclaw config set browser.defaultProfile "openclaw"
Restart OpenClaw locally. The browser now pops up as a visible window—no more waiting for screenshots to see what the agent is doing.
Routing Tasks
Once the node is registered with your gateway, dispatch tasks in two ways:
- Dedicated agent — assign it to run exclusively on your local node.
- Slash command — from any channel use
/exec host=node node=<node_id_or_name> <your instruction>to send specific instructions to your local browser.
The agent runs under your home IP, uses your existing logins and cookies, and you can even take over manual control when needed. RAM sits under 50MB idle; CPU spikes only during tasks.
Why This Works
No CDP tunneling, no RDP, no port forwarding. The gateway orchestrates; the local node executes. It solves the common complaints about remote browser control—visibility, session persistence, and IP reputation.
📖 Read the full source: r/openclaw
👀 See Also

OpenClaw: Your Ultimate Quick Reference Cheatsheet
Dive into the nitty-gritty of OpenClaw with our handy reference cheatsheet. Extract critical features and functionalities to streamline your AI coding experience.

Evaluating Agent Skill Safety: Key Considerations Before Installation
Installing new agent skills can enhance functionality but also comes with risks. Learn how to evaluate the safety of these skills to protect your system.

Building a Fully Local Multi-Agent Assistant with OpenClaw and Ollama
A developer shares their stack for a fully local personal AI assistant using OpenClaw and Ollama, including models qwen3.5:35b-a3b, gemma3:4b, mistral:7b, MCP servers for Home Assistant and Gmail, and a Telegram Bot interface.

Building API endpoints with Claude: Practical prompt engineering lessons from a 70+ endpoint project
A developer built 70+ LinkedIn automation API endpoints with Claude writing 80% of the code, discovering that treating prompts like contracts with explicit constraints works better than natural language instructions for action-taking agents.