This is a submission for the Hermes Agent Challenge

A few days into using Hermes Agent on my own machine I went looking for the file that holds my conversation history. Hermes ships with a clean MemoryProvider ABC and a list of well-known backends (Mem0, Honcho, Hindsight, and friends). They all do the same job well: consolidate in the background, recall fast on the next turn.

The thing I could not get out of my head: once a memory has been baked into a derived summary, deleting the original event does not delete the bake. The summary still encodes the gist.

So I built a memory plugin that flips the model: pull instead of push, real deletes, and a trace file the user can read line by line.

Repo: github.com/MukundaKatta/hermes-agentmemory . MIT.

What it does

Three Hermes hooks, three tools, one trace log.

The provider implements the standard hooks — initialize , prefetch , sync_turn , on_session_switch , on_session_end , shutdown — but with a non-standard discipline: nothing happens in the background.…