Skip to main content

​
Prerequisites

You need:

​
Manual setup

1

Clone both repositories

2

Build OpenClaw

This compiles the OpenClaw gateway and CLI tools you’ll use in the next steps.
3

Install the LogLife plugin

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.
4

Generate an API key

This creates a random 256-bit key and stores it in ~/.openclaw/openclaw.json. You’ll need this key when configuring the website.To retrieve the key later:
5

Start the OpenClaw gateway

Verify the plugin loaded by hitting the endpoint:
You should get a JSON response — either session data or {"error":"Session not found"}. Both mean the plugin is working.
If you already have an OpenClaw instance with sessions, try a real session ID to see actual data.

​
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:
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 for the full list of required secrets.

​
Troubleshooting

Make sure the name field in plugin/package.json matches the id in plugin/openclaw.plugin.json. Both should be "loglife".
Check that the gateway is running and the OPENCLAW_API_URL in your .env is correct. Test the connection directly:
Another gateway process may already be running. Kill it and try again:
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: