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
How to avoid unexpected OpenRouter costs in OpenClaw automation
A developer team accidentally spent $750 in 3 days on OpenRouter by defaulting to Claude Sonnet 4.6 ($3/M tokens) across all automation tasks. They reduced costs by 97% by changing default models, locking cron jobs and subagents to cheaper options, and reserving expensive models only for sensitive work.
Splitting Agent Context into Three Layers to Solve the 700-Line Monolith Problem
A team building a 6-agent autonomous system solved context file bloat by separating agent context into three layers based on concern type and change frequency: CLAUDE.md for identity, BRIEFING.md for mission, and PLAYBOOK.md for operations. This approach prevents silent failures from argument limits and makes editing predictable.
Running a 1 Trillion Parameter LLM Locally on AMD Ryzen AI Max+ Cluster
AMD demonstrates running the Kimi K2.5 open-source model (375GB, 1 trillion parameters) across four Framework Desktop systems with Ryzen AI Max+ 395 processors using llama.cpp RPC. The guide covers TTM kernel modifications for 120GB VRAM per node and provides two setup options: Lemonade SDK pre-built binaries or manual ROCm 7.0.2 installation.
Creating Custom Skills for Claude Co-Work: Best Practices and Formats
Explore best practices for creating custom skills for Claude Co-Work with specific formatting tips and implementation advice from user-experienced insights.