The latest articles on DEV Community by Yehuda Frankel (@yehuda_frankel_0157cf0a82). https://dev.to/yehuda_frankel_0157cf0a82 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3842337%2Fa1a50f63-94f5-48e5-8f93-ee4200faf0d8.jpg https://dev.to/yehuda_frankel_0157cf0a82 en Yehuda Frankel Wed, 25 Mar 2026 00:31:36 +0000 https://dev.to/yehuda_frankel_0157cf0a82/i-got-tired-of-re-explaining-my-codebase-to-claude-every-session-so-i-built-a-memory-system-that-53be https://dev.to/yehuda_frankel_0157cf0a82/i-got-tired-of-re-explaining-my-codebase-to-claude-every-session-so-i-built-a-memory-system-that-53be <p>very time I started a new Claude Code session I went through the same ritual.</p> <p>What's my stack? What files matter? What approach did we decide against last week?<br> Claude had no idea. I'd spend 10-15 minutes just getting it back up to speed.<br> Every. Single. Session.</p> <p>So I built Claude Recall.</p> <h2> What it actually does </h2> <p><strong>Memory that stays accurate</strong></p> <p>Most memory tools go stale — you document once, code moves on. Claude Recall <br> runs a drift detector after every file edit. It compares live code against what <br> Claude has in memory and flags undocumented changes automatically.</p> <p>First run on my project caught 21 undocumented functions Claude had no idea existed.</p> <p><strong>Skills that patch themselves</strong></p> <p>Every built-in skill scores itself — did it need correction? Run /evolve every <br> few sessions and it rewrites the failing steps using your actual failure data. <br> The same mistake becomes architecturally impossible after /evolve runs.</p> <p><strong>Autonomous operation</strong></p> <p>Skill chaining, self-healing on verify failure, session journal auto-captured <br> on every response. Claude works through multi-step tasks without human <br> checkpoints between each step.</p> <h2> Real numbers </h2> <p>Tested across 119 real sessions on a production codebase — legacy Java backend, <br> 100+ functions, scheduler, email system. Not a demo project.</p> <ul> <li>Sessions crashed mid-task — Start Session recovered every time</li> <li>Skills patched themselves — the same failure never happened twice </li> <li>21 undocumented functions caught on first drift detection run</li> <li>velocity.md reached 30+ entries — estimates now reflect real track record</li> </ul> <h2> No API keys. No database. No background service. </h2> <p>Plain markdown files + Python scripts. MIT license.</p> <p>GitHub: github.com/YehudaFrankel/claude-recall</p> claudecode ai productivity tooling