Building a Telegram Group Join Bot with Muse and OIDC

Introduction

The currently popular muse is an Agent. Moreover, it comes "fully furnished": utilities and the network are connected, and the furniture and appliances are all in place. You don't need to install a system or configure a model; you can start chatting right away.

All the examples in my blog about developing for Agents and putting Agents to work can be copied over to muse and tried there.

In Practice

Give muse the key points summarized in my previous post about a Telegram group-join verification bot and have it build the system from scratch.

Develop a Telegram group-join verification system deployed on Cloudflare worker

Based on Cloudflare worker; do not use KV.
Split the muting and unmuting operations into two workers.

Workflow:
1. A new member joins the group,
2. worker-a uses bot-admin to mute the new member and sends a group message containing a human-verification link. The link points to worker-b and carries the user's user_id and the group's chat_id.
3. The user visits worker-b through the human-verification link.
4. worker-b invokes Turnstile for human verification.
5. After the user passes human verification, worker-b uses the user_id and chat_id information carried in the link to have bot-admin remove the member's messaging restriction.

Additional requirements:
The message in step 2 must use Ephemeral Messages (visible only to the designated user).
The human-verification flow in step 4 must also include a telegram login step to confirm that the person completing the verification also controls the muted telegram account.

Exception handling:
There is a whitelist of work groups. If worker-a receives a message pushed by the telegram server and finds that the group's chat_id is not on the whitelist, the bot should leave the group.