Earlier this year, a piece called “Software Forgets: Agent Traces Are the Memory” argued that coding agents already generate the record we keep losing. Every search, error, documentation read, and abandoned approach leaves a trace of not just what changed, but why. The diagnosis was right, but traces alone are just an archive. You can’t grep ten thousand turns and expect to surface “why did we move off the streaming parser?” For an agent to actually use those traces while working, they need indexing, retrieval, ranking, and provenance.
That’s the gap funes is trying to fill. It’s a durable memory layer for Claude Code, Codex, pi, and Hermes, built from the sessions already sitting on your machine. Installation is a single binary via a curl command, and one funes add claude (or codex, pi, hermes) builds the first index, gives the agent recall and get tools, and sets up automation to index each completed turn incrementally. When a task touches a past decision or rationale, the agent reaches for recall on its own and names the session behind its answer. Results return the original text with exact provenance—agent, timestamp, session, turn—plus a get command to open the full context.
Under the hood, a deterministic pipeline parses supported traces into a consistent turn-and-block shape, chunks them, embeds with a pinned local model, and writes to a local Lance dataset. Queries combine vector and BM25 search, fuse rankings, rerank with a cross-encoder, reweight by recency, and attach neighboring chunks. Nothing is distilled into facts at write time, so raw evidence stays intact. And it’s local by default: no account required, embedding and reranking happen on your machine, and your coding agent does the reasoning.
Memory gets more interesting when it follows your work across machines. Binding a Hugging Face dataset with funes add codex acme/funes-memory publishes your memory there—private by default—and keeps it current at session boundaries. Credentials are redacted during indexing, and publishing scans every chunk again for anything that still looks like a secret. The Hub supplies ownership, access control, versioning, and distribution. Your memory doesn’t become an account in a separate memory service, and you don’t rent it back through an API. There’s also funes ask, a read-only sibling for putting direct questions to a memory yourself, with a published memory of funes development available to try without creating your own.
