What You'll Build

A spare Windows PC (or laptop collecting dust) that your AI agent controls remotely. It runs multiple Chrome browsers simultaneously, each logged into different accounts. Your agent can:

All through natural language. Tell your agent "check my LinkedIn DMs for positive replies" and it does the rest.

Why It Works

Most "browser automation" tools use headless browsers or API wrappers that get flagged instantly. This approach is different:

Real result: One user runs 4 parallel Chrome profiles handling Twitter, LinkedIn, Facebook, and general web scraping, all controlled by a single OpenClaw agent running on a $200 VPS.

Prerequisites

Step 1: Install the OpenClaw App on Windows

Download the OpenClaw desktop app from openclaw.ai and install it on the Windows PC.

This app runs as a "node," a lightweight bridge between your main OpenClaw gateway and the Windows machine. It doesn't run an AI model. It just receives commands and executes them locally.

Open the app. It will show a pairing screen with a code.

Step 2: Pair It With Your Gateway

On your main OpenClaw machine (wherever your gateway runs), approve the new node:

openclaw devices list
openclaw devices approve <the-request-id-shown>

That's it. Your gateway can now send commands to the Windows PC. You can verify with:

openclaw nodes list

You should see your Windows machine listed with a green status.

Step 3: Launch Chrome With Remote Debugging

This is the key step. You need to start Chrome in a way that lets OpenClaw control it. Open PowerShell on the Windows PC and run:

$chrome = 'C:\Program Files\Google\Chrome\Application\chrome.exe'

Start-Process $chrome -ArgumentList `
  "--remote-debugging-port=18800",
  "--user-data-dir=$env:USERPROFILE\.openclaw\browser-profiles\main"

A Chrome window opens. This is your first automation profile.

What just happened:

Step 4: Log Into Your Accounts (One Time)

In that Chrome window, manually log into whatever you need: Gmail, LinkedIn, Twitter, your CRM, your bank dashboard, whatever.

This is a one-time setup. The agent will reuse these sessions going forward. As long as Chrome stays open, the sessions persist.

Step 5: Test It

From your main machine (or Telegram, Signal, wherever you talk to your agent), try:

"Take a screenshot of my Chrome browser on the Windows PC"

Your agent will use the browser tool, connect to the Windows node, snap a screenshot, and send it back. If you see the page you left open, everything is working.

Try something more useful:

"Go to linkedin.com/messaging and tell me if I have any unread messages"

The agent navigates, reads the page, and reports back. No API keys. No LinkedIn developer account. Just a real browser.

Step 6: Add More Profiles (Parallel Automation)

Here's where it gets powerful. Launch more Chrome instances on different ports:

$chrome = 'C:\Program Files\Google\Chrome\Application\chrome.exe'

# Profile 2: Twitter/X automation
Start-Process $chrome -ArgumentList `
  "--remote-debugging-port=18801",
  "--user-data-dir=$env:USERPROFILE\.openclaw\browser-profiles\twitter"

# Profile 3: LinkedIn automation
Start-Process $chrome -ArgumentList `
  "--remote-debugging-port=18802",
  "--user-data-dir=$env:USERPROFILE\.openclaw\browser-profiles\linkedin"

# Profile 4: Facebook automation
Start-Process $chrome -ArgumentList `
  "--remote-debugging-port=18803",
  "--user-data-dir=$env:USERPROFILE\.openclaw\browser-profiles\facebook"

Log into the relevant accounts in each window. Now your agent can work across all four simultaneously. Twitter posting on port 18801 doesn't interfere with LinkedIn scraping on 18802.

You can run up to 100 profiles (ports 18800-18899). Most machines handle 4-8 comfortably.

Step 7: Automate With Cron Jobs

Set up recurring tasks that run on autopilot:

Morning LinkedIn check (every day at 9 AM): Your agent opens LinkedIn on the dedicated profile, checks DMs for positive replies to your outbound messages, and sends you a summary on Telegram.

Social posting (3x per day): Your agent posts to Twitter, LinkedIn, and Facebook using three separate Chrome profiles in parallel. Each post is tailored to the platform. No scheduling tool needed.

Competitor price monitoring (daily): Your agent visits 5 competitor websites, screenshots their pricing pages, and flags any changes.

Lead scraping (weekly): Your agent searches Google Maps or industry directories for prospects, extracts contact info, and adds them to your CRM.

What People Are Actually Building

From the OpenClaw community:

Making It Persistent

Chrome profiles survive restarts (the user-data-dir keeps everything). But you need to re-launch Chrome with the debugging flags after a reboot.

Auto-start on boot (PowerShell script):

Create a file called start-browsers.ps1:

$chrome = 'C:\Program Files\Google\Chrome\Application\chrome.exe'
$profiles = @(
    @{Port=18800; Name="main"},
    @{Port=18801; Name="twitter"},
    @{Port=18802; Name="linkedin"},
    @{Port=18803; Name="facebook"}
)

foreach ($p in $profiles) {
    $dataDir = "$env:USERPROFILE\.openclaw\browser-profiles\$($p.Name)"
    Start-Process $chrome -ArgumentList `
      "--remote-debugging-port=$($p.Port)",
      "--user-data-dir=$dataDir"
    Start-Sleep -Seconds 2
}

Add it to Windows Task Scheduler to run at login, and your automation machine survives reboots.

Gotchas and Tips