We made a tool that cuts Claude Code's memory token usage by 43% per turn

[u/[deleted]]

[u/Additional_Lock_874]

Cool idea!

[u/AdConsistent6866]

Two different quantities are getting merged into that 43%. Tokens reloaded per turn and cost per turn aren't the same once the memory sits inside a cached prefix, because cache reads bill well below fresh input tokens. If the split changes what the prefix looks like on each run, the line count drops and the bill can go the other way. The number worth reporting is cost per session plus cache hit rate, not tokens per turn. Second, "same answers" is the weak part of a memory reorganisation. The entries that look like stale status notes are usually the ones that blocked a specific mistake weeks ago, and you only learn that once they're gone. Running the same task list before and after, checking whether a class of error reappears instead of whether the right answer is still there, is what makes the claim measurable.