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

@vshulcz/openclaw-deja

v0.20.2

Published

deja-vu memory for OpenClaw: the coding sessions already on this machine — OpenClaw, Claude Code, Codex, Cursor and 29 more — recalled before each turn and searchable as tools. A local index, no LLM.

Readme

@vshulcz/openclaw-deja

OpenClaw remembers its own sessions. This plugin answers the other question: what was done in the thirty-two other coding agents on this machine — Claude Code, Codex, Cursor, Gemini and Zed among them — including the months before OpenClaw was installed.

It runs deja, a local Go binary that indexes the transcripts those agents already wrote to disk. No LLM, no embeddings, nothing leaves the machine.

Install

openclaw plugins install clawhub:@vshulcz/openclaw-deja

The deja binary comes with the package; a deja you installed yourself (brew install deja-vu) always wins — see Which binary.

deja install openclaw-auto wires OpenClaw too, and is the shorter path if you have the CLI: it adds deja's MCP server and writes a plugin of its own. Having both is fine: this package reads what the installer wrote and contributes only what is missing.

What it does

  • Before each turn (before_prompt_build): the prompt is matched against the index and, when a past session answers it, that session goes in front of the model. Silence is the common case.
  • Tools: deja_recall (search the history), deja_fix (what was run after this error before), deja_blame (which sessions touched a file and what they concluded).

Config

{
  "plugins": {
    "entries": {
      "deja-vu": {
        "enabled": true,
        "config": { "autoRecall": true, "tools": true, "bin": "/opt/homebrew/bin/deja" }
      }
    }
  }
}

All three are optional. autoRecall: false keeps the tools and drops the per-turn recall; tools: false the reverse.

Which binary

In order: bin from the config, DEJA_BIN, deja on PATH, the usual install locations, and last the copy bundled through @vshulcz/deja-vu.

Privacy

deja reads session files where the agents wrote them and builds a local index under ~/.cache/deja (or DEJA_INDEX_DIR). Keys and tokens are stripped as the index is built. Nothing is uploaded.

Part of deja-vu. MIT.