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

@carlitose86/pi-telegram-stt

v0.1.0

Published

Local, pluggable speech-to-text for Pi Telegram voice notes (ports and adapters: whisper.cpp, any command).

Readme

pi-telegram-stt

Local, pluggable speech-to-text for Pi Telegram Reactive: send a voice note from Telegram and it is transcribed on your own PC into the Pi prompt, with the engine and model you choose.

  • Audio never leaves your machine (unless you configure a command that sends it).
  • Nothing is downloaded automatically: you install the engine and pick the model.
  • Language is auto-detected by the model; you can force one.
  • Ports and adapters: built-in whisper-cpp and command engines, plus registerEngine() for third-party engines.

Install

Requires @carlitose86/pi-telegram-reactive connected in Pi.

pi install npm:@carlitose86/pi-telegram-stt
# or from Git
pi install git:github.com/carlitose/pi-telegram-stt

Then /reload Pi.

Configure

Create ~/.pi/agent/telegram-stt.json (or $PI_CODING_AGENT_DIR/telegram-stt.json). It is read on every voice note, so edits apply without reload. Without this file the package stays passive.

whisper.cpp (recommended)

  1. Install whisper.cpp (whisper-cli) and ffmpeg.
  2. Download a GGML model of your choice, for example ggml-large-v3-turbo.bin (best quality) or ggml-small.bin (faster), from the whisper.cpp models page.
  3. Configure:
{
  "engine": "whisper-cpp",
  "engines": {
    "whisper-cpp": {
      "binary": "whisper-cli",
      "model": "C:/models/ggml-large-v3-turbo.bin",
      "threads": 4
    }
  }
}

binary and ffmpeg accept an executable name on PATH, an absolute path, or an argv array (for example ["wsl", "whisper-cli"]).

Any other engine (command)

Use any program that prints the transcript on stdout. Placeholders: {file} original audio, {wav} 16 kHz mono WAV (converted with ffmpeg), {language} optional hint (dropped when empty). No shell is involved.

{
  "engine": "command",
  "engines": {
    "command": { "template": ["my-stt", "--input", "{wav}", "--lang", "{language}"] }
  }
}

Common options

| Key | Default | Meaning | | --- | --- | --- | | engine | — | whisper-cpp, command, or a third-party engine id | | language | auto-detect | Force a language code such as it | | timeoutMs | 120000 | Per-step timeout; the process is killed when exceeded |

Check

Run /telegram-stt-status in Pi: it shows the selected engine and why it is not ready (missing binary, ffmpeg, or model).

Operator-configured inboundHandlers in telegram.json still take priority; this package is the bridge's registered transcription provider fallback.

Add an engine

import { registerEngine, type SttEngine } from "@carlitose86/pi-telegram-stt";

registerEngine("my-engine", (options): SttEngine => ({
  id: "my-engine",
  isAvailable: async () => ({ ok: true }),
  isReady: async () => ({ ok: true }),
  transcribe: async ({ path, language }) => ({ text: await myTranscribe(path, language) }),
}));

Then set "engine": "my-engine"; options come from engines["my-engine"].

Design

See docs/specs/local-stt-adapters.md. The port idea is inspired by FluidVoice's TranscriptionProvider; no code is copied.

License

MIT