Performance Benchmarks
Tested on LoCoMo10 dataset (1,540 long-range dialogue cases):Result: 49% improvement over baseline with 83% token reduction compared to native memory.
Prerequisites
- Python 3.10+
- Node.js 22+
- cmake and g++ (for compiling C++ extensions)
- OpenClaw installed globally:
npm install -g openclaw - OpenViking installed:
pip install openviking --upgrade --force-reinstall
Quick Start
One-Click Install (Linux/macOS)
Manual Setup
1
Install OpenClaw
2
Install OpenViking
3
Run Setup Helper
From the OpenViking repository:The helper will:
- Create
~/.openviking/ov.confwith your API keys - Deploy the plugin to
~/.openclaw/extensions/memory-openviking - Configure OpenClaw to use the plugin
- Generate environment file
~/.openclaw/openviking.env
4
Start OpenClaw
Linux/macOS:Windows (cmd):
Configuration
Server Config (~/.openviking/ov.conf)
The
workspace path must be absolute (e.g., /home/yourname/.openviking/data). Tilde (~) is not supported.Plugin Configuration
The plugin operates in two modes:Memory Behavior
Usage
Once configured, memory works automatically:Storing Memories
- User provides factual information
- Preferences or settings are mentioned
- Important decisions are discussed
Recalling Memories
In a later session:Manual Tools
OpenClaw also provides explicit memory tools:Troubleshooting
Plugin not showing in gateway output
Plugin not showing in gateway output
Verify the environment file is loaded:
Health check timeout
Health check timeout
A stale process may be occupying the port:
Extracted 0 memories
Extracted 0 memories
Check your model configuration in
ov.conf:- Verify
embedding.dense.api_keyis a valid API key - Verify
vlm.api_keyis set - Verify
vlm.modelis a model name (not an API key)
Memory shows 'disabled' or 'memory-core'
Memory shows 'disabled' or 'memory-core'
The plugin slot is not set correctly:Restart the gateway after changing slots.
Daily Usage
Create a convenient alias (Linux/macOS):.bashrc
