examples/openclaw-plugin/INSTALL.md
Use OpenViking as the long-term memory backend for OpenClaw. After installation, OpenClaw will automatically remember important facts from conversations and recall relevant context before replying.
This document covers the current OpenViking plugin built on OpenClaw's
context-enginearchitecture.
| Component | Required Version |
|---|---|
| Node.js | >= 22 |
| OpenClaw | >= 2026.3.7 |
The plugin connects to an existing OpenViking server. It does not start the OpenViking server for you. Start OpenViking first, keep it running, then point the plugin baseUrl at that HTTP service. The default local URL is http://127.0.0.1:1933.
Quick check:
node -v
openclaw --version
For a local OpenViking server on the same machine as OpenClaw:
pip install openviking --upgrade --force-reinstall
openviking-server init
openviking-server doctor
openviking-server
openviking-server init writes the server configuration, openviking-server doctor validates local model/provider auth, and openviking-server starts the HTTP API. Keep this process running while OpenClaw uses the plugin.
To run the server in the background:
mkdir -p ~/.openviking/data/log
nohup openviking-server > ~/.openviking/data/log/openviking.log 2>&1 &
If OpenViking runs on another machine, start it on a reachable host/port, for example:
openviking-server --host 0.0.0.0 --port 1933
Then configure the OpenClaw plugin baseUrl to that address, such as http://your-server:1933.
Verify the server before installing or restarting the plugin:
curl http://127.0.0.1:1933/health
If you previously installed the legacy memory-openviking plugin, remove it first, then continue with the install or upgrade commands below.
openviking plugin is not compatible with the legacy memory-openviking plugin.curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/openclaw-plugin/upgrade_scripts/cleanup-memory-openviking.sh -o cleanup-memory-openviking.sh
bash cleanup-memory-openviking.sh
openclaw plugins install clawhub:@openclaw/openviking
After installation, run the interactive setup wizard:
openclaw openviking setup
The wizard prompts for your remote OpenViking server URL and optional API key, then writes configuration to $OPENCLAW_STATE_DIR/openclaw.json (default: ~/.openclaw/openclaw.json).
The ov-install helper automates plugin deployment:
npm install -g openclaw-openviking-setup-helper
ov-install
Common variant:
ov-install --workdir ~/.openclaw-second
To upgrade the plugin to the latest version:
npm install -g openclaw-openviking-setup-helper@latest && ov-install -y
To install or upgrade to a specific release:
ov-install -y --version 0.2.9
| Parameter | Meaning |
|---|---|
--workdir PATH | Target OpenClaw data directory |
--version VER | Set plugin version. For example, 0.2.9 maps to plugin v0.2.9 |
--current-version | Print the currently installed plugin version |
--plugin-version REF | Set only the plugin version. Supports tag, branch, or commit |
--github-repo owner/repo | Use a different GitHub repository for plugin files. Default: volcengine/OpenViking |
--update | Upgrade only the plugin |
-y | Non-interactive mode, use default values |
If you need to pin the installer itself:
npm install -g openclaw-openviking-setup-helper@VERSION
The plugin configuration lives under plugins.entries.openviking.config.
Get the current full plugin configuration:
openclaw config get plugins.entries.openviking.config
The plugin connects to an existing remote OpenViking server.
| Parameter | Default | Meaning |
|---|---|---|
baseUrl | http://127.0.0.1:1933 | Remote OpenViking HTTP endpoint |
apiKey | empty | Optional OpenViking API key |
agent_prefix | empty | Optional prefix for OpenClaw agent IDs. If no agent ID is available, the plugin uses main. Interactive setup accepts only letters, digits, _, and - |
Common settings:
openclaw config set plugins.entries.openviking.config.baseUrl http://your-server:1933
openclaw config set plugins.entries.openviking.config.apiKey your-api-key
openclaw config set plugins.entries.openviking.config.agent_prefix your-prefix
After installation:
openclaw gateway restart
Windows PowerShell:
openclaw gateway restart
Check that the plugin owns the contextEngine slot:
openclaw config get plugins.slots.contextEngine
If the output is openviking, the plugin is active.
Follow OpenClaw logs:
openclaw logs --follow
If you see openviking: registered context-engine, the plugin loaded successfully.
Check the OpenViking service log:
By default the log file lives under workspace/data/log/openviking.log. With the default setup this is usually:
cat ~/.openviking/data/log/openviking.log
Check installed versions:
ov-install --current-version
If the steps above all look good and you want to further verify the full Gateway → OpenViking pipeline, run the plugin's health check script:
python examples/openclaw-plugin/health_check_tools/ov-healthcheck.py
This script injects a real conversation through Gateway and then verifies from the OpenViking side that the session was captured, committed, archived, and had memories extracted. See health_check_tools/HEALTHCHECK.md for full details.
To remove the OpenClaw plugin:
curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/openclaw-plugin/upgrade_scripts/uninstall-openclaw-plugin.sh -o uninstall-openviking.sh
bash uninstall-openviking.sh
For a non-default OpenClaw state directory:
curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/openclaw-plugin/upgrade_scripts/uninstall-openclaw-plugin.sh -o uninstall-openviking.sh
bash uninstall-openviking.sh --workdir ~/.openclaw-second
See also: INSTALL-ZH.md