News for hackers. Stuff that matters.
Re: by zaterka on Tuesday November 10, 2026 @11:49AM (#50442899)
I've been trying different approaches to tackle agent memory across different sessions, without bloating context and increasing token spending.

I was using LLM Wiki for a while, it seemed to work well but when I decided to measure token usage, I ran into a surprising +23% in token usage (model was often double checking or query was finding more matches than intended). I also tried static graphs for codebase structure, like graphify, and saw a +5% increase in token usage in the same benchmark.

In the end, I created this hybrid solution, called wayfinder: https://github.com/zaterka/wayfinder

It's a simple rust application that build a knowledge graph on top of the LLM wiki, with metadata that helps the model navigate through the markdown files, tracking files that are up to date and the structural relationships inside the project. It also led to -30% token usage on the same benchmarks both LLM Wiki and graphify increased the token usage.

For managing context between different teams, I use my memory by project, so personal and professional work is kept separate, and I just reuse templates as needed (for agent prompts for example).

There are no comments on this comment yet.