Telegram Group Community Manager

A universal AI community-manager bot for your Telegram groups. It reads every message to build memory and learn each group's tone of voice, and replies only when @-mentioned or replied-to — in the group's own language and style. It understands images, answers with a voice note on request, web-checks anything current, and never invents facts. You (the installer) get a private DM assistant and a slash-command menu.

It self-configures — no code to edit, no IDs to paste into a script.

warning Read this first — trust model

Inside a group you enroll, every member's message is answered by the full in-app AI acting AS you (the workspace owner). That means a group member can, through the bot, read and write your workspace data and use your connected accounts (email, CRM, etc.).

Only enroll groups whose members you would trust with your entire Brain. To stop the bot in a group at any time, run /remove there.

Install & setup (about 5 minutes)

1. Install this project into your workspace.

2. Create a Telegram bot: message @BotFather → /newbot → copy the token. Then /setprivacy → select your bot → Disable (so it can see group messages — required for memory, tone, and mentions).

3. Add the token to Brain: Integrations → add a credential with service telegram and a field botToken = your token.

4. Open the "Community Manager" agent and copy its id from the page URL.

5. Run the agent once (its Run/Test panel) with this input:

```json

{ "_setup": true, "agentId": "<paste the agent id>" }

```

It activates itself, registers its Telegram webhook, creates its message database, and reports status. (If your workspace has more than one Telegram bot, also pass "credId": "<the right credential id>" so it picks the correct one.)

1. DM your bot (open t.me/<your_bot_username> and send anything). The first person to DM it becomes the owner — that's you. You'll get a welcome + the command menu.

2. Add the bot to a Telegram group, then type /allow in that group. Done — it's managing that group.

How members use it (in a group)

• Ask it — @mention the bot or reply to one of its messages.

• Show it a photo — send an image with a caption that tags the bot.

• Get a voice reply — say "reply with voice" / "ответь голосом".

• While it thinks, it keeps the typing indicator alive and reacts on your message (eyes → thinking → writing_hand).

Author / owner commands

Recognized only from the owner, and shown as a Telegram slash-menu in your DM. Group-scoped ones can also run inside the group (no argument needed there).

In a DM, [group] = a chat ID (from /groups) or part of the group's title.

Memory & tone

• Short-term: a rolling buffer of the last 1,000 messages per group — the context for every reply.

• Long-term: every message is also saved to the Community Manager Messages database (created automatically on first run).

• Tone of voice: the bot studies each group's own messages — language, formality, humor, punctuation, emoji habits, typical length — and relearns every 500 messages or 7 days. /relearn forces it.

• Erase: /forget FROM TO clears both layers for a group and date range.

Maintenance

• Change the bot token (same bot): just update the credential — everything else keeps working, and the menu re-registers itself.

• Move to a different bot: update the credential; the bot auto-registers its menu on the new bot. If it doesn't receive messages, re-run { "_setup": true, "agentId": "…" } to re-point the webhook.

• Re-assign the owner: run { "_setup": true, "resetOwner": true }, then DM the bot again (or pass "ownerTgId": <telegram id>).

• Check state anytime: run { "_selftest": true } — it reports the resolved bot, owner, database, and webhook.