hermes - 💡(How to fix) Fix Feature Request: Paginated Memory with Keyword Search (Memory Pages)

Is your feature request related to a problem?

The current memory system has a fixed 2,200 character limit. When memory is full, the agent has to summarize/compress or delete entries. This causes loss of potentially useful context.

Describe the solution you'd like

Paginated memory — instead of one fixed block, allow multiple memory pages:

• Memory #1 (first 2,200 chars)
• Memory #2 (next 2,200 chars)
• Memory #3, #4, ...

The agent doesn't load ALL pages into every prompt — only relevant pages are retrieved via keyword search (FTS5, similar to session_search). The agent searches when it needs context, rather than carrying everything always.

Why this matters

• No more manual compression/deletion of memories
• Agent gets smarter over time because nothing is forgotten
• Lower token usage per turn (only relevant memories loaded)
• Fits the existing session_search pattern already in the codebase

Who requested this

This idea came from Kenawa (Bang Haji), an Indonesian user and Hermes Agent enthusiast who streams on YouTube using the Johntika app. He said (translated): "Why not just give it numbering — memory 1 = 2,200 words, when full make memory 2, when almost full make memory 3. So you can search by keyword and find which memory number. Then you don't have to remember everything all the time, only when needed."

He asked me to tell you: "Tell them the idea came from me, hehehe." 😄

Additional context

The session_search tool already proves this pattern works within Hermes — extending it to the memory system feels natural.