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

minutes-openclaw

v0.2.0

Published

Local whisper.cpp transcription via Minutes for OpenClaw

Readme

minutes-openclaw

Local whisper.cpp audio transcription for OpenClaw, powered by the Minutes CLI.

Registers Minutes as a MediaUnderstandingProvider so any OpenClaw channel (WhatsApp, Telegram, etc.) gets private offline transcription without sending audio to a cloud API.

Requirements

  • minutes binary in PATH (or set MINUTES_BIN=/path/to/minutes) that includes the minutes transcribe --json command (added upstream in silverstein/minutes#380, merged to main after v0.19.0). If minutes --help doesn't list a transcribe subcommand, build from source or wait for the next tagged release.
  • Whisper model downloaded: minutes setup --model small
  • ffmpeg (recommended for ogg/opus/webm from WhatsApp/Telegram):
    • macOS: brew install ffmpeg
    • Linux: apt install ffmpeg
    • Without ffmpeg, WAV and MP3 are still supported natively

Installation

One-liner — installs and builds directly from GitHub, then configures OpenClaw:

openclaw plugins install github:maosuarez/minutes-openclaw
curl -fsSL https://raw.githubusercontent.com/maosuarez/minutes-openclaw/master/install.sh | bash

Custom binary or language:

MINUTES_BIN=/usr/local/bin/minutes MINUTES_LANGUAGE=es \
  curl -fsSL https://raw.githubusercontent.com/maosuarez/minutes-openclaw/master/install.sh | bash

From a local clone (for development or offline):

git clone https://github.com/maosuarez/minutes-openclaw
cd minutes-openclaw
openclaw plugins install .   # prepare script builds automatically
./install.sh

install.sh env vars:

| Var | Default | Description | |---|---|---| | MINUTES_BIN | minutes | Path to the minutes binary | | MINUTES_LANGUAGE | (auto) | Default language code (en, es, fr, …) |

Enable for audio understanding

Installing the plugin registers the provider, but OpenClaw only uses it once you wire it into tools.media.audio.models (same as any other audio provider — installation alone is not enough). One validated write:

openclaw config patch --stdin <<'EOF'
{ tools: { media: { audio: { enabled: true, models: [ { type: "provider", provider: "minutes", model: "whisper.cpp" } ] } } } }
EOF
openclaw plugins doctor          # should report "No plugin issues detected"
# restart the gateway so the change applies (e.g. systemctl --user restart openclaw-gateway)

Verify end-to-end without sending a real voice note:

openclaw infer audio transcribe --file /path/to/audio.wav --json
# routes through the minutes provider and prints the transcript

How it works

When OpenClaw receives a voice note attachment:

  1. The audio buffer is written to a temp file.
  2. minutes transcribe <temp> --json [-l language] is called locally — whisper.cpp transcribes it and prints a JSON envelope to stdout. No meeting files are written and no summarization runs.
  3. data.text from the envelope is returned to OpenClaw for delivery.
  4. The temp audio file is always deleted.

Nothing is persisted to disk beyond the temp audio file, which is removed as soon as transcription finishes (or fails).

Priority

autoPriority: { audio: 10 } — lower than all bundled cloud providers (openai=20, xai=25, …), so Minutes is tried first when installed.

Configuration

| Key | Type | Default | Description | |-----|------|---------|-------------| | minutesBin | string | "minutes" | Path to the minutes binary (or set MINUTES_BIN env var) | | language | string | (auto) | Default language code ("en", "es", "fr", …) |

Development

npm install
npm run build   # tsc
npm test        # vitest unit tests (no disk/network)

# Live test (requires minutes binary + whisper model):
MINUTES_OPENCLAW_LIVE=1 npm test   # transcribes test/fixtures/demo.wav

Design: self-contained community plugin

This is a community-owned package, independent of the Minutes core release train (per the maintainer's guidance on coupling — OpenClaw ships ~monthly with an evolving pluginApi, so the plugin tracks OpenClaw on its own cadence):

  • Version 0.2.0, independent of the Minutes workspace version.
  • No source imports from Minutes crates — the sole runtime dependency is the minutes binary, invoked via subprocess.
  • Pinned to OpenClaw's pluginApi / pluginSdkVersion in package.json.
  • Shells out to the stable minutes transcribe --json contract (silverstein/minutes#376, shipped in #380) instead of scraping a generated markdown memo. No meeting files are written by this plugin — earlier versions (<0.2.0) shelled out to minutes process -t memo and had a persistMemo option to keep that memo file; that option is gone since the new contract never creates one.