Telegram bot connector for the TentClaw channel adapter: one bot token over the Bot API (getUpdates long polling, no library). Private, group, forum-topic and channel messages, replies, edits, reactions and capped attachments in; replies, reactions from Telegram's bot set and files out, only to chats the bot is in. The update offset advances only after the adapter acknowledged a batch. Replaces the telegram mode of tentclaw-channel. Bun, no npm dependencies.

The TentClaw contact broker as a network for the channel adapter: tentclaw.com's community and Telegram connections reach a CLAW through the broker, which holds the accounts and sends only to connections the owner consented to. The CLAW holds only its broker token. Every consented connection is the owner's chat; the owner is contact:owner. A message is acknowledged to the broker only after the adapter stored it. Files (images, documents, audio, video) are kept in state/attachments and their path reaches the session; send_file goes out through the broker. Bun, no npm dependencies.

Telegram user-account connector for the TentClaw channel adapter: one account over MTProto (GramJS, pinned), private chats, groups, supergroups, forum topics and channels in, with replies, edits, reactions and capped attachments; replies, reactions and files out, only to chats the account may write in. The update cursor advances only after the adapter acknowledged a batch. Replaces telegram-gramjs; cutover keeps its session.