Measured from actual use

How many tokens Durmem can save.

A closer look at real Codex and Claude sessions—and the work agents could avoid with shared memory.

Study period: September 10–17, 2026

What happens when an agent can find the decisions, facts, and instructions a project has already established? It can spend less time searching, repeating work, and recovering from mistakes.

We studied actual Codex interactive sessions, Codex automated sessions, and Claude automated sessions. We then ran controlled comparisons without Durmem’s saved context to estimate the work those same sessions would have needed. The ranges below show conservative and realistic estimates.

The results at a glance
57.8%–82.5%estimated reduction in total token useIncluding tokens used by Durmem
16.6×–54.7×estimated tokens saved per Durmem tokenAcross all three session types

Across the observed sessions, the work used 82.1 million tokens with Durmem, including the 7.2 million tokens Durmem itself used. The estimated equivalent without Durmem was 194.7 million to 468.4 million tokens. These results describe the sessions in this study.

The savings, by session

Each row shows actual total tokens used with Durmem and the estimated total for the same work without it. The final two columns turn those estimates into a reduction.

Reduction in total token use

Swipe to see all columns on a small screen.

Session typeWith DurmemWithout, conservativeWithout, realisticReduction, conservativeReduction, realistic
Codex interactive27,675,21877,886,608199,011,68464.5%86.1%
Codex automated33,018,06473,339,623172,556,98155.0%80.9%
Claude automated21,430,39443,489,64996,874,05150.7%77.9%
Combined82,123,676194,715,880468,442,71657.8%82.5%

What each Durmem token made possible

The study also compared Durmem’s own token use with the work it helped avoid. Across all three session types, each token Durmem used corresponded to an estimated 16.6 to 54.7 tokens of avoided work.

Tokens saved for each token Durmem used

Session typeDurmem tokensSaved, conservativeSaved, realisticPer token, conservativePer token, realistic
Codex interactive3,526,21953,737,609174,862,68515.2×49.6×
Codex automated2,309,85242,631,411141,848,76918.5×61.4×
Claude automated1,362,74323,421,99876,806,40017.2×56.4×
Combined7,198,814119,791,018393,517,85416.6×54.7×

Where the savings came from

Shared context helped in five ways. These categories divide the same estimated savings shown above; they are not additional savings. Durmem Kanban also automates the production release, acceptance, and monitoring workflow, with the operator making decisions and giving approvals where required.

Reusing facts and instructions

Already-established knowledge reduces repeated code and history searches, experiments, and questions.

5,939,295–17,644,658estimated tokens saved

Preventing unsafe or unapproved actions

Decisions and limits reach agents before they act, helping them avoid work that was rejected, postponed, or not approved.

2,136,570–10,140,322estimated tokens saved

Avoiding duplicate or outdated work

Agents see what was already completed, disproven, or replaced instead of starting over from old assumptions.

17,917,177–66,593,375estimated tokens saved

Preventing release and multi-computer mistakes

Shared release requirements and computer-specific test evidence help agents avoid incomplete releases, repeated diagnosis, and platform failures.

55,771,770–177,455,635estimated tokens saved

Avoiding invalid measurements and reruns

Shared study definitions, procedures, and known issues help agents avoid repeating invalid analysis.

38,026,206–121,683,864estimated tokens saved

How we measured it

1

Start with actual use

Examine real interactive and automated Codex sessions and automated Claude sessions.

2

Replay representative cases

Run controlled comparisons without saved context and observe searches, unnecessary work, and questions to the user.

3

Apply results to similar cases

Count related lookups supporting one decision once, so the same benefit is not credited multiple times.

Less rediscovery. Fewer repeated mistakes. More room for the work that moves the project forward.

The conservative estimate values avoided work cautiously and limits credit for each decision. The realistic estimate also accounts for the time serious release, implementation, and measurement mistakes can consume. The figures are estimates for the observed sessions, not a company-wide projection.

Give your agents a shared memory.

Help your team pick up where it left off and keep moving together.

Explore Durmem →
Total-token reduction compares the estimated tokens without Durmem with the tokens used with Durmem, including Durmem’s own use. Savings per Durmem token compares estimated avoided-work tokens with Durmem tokens used. Read the original study PDF.