Skip to content

LeoYeAI/agent-master-skills / skills/bengii-gemini-fix

openclaw

Flagged

Comprehensive guide for installing, configuring, operating, and troubleshooting OpenClaw — a self-hosted, multi-channel AI agent gateway. Use when the user asks about OpenClaw setup, configuration, channel management (WhatsApp/Telegram/Discord/Slack/iMessage/etc.), model provider setup, Gateway operations, multi-agent routing, security hardening, troubleshooting, or any maintenance task related to their local OpenClaw installation. Also use when encountering errors from `openclaw` CLI commands or the Gateway daemon.

FileKindSize
README.mdmarkdown7.5 KB
README_CN.mdmarkdown7.3 KB
SKILL.mdskill md18.7 KB
_meta.jsonconfig286 B
references/acp_agents.mdmarkdown12.6 KB
references/agent_runtime.mdmarkdown5.6 KB
references/architecture.mdmarkdown3.8 KB
references/automation.mdmarkdown5.8 KB
references/bonjour.mdmarkdown3.3 KB
references/browser.mdmarkdown8.5 KB
references/channel_routing.mdmarkdown4.0 KB
references/channel_troubleshooting.mdmarkdown11.6 KB
references/channels.mdmarkdown6.2 KB
references/clawhub.mdmarkdown3.6 KB
references/config_reference.mdmarkdown11.2 KB
references/diffs_firecrawl.mdmarkdown3.3 KB
references/elevated.mdmarkdown2.8 KB
references/exec.mdmarkdown6.5 KB
references/exec_approvals.mdmarkdown3.1 KB
references/gateway_internals.mdmarkdown7.7 KB
references/gateway_ops.mdmarkdown9.6 KB
references/heartbeat.mdmarkdown4.9 KB
references/hooks.mdmarkdown14.6 KB
references/install.mdmarkdown4.1 KB
references/llm_task.mdmarkdown2.6 KB
references/lobster.mdmarkdown7.8 KB
references/media.mdmarkdown4.2 KB
references/memory.mdmarkdown11.9 KB
references/model_failover.mdmarkdown3.1 KB
references/multi_agent.mdmarkdown4.4 KB
references/nodes.mdmarkdown8.8 KB
references/openprose.mdmarkdown2.6 KB
references/pairing.mdmarkdown3.1 KB
references/pdf_tool.mdmarkdown3.5 KB
references/platforms.mdmarkdown2.7 KB
references/plugins.mdmarkdown6.9 KB
references/polls.mdmarkdown2.2 KB
references/presence_discovery.mdmarkdown2.2 KB
references/providers.mdmarkdown6.0 KB
references/queue.mdmarkdown2.1 KB
references/remote_access.mdmarkdown4.7 KB
references/sandboxing.mdmarkdown5.6 KB
references/secrets.mdmarkdown5.4 KB
references/security.mdmarkdown24.5 KB
references/sessions.mdmarkdown8.9 KB
references/skills.mdmarkdown4.4 KB
references/slash_commands.mdmarkdown5.1 KB
references/streaming.mdmarkdown1.8 KB
references/subagents.mdmarkdown12.3 KB
references/thinking.mdmarkdown2.8 KB
references/tools.mdmarkdown13.3 KB
references/tui.mdmarkdown4.0 KB
references/voice.mdmarkdown2.7 KB
references/web_tools.mdmarkdown2.7 KB
references/web_ui.mdmarkdown4.5 KB

references/remote_access.md

View on GitHub
# Remote Access Reference

Remote access patterns for OpenClaw: SSH tunnels, VPNs, and Tailscale.

## The Core Idea

OpenClaw's Gateway binds to loopback by default. To access it from another machine, you need either a tunnel (SSH), a VPN/tailnet (Tailscale), or explicit network binding.

## Common VPN/Tailnet Setups

### 1) Always-On Gateway in Your Tailnet (VPS or Home Server)

The Gateway runs on a VPS or home server joined to your Tailscale tailnet. Access from any device on the tailnet.

### 2) Home Desktop Runs the Gateway, Laptop is Remote Control

Desktop runs the Gateway. Laptop connects via Tailscale or SSH tunnel.

### 3) Laptop Runs the Gateway, Remote Access from Other Machines

Laptop runs the Gateway. Access from other machines via tunnel or tailnet.

## Command Flow (What Runs Where)

