> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claw-link.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenClaw setup

> Install the ClawLink plugin in OpenClaw and pair this device

ClawLink works with OpenClaw through the ClawLink plugin. The normal flow is: install the plugin, start browser pairing, approve the device, then connect apps from the ClawLink dashboard.

## Install the plugin

The recommended install path uses ClawHub:

```bash theme={null}
openclaw plugins install clawhub:clawlink-plugin
openclaw gateway restart
```

If you prefer npm, this also works:

```bash theme={null}
openclaw plugins install @useclawlink/openclaw-plugin
openclaw gateway restart
```

If the current chat started before the plugin was installed and the ClawLink tools do not appear yet, start a fresh chat so OpenClaw reloads the tool catalog.

## Pair this device

<Steps>
  <Step title="Start browser pairing">
    In OpenClaw, ask the assistant to set up ClawLink or start pairing. The plugin should call `clawlink_begin_pairing` and return a browser URL.
  </Step>

  <Step title="Approve this device in your browser">
    Open the pairing URL, sign in to ClawLink if needed, and click **Approve this device**.
  </Step>

  <Step title="Let OpenClaw finish the pairing check">
    Return to OpenClaw so the plugin can finish the local save step and confirm that the device is paired.
  </Step>

  <Step title="Connect apps from the dashboard">
    Open **Dashboard > Connections**, add the apps you want, and start using them from OpenClaw.
  </Step>
</Steps>

## What pairing stores locally

Browser pairing stores a local ClawLink device credential in `~/.openclaw/openclaw.json`.

In the recommended flow, you never have to paste that raw key into chat. OpenClaw stores it for the plugin after browser approval finishes.

## Available plugin tools

After setup, the plugin exposes tools for pairing, connection management, tool discovery, previews, and execution:

* `clawlink_begin_pairing`
* `clawlink_get_pairing_status`
* `clawlink_start_connection`
* `clawlink_get_connection_status`
* `clawlink_list_integrations`
* `clawlink_list_tools`
* `clawlink_search_tools`
* `clawlink_describe_tool`
* `clawlink_preview_tool`
* `clawlink_call_tool`

## Manual fallback

Use **Settings > API Keys** only if your OpenClaw client exposes a plugin settings UI and browser pairing is not available.

In that fallback path:

1. Create a key in **Settings > API Keys**
2. Copy the raw `cllk_live_...` value when it is shown
3. Paste it into the plugin settings field for `clawlink-plugin`

Most users should skip this and use browser pairing instead.