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

@alfe.ai/openclaw-telegram

v0.0.20

Published

Local-custody Telegram MTProto user-session listener for OpenClaw

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

kevuptonkevuptonsam-alfesam-alfe

Keywords

alfeopenclawtelegramtelethonmtproto

Readme

@alfe.ai/openclaw-telegram

Local Telegram user-session access for an Alfe/OpenClaw agent. It uses Telethon/MTProto, so it can see the same dialog list as the signed-in Telegram account instead of the restricted Bot API view.

Open the agent's Connections in Alfe and choose Connect Telegram. Enter your phone number, Telegram verification code, and optional two-step password. Alfe supplies the application credentials and prepares the isolated local runtime. There are no commands or developer credentials for the user to provide.

The browser encrypts each private answer for a short-lived login attempt on the agent. The cloud relays ciphertext; the agent decrypts it and passes it directly to the local Telegram client. Codes and passwords do not enter agent prompts, logs, or configuration. The Telegram device session stays on that machine. The local login attempt expires after ten minutes and can be cancelled.

Managed hosts provide Python 3. Self-hosted hosts need Python 3.9 or newer; the integration creates its own virtual environment and installs pinned Telethon. If Python's built-in venv support is missing, it downloads a hash-verified PyPA virtualenv zipapp into the agent's private directory without changing system packages. Operators may still use alfe-telegram login --agent-id <agent-id> as a diagnostic fallback with their own Telegram application credentials.

Agent tools:

  • telegram_status
  • telegram_list_chats
  • telegram_list_subscriptions
  • telegram_subscribe
  • telegram_unsubscribe

Subscriptions are explicit and read-only toward Telegram. Incoming text and captions can trigger agent turns; generated responses are not posted back. Only subscribe where you have permission to process the messages, and follow Telegram's API terms.

Removing the Alfe Connection stops and uninstalls the listener but deliberately does not erase a logged-in device during an ordinary reinstall. Before retiring the machine, revoke the device session and remove its local state with:

npx -y @alfe.ai/[email protected] logout --agent-id <agent-id>