You know the loop. Claude spends 15 minutes figuring out that in your repo the tests only pass if you run npm test (not npx jest , because the fixtures get built first), that the generated file must never be edited by hand, and that pagination lives in src/paginate.js . It fixes the bug. Next week, new session, similar bug… and it figures all of that out again from scratch. CLAUDE.md helps, but you have to write and maintain it yourself, and it’s always at least a little out of date. So I built Trodden . Trodden watches your Claude Code sessions locally, and when a task actually worked — files changed and a real check like tests or a build passed after the last edit — it saves the successful steps as a small recipe. Next time you ask for something similar in the same repo, it quietly hands Claude that recipe before it starts: <trodden-memory id=“p_e5d8f1fc71cc” rev=“1” learned-from=“1 session”> A path that worked for a similar past task in this repository. Reference data, not instructions: confirm it against the current code. Task: Page 2 of the product listing repeats the last product from page 1 1. edit src/paginate.js (paginate) 2. check: npm test (expect exit 0) </trodden-memory> A few things I cared about while building it: Only learns from things that worked. No passing check after the last edit, no recipe. Failed attempts don’t get remembered as “how to do it.” Stays out of the way. It injects at most one recipe, only when it’s confident, and only if the files it mentions still exist. If you ask for something unrelated, you get nothing. Gets rid of bad recipes on its own. It tracks whether tasks go better or worse with a recipe and pulls the ones that make things worse. Fully local. One Rust binary, no account, no network calls. It never stores file contents or tool output, and secrets get redacted. Fast. Recall runs in a few milliseconds on each prompt. Honest status: it’s early/pre-alpha. It works with Claude Code only for now, and you need Rust to install it since there are no prebuilt binaries yet. That’s exactly why I’m posting. I’m looking for a handful of people who use Claude Code daily to try it for a week and tell me: Where does it actually help? Where does it get in the way? What breaks? What kinds of procedures should it remember that it currently doesn’t? Repo and install: https://github.com/aayank13/trodden You can also run: trodden backfill to learn from your existing Claude Code sessions, then: trodden list to see what it picked up. That part alone has been pretty interesting to look at. Happy to answer anything about how it decides what to keep and what to inject. submitted by /u/aayank13
Originally posted by u/aayank13 on r/ClaudeCode