hermes - 💡(How to fix) Fix feat(gateway): include bot identity in session_key for multi-bot Telegram setups [1 participants]

TL;DR

Modify the build_session_key() function in gateway/session.py to include the bot identifier, such as the bot token hash, to prevent session key collisions across bots.

Guidance

• Identify the build_session_key() function in gateway/session.py and verify that it only uses chat_id for Telegram DMs.
• Consider modifying the function to include the bot token hash in the session key, as suggested in the expected behavior.
• Review the code to ensure that the bot token hash is accessible and can be used to construct the session key.
• Test the modified function with multiple bots and the same Telegram user to verify that session key collisions are resolved.

Example

def build_session_key(chat_id, bot_token):
    # Assuming bot_token_hash is a function that generates a hash from the bot token
    bot_token_hash = bot_token_hash(bot_token)
    return f"agent:main:telegram:bot:{bot_token_hash}:dm:{chat_id}"

Notes

The solution assumes that the bot token is available and can be used to generate a unique hash. The actual implementation may vary depending on the specific requirements and constraints of the system.

Recommendation

Apply workaround: Modify the build_session_key() function to include the bot identifier, as this will resolve the session key collision issue and provide isolated session state for each bot.