title: "Pairing"

---

“Pairing” is OpenClaw’s explicit access approval step.

"Pairing" is OpenClaw's explicit access approval step.

It is used in two places:

1. **DM pairing** (who is allowed to talk to the bot)

- Runs entirely in-process via `zca-js`.

- Uses native event listeners to receive inbound messages.

- Sends replies directly through the JS API (text/media/link).

- Designed for “personal account” use cases where Zalo Bot API is not available.

- Designed for "personal account" use cases where Zalo Bot API is not available.

## Naming

# `openclaw directory`

Directory lookups for channels that support it (contacts/peers, groups, and “me”).

Directory lookups for channels that support it (contacts/peers, groups, and "me").

## Common flags

## macOS: `launchctl` env overrides

If you previously ran `launchctl setenv OPENCLAW_GATEWAY_TOKEN ...` (or `...PASSWORD`), that value overrides your config file and can cause persistent “unauthorized” errors.

If you previously ran `launchctl setenv OPENCLAW_GATEWAY_TOKEN ...` (or `...PASSWORD`), that value overrides your config file and can cause persistent "unauthorized" errors.

```bash

launchctl getenv OPENCLAW_GATEWAY_TOKEN

Enable a specific hook by adding it to your config (`~/.openclaw/openclaw.json` by default).

**Note:** Workspace hooks are disabled by default until enabled here or in config. Hooks managed by plugins show `plugin:<id>` in `openclaw hooks list` and can’t be enabled/disabled here. Enable/disable the plugin instead.

**Note:** Workspace hooks are disabled by default until enabled here or in config. Hooks managed by plugins show `plugin:<id>` in `openclaw hooks list` and can't be enabled/disabled here. Enable/disable the plugin instead.

**Arguments:**

summary: "CLI reference for `openclaw memory` (status/index/search/promote/promote-explain/rem-harness)"

read_when:

- You want to index or search semantic memory

- You’re debugging memory availability or indexing

- You're debugging memory availability or indexing

- You want to promote recalled short-term memory into `MEMORY.md`

title: "Memory"

---

- Keep exec **sandboxed** on the gateway, but delegate approved runs to other hosts.

- Provide a lightweight, headless execution target for automation or CI nodes.

Execution is still guarded by **exec approvals** and per‑agent allowlists on the

Execution is still guarded by **exec approvals** and per-agent allowlists on the

node host, so you can keep command access scoped and explicit.

## Browser proxy (zero-config)

---

summary: "CLI reference for `openclaw nodes` (status, pairing, invoke, camera/canvas/screen)"

read_when:

- You’re managing paired nodes (cameras, screen, canvas)

- You're managing paired nodes (cameras, screen, canvas)

- You need to approve requests or invoke node commands

title: "Nodes"

---

---

summary: "CLI reference for `openclaw pairing` (approve/list pairing requests)"

read_when:

- You’re using pairing-mode DMs and need to approve senders

- You're using pairing-mode DMs and need to approve senders

title: "Pairing"

---