Give Your Coding Agents a Memory You Own

Hugging Face add memory to the agent you already use A memory is a dataset, not a service Ask first, wire later Switching agents without losing the thread The cheapest way out of a long session Stop starting from zero Built on open source I work across several machines, and I switch coding agents depending on the task. Every one of them meets my projects as a stranger.

The reasoning from “last Tuesday” disappears when the session ends. Each new agent, on each new host, starts from zero. Earlier this year, Software Forgets: Agent Traces Are the Memory made the case that coding agents already produce the record we keep losing. As they search a codebase, try approaches, hit errors, read documentation, and change direction, they leave behind a dense account of not just what changed, but why. While the diagnosis is correct, traces are only potential memory. The session logs of an agent are still just an archive. You cannot grep your way to “why did we move off the streaming parser?” across ten thousand turns. For an agent to use those traces while it works, they need indexing, retrieval, ranking, and exact provenance. That is what funes provides. It is a durable memory layer for your agents (Claude Code, Codex, pi, and Hermes). It is built from the sessions already on your machine. It works locally and becomes part of your agent’s normal workflow with one command. When you want it to, it can also travel to a Hugging Face dataset you own, private by default. funes is a single binary. Its default inference backend has no ML runtime dependency, and embedding and reranking happen on your machine.