hermes - 💡(How to fix) Fix session_search becomes very slow on long sessions because it appears to read and summarize the entire session [1 participants]

Hi, I want to report a usability/performance problem with session_search.

I am not a programmer, so I may not describe the internals perfectly, but the user-facing problem is very clear:

When a conversation session becomes long, session_search can take a very long time. In my case, I have some sessions with 800+ messages, and searching past conversations becomes slow enough that it feels stuck.

From the user side, this feels unexpected because "search session history" sounds like it should behave like a fast history search. But in practice, it seems that after finding matches, Hermes may read and summarize too much of the full session, which becomes expensive on long conversations.

Why this matters: Non-programmer users may keep very long sessions without knowing this will hurt recall/search speedThis is likely not just my issue; many normal users probably have long sessionsThe problem is hard to report clearly unless someone inspects the implementationUsers may think the model is broken, frozen, or unreliable, when the real issue is the search strategy on long sessions Suggested improvements: Add a fast/default mode for session_search that only uses matched snippets plus nearby context firstAvoid reading the entire session transcript by default for very long sessionsOnly do full-session summarization when the user explicitly asks for a deep recapAdd safeguards for very large sessions (message-count or token-based limits)Make the UX clearer about whether this is "fast search" or "deep summary" Expected behavior: session_search should stay responsive even for very long sessionsLong sessions should degrade gracefully instead of becoming extremely slow Actual behavior: On long sessions (for example, 800+ messages), session_search can take a very long time This seems especially important for non-technical users, because they are less likely to know they should manually split sessions or work around the issue.

Thanks.