npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

openclaw-openviking-plugin

v0.1.5

Published

OpenClaw plugin for long-term memory via OpenViking. Hook-only design, works alongside LCM without conflict.

Readme

openclaw-openviking-plugin

中文文档

An OpenClaw plugin that integrates with OpenViking for long-term memory.

Hook-only — does not register as a context engine. Works alongside LCM or any other context engine without conflict.

Features

  • autoRecall — searches OpenViking memories before each prompt and injects relevant context
  • autoCapture — commits new conversation messages to OpenViking after each turn for memory extraction
  • memory_recall tool — model-triggered memory search
  • memory_store tool — model-triggered memory write
  • memory_forget tool — model-triggered memory deletion

Slash Commands

  • /ov, /openviking, or explicit /ov status — show plugin status and diagnostics
  • Status output includes:
    • PluginautoRecall, autoCapture, captureSessionFilter
    • ConfigbaseUrl and recall/capture limits
    • OV Server — server reachability and version
    • Queue — local OpenViking queue counts by status (shown when the OV server is local)
    • Memories — user/agent memory counts broken down by subdirectory
  • /ov help — show command help

Requirements

  • OpenClaw gateway
  • OpenViking server running and accessible via HTTP

Installation

Via OpenClaw CLI (recommended)

openclaw plugins install openclaw-openviking-plugin

To update to the latest version:

openclaw plugins update openclaw-openviking-plugin

Using install.sh (from source)

git clone https://github.com/liushuangls/openclaw-openviking-plugin
cd openclaw-openviking-plugin
./install.sh

The script copies plugin files, installs dependencies, updates openclaw.json, and restarts the gateway automatically. Re-running it on an already-installed plugin performs an update (syncs files + restarts, config unchanged).

# Custom OV server address
OV_BASE_URL=http://192.168.1.100:1934 ./install.sh

Manual

Copy the directory to ~/.openclaw/extensions/openclaw-openviking-plugin/, run npm install --omit=dev inside it, then add the plugin to openclaw.json (see Configuration below) and restart the gateway.

Configuration

Add to your openclaw.json:

{
  "plugins": {
    "allow": ["openclaw-openviking-plugin"],
    "entries": {
      "openclaw-openviking-plugin": {
        "enabled": true,
        "config": {
          "baseUrl": "http://127.0.0.1:1934",
          "apiKey": "",
          "autoRecall": true,
          "autoCapture": true,
          "recallLimit": 6,
          "recallScoreThreshold": 0.15,
          "recallTokenBudget": 2000,
          "recallMaxContentChars": 500,
          "commitTokenThreshold": 0
        }
      }
    }
  }
}

| Field | Default | Description | |---|---|---| | baseUrl | http://127.0.0.1:1934 | OpenViking server URL | | apiKey | "" | API key (if required) | | autoRecall | true | Inject relevant memories before each prompt | | autoCapture | true | Commit conversation turns to OV after each response | | captureSessionFilter | [] | Only auto-capture when sessionKey fully matches any configured glob pattern, e.g. ["agent:*:telegram:direct:**"] | | recallLimit | 6 | Max memories to inject per turn | | recallScoreThreshold | 0.15 | Minimum relevance score (0–1) | | recallTokenBudget | 2000 | Max tokens for injected memory context | | recallMaxContentChars | 500 | Max characters per memory snippet | | commitTokenThreshold | 0 | Min tokens in a turn before committing (0 = always) |

Testing

npm install

# Unit tests (no server required)
npm run test:unit

# Integration tests (requires OV server)
OV_BASE_URL=http://127.0.0.1:1934 npm run test:integration

Integration tests skip automatically if the server is unreachable.

Coexistence with LCM

This plugin uses hooks only (before_prompt_build + agent_end). It does not set kind: "context-engine" and does not occupy the exclusive context engine slot, so it runs alongside lossless-claw or any other context engine without conflict.

License

MIT