hermes - 💡(How to fix) Fix 🚀 Feature Request: Multi-User Preference Memory [3 comments, 3 participants]

TL;DR

Modify the memory tool to include an optional user_id parameter for isolating user preferences.

Guidance

• Add a user_id field to the memory tool parameters to allow for user-specific preference storage.
• Update the backend storage to include the user_id as a filtering condition, such as adding a column to the SQLite database or using user-isolated storage with Honcho/Mem0.
• Implement automatic injection of the corresponding user's preferences based on the user_id in the current message.
• Ensure backward compatibility by defaulting to the current single-user behavior when no user_id is provided.

Example

# Example of modified memory tool function
def get_user_preferences(user_id=None):
    if user_id:
        # Fetch preferences from storage using user_id as filter
        preferences = storage.get_preferences(user_id)
    else:
        # Default to current single-user behavior
        preferences = storage.get_preferences()
    return preferences

Notes

The implementation details may vary depending on the specific storage solutions (e.g., SQLite, Honcho/Mem0) and the existing codebase.

Recommendation

Apply the workaround by modifying the memory tool to include the user_id parameter, as it provides a clear solution to the issue of shared user preferences in multi-user scenarios.