recall measured on coding work: finding the session where a bug was fixed before, how much an agent reads to get there, and notes that keep up with the conventions you set. With 0.3.0's notes loaded at session start, an agent follows the latest conventions of a long MemoryCode history 65% of the time, against 45% with 0.3.0's search alone (held-out histories; one run and three). Method and numbers: docs/research/coding-memory-hillclimb.md.
recall eval swe-contextbench checks whether recall finds the past fix for a new GitHub issue among 300 real Claude Code sessions, by itself or through an agent using its tools. recall eval memorycode checks whether the nightly notes hold every coding convention you set, in its latest form, and whether an agent's code follows them. recall eval amb scores retrieval on agent-memory-bench. Each has a fixed train/test split, so a change is judged on cases it was not tuned on.recall eval search --v2, recall eval agent and recall eval memory --v2 score cases you write (questions and the chats that answer them, questions an agent must answer from past work, chats and the memories they should yield), with confidence intervals, paired comparisons (--against) and a results page per run. Answers and memories are graded by Claude Sonnet 5.5 against checkable claims.search_chats takes alternatives, other words for the same thing, and returns the best chats across all of them, each listed once.read_chat shows a long message's start, the passage that matches and its end (ask for one message to see it whole). An agent takes in an estimated 37% fewer Claude tokens per question on held-out SWE-ContextBench issues (about 9.0k against 14.4k, tool definitions included), and finds as much.alternatives. Codex and Cursor now get search results as compact text instead of JSON, 29% fewer characters per search over 481 logged searches.