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
Claude for Motion Graphics: Prompt Patterns That Produce Animated HTML Visuals You Can Capture as Video
A r/ClaudeAI user shares a reliable prompt structure for generating animated motion graphics and interactive charts as HTML widgets from Claude, then capturing them as MP4 with Playwright + ffmpeg.
How to Import Your ChatGPT History Into Claude Using Projects
Export ChatGPT chats as Markdown files and load the relevant ones into Claude Projects to carry over years of context, ongoing projects, and style preferences.
How OpenCLAW Memory Actually Works: Fixing Agent 'Forgetting'
OpenCLAW agents don't have persistent memory between conversations - they reconstruct context from files like SOUL.md, USER.md, and MEMORY.md each session. Common 'forgetting' issues stem from session bloat, unstructured memory files, and confusing chat history with permanent storage.
Upgrading an NVMe Raspberry Pi 5 to OpenClaw 9.3 Using a Staged Clone
A developer upgraded a production NVMe Raspberry Pi 5 from OpenClaw 2026v7.1-2 to 9.3 by cloning to a spare Pi, wiping the original, and restoring — with the agent SSHing in to do the work.