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

@coinseeker/opencode-telegram-plugin

v1.1.3

Published

Control and monitor OpenCode from Telegram with notifications, question replies, and subagent-aware completion.

Readme

OpenCode Telegram Plugin

Control and monitor OpenCode from Telegram.

Install

Paste below into your OpenCode.

Install and configure OpenCode Telegram Plugin by following the instructions here:
https://raw.githubusercontent.com/coin-seeker/opencode-telegram-plugin/refs/heads/main/docs/installation.md

Configure the npm package in ~/.config/opencode/opencode.json:

{
  "plugin": ["@coinseeker/[email protected]"]
}

Current stable version: @coinseeker/[email protected].

Restart OpenCode after editing the config. OpenCode resolves npm package plugins on startup.

To update an existing install, replace the previous pinned package entry with @coinseeker/[email protected], keep the rest of the plugin array unchanged, and restart OpenCode.

Configure Telegram

Create ~/.config/opencode/telegram-remote/.env:

mkdir -p ~/.config/opencode/telegram-remote
chmod 700 ~/.config/opencode/telegram-remote
cat > ~/.config/opencode/telegram-remote/.env <<'EOF'
TELEGRAM_BOT_TOKEN=your_bot_token_here
TELEGRAM_ALLOWED_USER_IDS=123456789,987654321
# Optional: skip first-message discovery
# TELEGRAM_CHAT_ID=123456789
EOF
chmod 600 ~/.config/opencode/telegram-remote/.env

Keep this file private. Never commit or share your Telegram bot token.

Usage

  1. Create a Telegram bot with @BotFather.
  2. Get your numeric Telegram user ID from @userinfobot.
  3. Add the token and allowed user IDs to the env file above.
  4. Restart OpenCode.
  5. Send any message to your bot in a private Telegram chat.

Features

  • Root session completion notifications.
  • Background subagent-aware completion: child session messages are suppressed and parent completion waits until children finish.
  • OpenCode question prompts via Telegram inline buttons.
  • Multi-select question prompts with toggle buttons and Done submission.
  • Custom free-text answers from Telegram.
  • Permission approve/reject buttons from Telegram.
  • Multi-session-safe Telegram polling through a file-lock leader model.
  • Log file output instead of stdout terminal spam.
  • Cross-process remote session listing via /sessions, /status N, /start_work N, /help slash commands.
  • Safety-gated remote /start-work execution: verifies agent=plan, idle status, incomplete plan, and no active boulder before dispatching.

Logs

node -e "const os=require('os'); console.log(os.tmpdir() + '/opencoder-telegram.log')"

Source

https://github.com/coin-seeker/opencode-telegram-plugin