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

imprnt-plugin-telegram

v0.1.0

Published

imprnt plugin: your vault from your phone - an imp lair session bridged to Telegram via Claude Code channels. Recall-first phone replies, one start command, no daemon.

Readme

imprnt-plugin-telegram

Your vault, reachable from your phone. A long-lived imp session runs in the lair with Claude Code's Telegram channel enabled. You text your bot from anywhere, the session searches the vault on your machine and texts the answer back. The vault never leaves the machine. Only the conversation does.

Built on Claude Code channels (research preview, v2.1.80+, claude.ai or Console auth, needs Bun). This plugin wraps the official telegram@claude-plugins-official channel with the vault-side behavior rules and a start command.

Install

imprnt plugin add telegram

That wires the behavior fragment (recall-first, phone-sized replies, never paste a whole note). Then the one-time channel setup, in any Claude Code session:

  1. Create a bot: open BotFather in Telegram, send /newbot, copy the token.
  2. Install the official channel plugin: /plugin install telegram@claude-plugins-official (if it is not found, run /plugin marketplace add anthropics/claude-plugins-official first), then /reload-plugins.
  3. Give it the token: /telegram:configure <token> (or export TELEGRAM_BOT_TOKEN in your shell instead, per the imprnt secrets rule - either way it never lands in the project).
  4. Start the link (below), text the bot anything, and pair: /telegram:access pair <code>, then /telegram:access policy allowlist so only you can reach the session.

Use

sh plugins/telegram/link.sh

This runs imp lair --channels plugin:telegram@claude-plugins-official under caffeinate -i (macOS), so the Mac stays awake while the link is up. Stop with Ctrl-C. It is a command you run when you leave the desk, never a daemon: nothing starts by being installed.

Then text the bot from your phone: "what do I know about the access-platform cutover?", "remember: the dentist moved to the 24th". The session recalls, answers, files.

Honest constraints

  • The session answers only while it is running on an awake machine. A message sent while the link is down arrives when you next start it (Telegram holds undelivered bot updates for a while), and there is no way to cold-start a local session from the phone.
  • Telegram bot chats are not end-to-end encrypted. The vault stays home, but your questions and the answers transit Telegram's servers. Keep the bot private and the allowlist on.
  • A permission prompt pauses the session until approved. Run the lair with your usual allow rules so recall/read paths do not prompt, or approve from the terminal when you are back.
  • Channels are a research preview: the --channels syntax may change, and only Anthropic-allowlisted channel plugins can register, which is why this plugin wraps the official one instead of shipping its own.

Remove

imprnt plugin rm telegram

Add --purge to delete plugins/telegram/. To remove the channel itself: /plugin uninstall telegram@claude-plugins-official, and delete ~/.claude/channels/telegram/.env if you configured the token there.