OpenClaw and Tandem Browser Setup Guide

Before you start

• Use a machine you control. Browser agents can access logged-in sessions.
• Keep API keys in environment files or provider login flows, not in screenshots or shared notes.
• Install only skills, plugins, and browser builds from sources you trust.
• Start with one model and one browser profile. Add extra agents after the first setup is working.

Install OpenClaw on macOS

Open Terminal and run the recommended installer. It detects the operating system, installs the needed Node runtime if required, installs OpenClaw, and starts onboarding.

curl -fsSL https://openclaw.ai/install.sh | bash

If you want to install first and run onboarding later, use the no-onboard flag.

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard
openclaw onboard

After install, open a new terminal and verify the CLI and gateway.

openclaw --version
openclaw doctor
openclaw gateway status

Install OpenClaw on Windows

For most Windows desktop users, start with the native Windows Hub companion app from the OpenClaw Windows docs. It includes setup, tray status, chat, node mode, and local MCP mode.

If you prefer the CLI installer, open PowerShell as your normal user and run:

iwr -useb https://openclaw.ai/install.ps1 | iex

To install now and run onboarding later:

& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -NoOnboard
openclaw onboard

Then verify the install from a new PowerShell window.

openclaw --version
openclaw doctor
openclaw gateway status

Connect an LLM to OpenClaw

The easiest path is the onboarding wizard. It walks through model auth, workspace, gateway, channels, skills, and health.

openclaw onboard

Choose your preferred LLM provider during onboarding. If you already completed onboarding, use the model commands to review and change the model later.

openclaw models list
openclaw models set provider/model
openclaw models status

For a long-running gateway, put provider keys on the machine running OpenClaw. A common pattern is ~/.openclaw/.env, then restart the gateway and check health.

cat >> ~/.openclaw/.env <<'EOF'
PROVIDER_API_KEY=replace-with-your-key
EOF

openclaw gateway restart
openclaw models status
openclaw doctor

Do not copy the example key name blindly. Use the real environment variable expected by your chosen provider.

Install Tandem Browser on macOS

For Apple Silicon Macs, download the signed and notarized Tandem Browser DMG from the Tandem Browser releases page. Open the DMG, drag Tandem Browser into Applications, then launch it once.

Install Tandem Browser on Windows

On Windows 11 x64, download the Tandem Browser installer or portable build from the Tandem Browser releases page. Windows builds are available, but the project notes that Windows builds may be unsigned, so SmartScreen may show an unknown publisher warning.

After first launch, open Settings, then Connected Agents, and generate connection instructions for the machine where OpenClaw runs.

Build Tandem from source if needed

Use source setup only when you need development builds, Linux support, or a custom checkout. For normal browser use, the packaged app is simpler.

git clone https://github.com/hydro13/tandem-browser.git
cd tandem-browser
npm install
npm start

Connect Tandem to OpenClaw

Tandem exposes agent access through Connected Agents. The local Agent API usually uses port 8765, but Tandem can change it in settings and also writes local discovery files.

API_PORT="$(cat ~/.tandem/api-port 2>/dev/null || printf 8765)"
API="http://127.0.0.1:${API_PORT}"
TOKEN="$(cat ~/.tandem/api-token)"

curl -sS "$API/status"
curl -sS "$API/tabs/list" \
  -H "Authorization: Bearer $TOKEN"

If OpenClaw and Tandem are on different machines, use Tandem's On another machine flow and connect over a private Tailscale network. Do not expose the Tandem agent API to the public internet.

Add Tandem as an MCP tool surface

If your OpenClaw setup uses MCP clients or local MCP mode, add Tandem as an MCP server using the instructions generated inside Tandem. The source checkout example looks like this:

{
  "mcpServers": {
    "tandem": {
      "command": "node",
      "args": ["/path/to/tandem-browser/dist/mcp/server.js"]
    }
  }
}

For a packaged Tandem app, prefer the exact generated instructions from Tandem's Connected Agents screen. They are version-matched to the installed browser.

Make Tandem the primary OpenClaw browser

OpenClaw configuration supports browser executable paths. Set the global browser path to Tandem so browser launches go through Tandem by default, then validate the config.

On macOS, first confirm the real app executable path, then set it:

openclaw config set browser.executablePath \
  "/Applications/Tandem Browser.app/Contents/MacOS/Tandem Browser" \
  --dry-run

openclaw config set browser.executablePath \
  "/Applications/Tandem Browser.app/Contents/MacOS/Tandem Browser"

openclaw config validate

On Windows, use the actual installed path from your machine. The path depends on whether you used the installer or portable build.

openclaw config set browser.executablePath \
  "C:\\Path\\To\\Tandem Browser.exe" \
  --dry-run

openclaw config set browser.executablePath \
  "C:\\Path\\To\\Tandem Browser.exe"

openclaw config validate

If you use multiple browser profiles, set profile-specific paths instead of replacing the global path.

openclaw config set browser.profiles.work.executablePath \
  "/Applications/Tandem Browser.app/Contents/MacOS/Tandem Browser"

Use Tandem for all agent browser work

After Tandem is the configured browser, make the operating rule explicit in your OpenClaw agent instructions. Put a short rule in the agent workspace instructions or team runbook.

For browser tasks, use Tandem Browser first.
Open new web tasks in the Tandem workspace.
Use Tandem MCP or HTTP tools for tabs, page reading, clicking, typing, and network inspection.
Ask the human before using logged-in sessions for purchases, account changes, or irreversible actions.

This makes the browser choice clear for every agent run without depending on memory or repeated prompts.

Verify the full setup

• openclaw doctor passes or shows only issues you understand.
• openclaw models status confirms the selected LLM is available.
• Tandem opens and shows Settings, then Connected Agents.
• The local Tandem status endpoint responds.
• OpenClaw config validates after setting browser.executablePath.
• A test agent task opens a page in Tandem instead of another browser.
• The agent can list tabs or read page structure through Tandem MCP or HTTP.

Source links

• OpenClaw install docs
• OpenClaw model provider quickstart
• OpenClaw configuration docs
• Tandem Browser repository