Skip to content

v0.4.0

Choose a tag to compare

@thenavidm thenavidm released this 07 Sep 20:01
· 13 commits to main since this release

The channel surface, which is the part nobody else has.

telegram-mcp --channel pushes real Telegram messages into a Claude Code session that is already open. The official Telegram channel is a BotFather bot and can only see messages sent to that bot. This one is backed by MTProto, so an event can come from any chat you are actually in.

Nothing forwards until a chat is allowed. allow_chat opts one in. That default is deliberate: without it every message in every group you are in becomes model input, which is both expensive and a prompt-injection surface.

Personas. Each allowed chat can carry a name, delivered on the event as persona, so one session can answer as a different assistant depending on which chat a message came from.

Also in this release: the channel keeps its MCP surface up when Telegram is unreachable rather than exiting, and the publish workflow no longer fails a tag when the npm token is unset or the version is already published.

Profile Tools Every turn
core (default) 13 2,218
read 31 4,673
full 74 11,643
CLI all 74 175
npm install -g @thenavidm/telegram-mcp-cli

Full Changelog: v0.3.0...v0.4.0