telegram-fleet-roll-call

To enable cross-agent messaging, you orchestrate a fleet roll-call that discovers all bot user IDs via the Telegram API, updates each agent's allowed_users configuration to include every other bot and the human user, then restarts the gateways to apply the changes.

Bots fail to communicate because Hermes gateways filter messages by allowed_users, blocking messages from unknown bot IDs. Running a roll-call discovers all bot identities and updates every agent's allowed_users list to permit bidirectional cross-agent traffic.

To update allowed_users, query the Telegram API with the new agent's bot token to retrieve its user ID, then modify the YAML config files of all existing agents to include the new ID alongside the human user, and restart the gateway services.

The best way to synchronize bot user IDs is to run an automated roll-call process that queries each agent's bot token, converges all discovered identities, updates the YAML configuration files, and restarts the gateway fleet to verify cross-agent communication.

You need to run a fleet roll-call whenever a new agent is added to the Hermes gateway fleet or when existing agents cannot communicate, ensuring each agent's allowed_users includes all other bots and the human user for successful cross-agent messaging.

Yes, the Hermes gateway requires a restart after updating allowed_users to apply the YAML configuration changes, which allows the newly discovered bot identities to pass the message filter and verify the roll-call works.