@alfe.ai/openclaw-telegram
v0.0.3
Published
Local-custody Telegram MTProto user-session listener for OpenClaw
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.
The Telegram device session never leaves the agent machine. After enabling the Telegram Connection in Alfe, run:
npx -y @alfe.ai/[email protected] login --agent-id <agent-id>If the package binary is already on PATH, alfe-telegram login is the
equivalent shorthand. The dashboard supplies the agent-specific command; when
--agent-id is omitted, the CLI resolves it from the local agent token.
The command creates an isolated local Python runtime, asks for the API ID/hash
from my.telegram.org, then completes phone-code and optional 2FA login. It
does not print the resulting session.
Agent tools:
telegram_statustelegram_list_chatstelegram_list_subscriptionstelegram_subscribetelegram_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>