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

# Plugin installation

> Install and run the LogLife plugin on your OpenClaw gateway

## Prerequisites

<Info>
  **You need:**

  * [Node.js](https://nodejs.org) 24 or higher
  * [pnpm](https://pnpm.io) 10 or higher
  * [Git](https://git-scm.com)
</Info>

## Manual setup

<Steps>
  <Step title="Clone both repositories">
    ```bash theme={null}
    git clone https://github.com/jmoraispk/loglife.git
    git clone https://github.com/openclaw/openclaw.git ~/openclaw
    ```
  </Step>

  <Step title="Build OpenClaw">
    ```bash theme={null}
    cd ~/openclaw
    pnpm install
    pnpm build
    ```

    This compiles the OpenClaw gateway and CLI tools you'll use in the next steps.
  </Step>

  <Step title="Install the LogLife plugin">
    ```bash theme={null}
    cd ~/openclaw
    ./openclaw.mjs plugins install /path/to/loglife/plugin --link
    ```

    The `--link` flag means the plugin loads directly from your LogLife repo — no files are copied. When you `git pull` new changes, the plugin updates automatically.
  </Step>

  <Step title="Generate an API key">
    ```bash theme={null}
    cd ~/openclaw
    ./openclaw.mjs config set plugins.entries.loglife.config.apiKey "$(openssl rand -hex 32)"
    ```

    This creates a random 256-bit key and stores it in `~/.openclaw/openclaw.json`. You'll need this key when [configuring the website](/configuration#website-env).

    To retrieve the key later:

    ```bash theme={null}
    grep apiKey ~/.openclaw/openclaw.json
    ```
  </Step>

  <Step title="Start the OpenClaw gateway">
    <CodeGroup>
      ```bash Development (foreground) theme={null}
      cd ~/openclaw
      ./openclaw.mjs gateway --allow-unconfigured
      ```

      ```bash Production (background service) theme={null}
      cd ~/openclaw
      ./openclaw.mjs gateway install
      ./openclaw.mjs gateway start
      ```
    </CodeGroup>

    Verify the plugin loaded by hitting the endpoint:

    ```bash theme={null}
    curl -H "Authorization: Bearer YOUR_API_KEY" \
      "http://localhost:18789/loglife/sessions?sessionId=test"
    ```

    You should get a JSON response — either session data or `{"error":"Session not found"}`. Both mean the plugin is working.

    <Tip>If you already have an OpenClaw instance with sessions, try a real session ID to see actual data.</Tip>
  </Step>
</Steps>

## Automated setup

If you prefer a single script instead of manual steps, the plugin includes a production setup script that handles steps 3–5 automatically:

```bash theme={null}
bash ~/loglife/plugin/setup.sh
```

The script installs the plugin, generates an API key (if not already set), restarts the gateway, and runs a health check. It prints the API key and next steps at the end.

## Plugin updates

A GitHub Actions workflow triggers on pushes to `main` that change files in `plugin/**`. The workflow SSHes into your server and runs `git pull` to update the plugin code. See the [CI/CD section](/development#ci-cd) for the full list of required secrets.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Plugin install fails with 'plugin not found'">
    Make sure the `name` field in `plugin/package.json` matches the `id` in `plugin/openclaw.plugin.json`. Both should be `"loglife"`.
  </Accordion>

  <Accordion title="Dashboard shows 'Failed to reach OpenClaw server'">
    Check that the gateway is running and the `OPENCLAW_API_URL` in your `.env` is correct. Test the connection directly:

    ```bash theme={null}
    curl -H "Authorization: Bearer YOUR_KEY" \
      "http://localhost:18789/loglife/sessions?sessionId=test"
    ```
  </Accordion>

  <Accordion title="Gateway fails to start with lock error">
    Another gateway process may already be running. Kill it and try again:

    ```bash theme={null}
    pkill -f "openclaw gateway" && ./openclaw.mjs gateway --allow-unconfigured
    ```
  </Accordion>

  <Accordion title="401 Unauthorized from the plugin">
    The API key in your `.env` (or Vercel env vars) doesn't match the key in `~/.openclaw/openclaw.json`. Regenerate it and update both sides:

    ```bash theme={null}
    cd ~/openclaw
    ./openclaw.mjs config set plugins.entries.loglife.config.apiKey "$(openssl rand -hex 32)"
    grep apiKey ~/.openclaw/openclaw.json
    ```
  </Accordion>
</AccordionGroup>