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
Building 9 Claude Skills for Solo Studio: Stacking Instructions for Real Work
A solo developer built nine Claude skills for video production, analytics, SEO, financial modeling, and more. Key insight: write skills as instructions to an experienced colleague, not as documentation. Skills auto-trigger and stack when tasks overlap.
Maximizing AI Agent Capabilities in OpenClaw
OpenClaw's AI can be optimized by selecting the right model and providing specific system context. The Qwen models excel in tool use, critical for autonomous workflows.
Optimizing GLM-4.7-Flash on M4 Mac Mini with 24GB RAM
A developer shares specific configuration details for running GLM-4.7-Flash on an M4 Mac Mini with 24GB RAM, including Q3_K_XL quantization, 32k context size with MLA, and memory allocation realities for Metal.
Using the Dispatcher Pattern to Reduce Claude API Costs by 95%
A developer reduced their Claude API costs from $800-$2,000/month to about $215/month by implementing a dispatcher pattern that delegates heavy work to Claude Code CLI on a Claude Max subscription, while using minimal API tokens for orchestration.