commonshell

Does memory help coding agents work faster?

commonshell research note · 13 November 2026 · draft for review

Summary

Coding agents start each session without memory of earlier ones. They repeat failed approaches and look up answers they already have. Published work on agent memory reports gains on benchmark tasks, and some reports show lower latency and fewer tokens when retrieval stays selective. Our own measurements do not yet show a speed-up. The experiment that would settle it is set out below.

What the published work reports

Figures are as reported in each paper's abstract or secondary summaries. We are checking them against the source tables.

SystemMemory formReported result
Reflexion (2023)Verbal reflections on failed episodesBetter success on coding and decision tasks without weight updates
Voyager (2023)Library of reusable, verified skillsFaster learning in Minecraft than a baseline starting from scratch
ExpeL (AAAI 2024)Experience pool and extracted insightsHotpotQA: 39% success against 28% for ReAct. Insights alone (36%) beat past trajectories alone (31%)
Mem0 (2025)Extracted facts with add, update and deleteLOCOMO: about 26% relative quality gain over OpenAI's memory; about 91% lower p95 latency and over 90% lower token cost than full-context prompting
Zep / Graphiti (2025)Temporal knowledge graphLongMemEval: up to 18.5% accuracy gain and about 90% lower latency

Three findings carry over to coding work. Distilled lessons help more than replaying past runs. Retrieval must stay small, since the speed and cost gains come from fetching a few facts rather than the whole history. Facts go stale, so a memory needs a way to supersede them.

These are question-answering and simulation benchmarks, not repository tasks with tests. They show the mechanism works; they do not predict gains in coding.

What we have measured in Commonshell Pilot

Our harness compared the same scenario before and after a rework of research reuse:

RunRequestsPromptsRequests per promptContext readLookups skipped
Before47152.70.93M tokens0
After45162.80.98M tokens0

The two runs are the same within noise, and neither exercised the reuse path. Earlier end-to-end cases showed the intended behaviour: a proven research answer caused zero repeat lookups and cited its date and source. That is evidence the mechanism works, not that it saves time. We do not yet measure failed attempts avoided, which matters most.

The experiment we are running

The claim to test is: with recalled learnings, a coding agent completes the same tasks with fewer requests, fewer tokens and fewer repeated failures.

We will publish the results here, including if they are negative.

Limitations

References