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/pairing.md

View on GitHub
# Gateway Pairing Reference

> Source: https://docs.openclaw.ai/gateway/pairing

## Overview

Gateway-owned pairing controls which nodes (iOS, Android, macOS companion apps) can connect to the Gateway. Nodes must be explicitly approved before they can interact.

## Concepts

| Term | Meaning |
|---|---|
| **Pending request** | A node asked to join; requires approval |
| **Paired node** | Approved node with an issued auth token |
| **Transport** | Gateway WS endpoint forwards requests but does not decide membership |

## How Pairing Works

1. A node connects to the Gateway WS and requests pairing.
2. The Gateway stores a pending request and emits `node.pair.requested`.
3. You approve or reject the request (CLI or UI).
4. On approval, the Gateway issues a **new token** (tokens are rotated on re-pair).
5. The node reconnects using the token and is now "paired".

## CLI Workflow (Headless Friendly)

```bash
openclaw nodes pending                               # List pending requests
openclaw nodes approve <requestId>                   # Approve
openclaw nodes reject <requestId>                    # Reject
openclaw nodes status                                # Show all paired nodes
openclaw nodes rename --node <id|name|ip> --name "Living Room iPad"  # Rename
```

## API Surface (Gateway Protocol)

### Events
| Event | When |
|---|---|
| `node.pair.requested` | New pending request created |
| `node.pair.resolved` | Request approved/rejected/expired |

### RPC Methods
| Method | Purpose |
|---|---|
| `node.pair.request` | Create or reuse a pending request (idempotent per node) |
| `node.pair.list` | List pending + paired nodes |
| `node.pair.approve` | Approve pending request (issues token) |
| `node.pair.reject` | Reject pending request |
| `node.pair.verify` | Verify `{ nodeId, token }` |

### Important
- `node.pair.request` is idempotent: repeated calls return the same pending request.
- Approval always generates a **fresh** token; no token is ever returned from `node.pair.request`.
- Requests may include `silent: true` as a hint for auto-approval flows.

## Auto-Approval (macOS App)

The macOS app auto-approves when:
- The request is marked `silent`, AND
- The app can verify an SSH connection to the gateway host using the same user.

## Storage (Local, Private)

Located under `~/.openclaw/` (or `OPENCLAW_STATE_DIR`):

| File | Purpose |
|---|---|
| `~/.openclaw/nodes/paired.json` | Paired nodes with tokens (**sensitive**) |
| `~/.openclaw/nodes/pending.json` | Pending requests |

- **Tokens are secrets**: treat `paired.json` as sensitive.
- Rotating a token requires re-approval (or deleting the node entry).

## Transport Behavior

- Transport is **stateless**; it does not store membership.
- If the Gateway is offline or pairing is disabled, nodes cannot pair.
- If the Gateway is in remote mode, pairing happens against the remote Gateway's store.

## See Also

- [gateway_internals.md](gateway_internals.md) — Network model, lock, health
- [nodes.md](nodes.md) — iOS, Android, macOS companion apps
- [presence_discovery.md](presence_discovery.md) — Discovery mechanisms
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