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

@clamepending/videomemory

v0.1.9

Published

VideoMemory agent plugin, hook pack, and host onboarding CLI

Readme

VideoMemory npm Package

This directory now contains the npm package published as @clamepending/videomemory.

What the package does:

  • exposes the videomemory host CLI plus the backward-compatible videomemory-openclaw alias
  • provides videomemory claude, the one-command Claude Code setup/launch path
  • runs the maintained VideoMemory onboarding and relaunch scripts bundled inside this npm package version
  • still declares the legacy OpenClaw plugin/hook pack for existing OpenClaw users

Claude Code flow:

videomemory claude

The Claude flow starts or checks VideoMemory, installs/checks the repo channel package, configures VideoMemory's webhook, opens the browser camera bridge on macOS, checks Claude auth, launches through Claude Code's approved channel path, allowlists the VideoMemory MCP tools used for wakeup replies, and exposes MCP tools so Claude can create monitor tasks itself. Use videomemory claude launch --dev only for local channel development.

Legacy OpenClaw install:

openclaw plugins install @clamepending/videomemory

After restarting the gateway, OpenClaw can call the plugin tools directly. A user can also run:

/videomemory-onboard --explain
/videomemory-onboard

Hook-pack install, for setups that want only gateway-startup checks:

openclaw hooks install @clamepending/videomemory

The startup hook does not auto-start VideoMemory unless VIDEOMEMORY_OPENCLAW_AUTOSTART=1 or hook config autoStart: true is set.

Current source-of-truth split:

  • VideoMemory host install and relaunch remain in docs/openclaw-bootstrap.sh and docs/relaunch-videomemory.sh
  • npm pack runs scripts/sync-bundled-scripts.mjs so those scripts are copied into bundled/ before publish
  • the current OpenClaw bridge files still live in the repo under docs/ and deploy/openclaw-real-home/
  • the ClawHub skill lives separately under clawhub-skill/videomemory/

Legacy OpenClaw CLI flow:

  1. videomemory-openclaw onboard --safe --explain
  2. videomemory-openclaw onboard --safe
  3. The CLI bootstraps VideoMemory without Docker and returns the UI link

Safe mode:

  • disables automatic Tailscale setup
  • disables model API-key copying
  • disables Telegram notification side effects
  • avoids sudo-requiring setup paths