hermes - 💡(How to fix) Fix [Feature]: session_search source filter — support cross-platform session recall [1 comments, 1 participants]

Problem or Use Case

Users who alternate between multiple platforms (e.g. CLI + Feishu + Telegram) cannot effectively recall past conversations via session_search.

The recent mode (no query) returns sessions sorted purely by started_at DESC. When one platform has high session density (e.g. CLI), it dominates the top-N results, completely hiding sessions from other platforms.

Example: a user with 10 CLI sessions and 1 Feishu session on the same day, with limit=3, will only ever see CLI sessions — even though the Feishu conversation may be more relevant.

Proposed Solution

Add an optional source parameter to the session_search tool:

{
  "source": {
    "type": "string",
    "description": "Optional: filter by session source platform. E.g. \"cli\", \"feishu\", \"telegram\". Use \"all\" or omit to search across all platforms."
  }
}

Changes needed:

1. tools/session_search_tool.py — add source parameter to session_search() and _list_recent_sessions(), pass it through to db.list_sessions_rich(source=...)
2. SESSION_SEARCH_SCHEMA — add the source property to parameters
3. run_agent.py — pass source from function_args through to the handler (both call sites ~line 7516 and ~line 8021)
4. hermes_state.py — list_sessions_rich() already supports source filtering, no changes needed

Alternatives Considered

• Per-source separate calls: would require multiple session_search calls and manual merging, wasteful
• Group results by source in the response: useful but still needs a filter param for targeted searches

Feature Type

Gateway / messaging improvement

Scope

Small (single file, < 50 lines)

Debug Report

• Hermes Agent v0.10.0
• Platforms in use: cli, feishu