snowclaw plugins

Manage OpenClaw plugins. Two plugin sources are supported: npm packages (installed into the image at build time) and path-based (local directories copied into the build context and registered via plugins.load.paths).

Plugin declarations live in .snowclaw/plugins.json (commit to git). The CLI reads that file and emits the corresponding plugins section in openclaw.json on every config write.

list

snowclaw plugins list

Shows configured plugins — id, source (npm or path), and version/path.

add

snowclaw plugins add @openclaw/plugin-example
snowclaw plugins add ./my-local-plugin

Add a plugin. The CLI detects whether the spec is an npm package name or a local path and updates .snowclaw/plugins.json + openclaw.json accordingly.

• npm plugins — injected as a RUN openclaw plugins install <spec> Dockerfile layer. Installed at image build time.
• Path-based plugins — the directory is copied into .snowclaw/build/plugins/ during snowclaw build, and referenced from plugins.load.paths in the generated openclaw.json.

Configure plugin settings directly in openclaw.json under plugins.entries.<id>.config. Store plugin credentials in .env — they'll automatically sync as Snowflake secrets on the next push or deploy.

remove

snowclaw plugins remove <id>

Removes the plugin declaration from .snowclaw/plugins.json and the corresponding entry from openclaw.json. Rebuild the image on next deploy to actually uninstall it from the container.