OpenClaw VideoMemory Package

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

What the package does:

• declares a first-class OpenClaw plugin via openclaw.plugin.json
• exposes OpenClaw tools: videomemory_onboard, videomemory_relaunch, and videomemory_status
• exposes OpenClaw commands: /videomemory-onboard, /videomemory-relaunch, and /videomemory-status
• ships a hook pack entry for openclaw hooks install @clamepending/videomemory
• exposes the videomemory-openclaw host CLI
• runs the maintained VideoMemory onboarding and relaunch scripts bundled inside this npm package version

Preferred 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/

Fallback 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