Five things to check your agent memory store againstAn agent-memory bug can look nothing like one. It looks like confidence: the agent remembers an old address, keeps a preference the user changed months ago, or retrieves a fact that should have expire22KSep 1 · 10 min readsovantica.hashnode.dev
A LongMemEval-S number you can reproduceWe held off on posting a benchmark for a long time. Not because we didn't have runs - because most memory benchmarks you read are a number with no way to check it. A blog says "X%", and you have no idAug 27 · 8 min readsovantica.hashnode.dev
What our coverage number did not protectEngrava's test suite had 3,845 tests and 94.22% line coverage. There was more test code in the repository than production code. By every number we had, the thing was well tested. Then we ran a mutatioAug 24 · 9 min readsovantica.hashnode.dev
Engrava 0.5.0: a first-class MCP serverEngrava 0.5.0 pulls the MCP server out of the library. Install engrava now and you get the memory library and nothing else. The server ships separately, as engrava-mcp. The two were never really the sAug 22 · 3 min readsovantica.hashnode.dev
Action Records: Memory for Things an Agent DidMost agent memory examples start with facts: a user preference, a summary, a document chunk, a note extracted from a conversation. Those are useful, but they leave out a large part of what an agent acJul 20 · 5 min readsovantica.hashnode.dev