- **Gateway host**: Runs the Gateway daemon, serves channels, tools, and sessions.
- **Remote client**: Runs CLI commands or the Control UI, connecting to the Gateway via WebSocket.

## SSH Tunnel (CLI + Tools)

```bash
# Forward the Gateway port to your local machine
ssh -N -L 18789:127.0.0.1:18789 user@host
```

Then access the Gateway at `http://127.0.0.1:18789` locally.

## CLI Remote Defaults

```bash
# Set remote Gateway URL for CLI
export OPENCLAW_GATEWAY_URL=ws://host:18789
export OPENCLAW_GATEWAY_TOKEN=your-token
```

## Credential Precedence

1. CLI `--gateway-url` / `--gateway-token` flags
2. Environment variables (`OPENCLAW_GATEWAY_URL`, `OPENCLAW_GATEWAY_TOKEN`)
3. Config file `gateway.url` / `gateway.auth.token`

## Chat UI over SSH

Access the Control UI via SSH tunnel for the web dashboard.

## macOS App "Remote over SSH"

The macOS OpenClaw app supports remote SSH connections for accessing a Gateway on another machine.

## Security Rules (Remote/VPN)

- Always use auth (`gateway.auth.token` or `gateway.auth.password`) when exposing non-loopback.
- Prefer Tailscale or VPN over SSH port forwarding.
- Never expose the Gateway to the public internet without auth.

---

# Tailscale (Gateway Dashboard)

Tailscale provides zero-config VPN access to your OpenClaw Gateway.

## Modes

- **Tailnet-only (Serve)**: Expose the Gateway to your Tailscale tailnet only.
- **Tailnet-only (bind to Tailnet IP)**: Bind the Gateway to your Tailscale IP.
- **Public internet (Funnel)**: Expose the Gateway to the public internet via Tailscale Funnel.

## Auth

- Tailscale provides identity headers for authentication.
- See `gateway.auth.tailscaleIdentityHeaders` for config.

## Config Examples

### Tailnet-Only (Serve)

Use `tailscale serve` to expose the Gateway to your tailnet:

```bash
tailscale serve --bg https://127.0.0.1:18789
```

### Tailnet-Only (Bind to Tailnet IP)

```json5
{
  gateway: {
    bind: "tailnet",
    auth: {
      mode: "token",
      token: "your-token",
    },
  },
}
```

### Public Internet (Funnel + Shared Password)

```json5
{
  gateway: {
    bind: "tailnet",
    auth: {
      mode: "password",
      password: "your-password",
    },
  },
}
```

Then:

```bash
tailscale funnel --bg https://127.0.0.1:18789
```

## CLI Examples

```bash
openclaw gateway --bind tailnet
openclaw gateway --bind auto
```

## Notes

- Tailscale Serve/Funnel requires Tailscale v1.50+.
- Funnel traffic is end-to-end encrypted.
- Use `gateway.auth` with Tailscale for an additional security layer.

## Browser Control (Remote Gateway + Local Browser)

When the Gateway is remote but you want browser control on the local machine, use node browser proxy or set up a remote CDP endpoint.

## Tailscale Prerequisites + Limits

- Tailscale must be installed and logged in on both the Gateway host and client.
- Tailscale free tier supports up to 100 devices.

---

# Web (Gateway Surfaces)

The Gateway serves a web dashboard (Control UI) and supports WebChat and webhooks.

## Control UI

Default: `http://127.0.0.1:18789/`

Features:
- Chat interface (WebChat)
- Configuration editor
- Session management
- Skills management
- Plugin management

## Webhooks

External systems can send messages to the Gateway via webhooks.

## Config (Default-On)

```json5
{
  web: {
    enabled: true,    // default: true
  },
}
```

## Tailscale Access

### Integrated Serve (Recommended)

```bash
tailscale serve --bg https://127.0.0.1:18789
```

### Tailnet Bind + Token

```json5
{
  gateway: {
    bind: "tailnet",
    auth: { mode: "token", token: "your-token" },
  },
}
```

### Public Internet (Funnel)

```bash
tailscale funnel --bg https://127.0.0.1:18789
```

## Security Notes

- The Control UI has full access to the Gateway (config, sessions, tools).
- Always use auth when exposing non-loopback.
- HTTPS is recommended for non-local access.

## Building the UI

The Control UI is built into the Gateway and served at the root URL. No separate build step is needed.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall