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

@getplumb/plumb

v0.2.10

Published

Plumb OpenClaw plugin — auto-ingest and memory injection for OpenClaw

Readme

@getplumb/plumb — Plumb Memory Plugin for OpenClaw

Persistent memory for OpenClaw — automatic ingest and context injection, no setup required.

Made by Plumb · GitHub · npm

This is the official OpenClaw memory plugin from Plumb (plumb.run). It replaces OpenClaw's default memory-core slot with a persistent SQLite-backed memory that learns from your conversations and injects relevant context automatically.

Install

openclaw plugins install @getplumb/plumb

Then restart the gateway to activate:

openclaw gateway restart

That's it. Plumb starts learning from your conversations immediately.

Note on security warning: OpenClaw may show a warning about "environment variable access combined with network send." This is expected — Plumb reads your configured LLM API key and uses it to extract memory facts from conversations. No credentials are sent anywhere except the LLM provider you configure. You can safely proceed past this warning.

What it does

  • Auto-ingest — every conversation turn is stored to a local SQLite DB after the response
  • Context injection — relevant memory facts are injected into the system prompt before each response
  • Shadow mode — observe what would be injected without actually injecting it (good for testing)
  • Local only — all data stays on your machine; nothing is sent to external servers

Configuration

Configuration lives under plugins.entries.plumb.config in your openclaw.json. All fields are optional — defaults work out of the box.

| Field | Default | Description | |---|---|---| | dbPath | ~/.plumb/memory.db | Path to the SQLite database file | | userId | default | User ID for scoping memory | | shadowMode | false | If true, retrieves context but does not inject it | | llmProvider | (inherits from OpenClaw) | LLM provider for fact extraction (openai, anthropic, ollama, openai-compatible) | | llmModel | (inherits from OpenClaw) | Model for fact extraction | | llmApiKey | (inherits from OpenClaw) | API key for fact extraction |

To configure via CLI:

openclaw config set plugins.entries.plumb.config.userId "clay"
openclaw gateway restart

Uninstall

openclaw plugins uninstall @getplumb/plumb

Then manually restore the memory slot in your openclaw.json — OpenClaw does not do this automatically:

"plugins": {
  "slots": {
    "memory": "memory-core"
  },
  "entries": {
    "memory-core": { "enabled": true }
  }
}

Remove any "plumb" blocks from plugins.entries and plugins.installs, then restart:

openclaw gateway restart

Note: Skipping the manual config cleanup will leave OpenClaw with a broken memory slot. This is a known gap in the OpenClaw plugin uninstall flow — filed as an issue.

Links

License

MIT