We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient.
While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching. This was ideal for our use case but trying to manage these rules by hand was already not working and would be even harder with more granular, targeted rules.
CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion patterns, and generates targeted rules with proper scoping. You review and approve everything. Dashboard for auditing, a background-agent review process so nothing goes stale as code changes, tracking of everything lives in a simple file in git.
How to Get Started:
Install: npm install -g @codeyam/codeyam-cli@latest
Then from your project root run: codeyam
This will launch a dashboard with further instructions for initializing CodeYam Memory.
Free, runs locally, no login required, and language agnostic. Would love feedback.
More context:
Background blog post: https://open.substack.com/pub/codeyam/p/introducing-the-code...
90 sec demo on our own repo: https://youtu.be/oJ2gTb-lxbE
Demo teaching Claude a real OSS repo (Plane): https://youtu.be/CjOKBwBCcOs
Website: https://codeyam.com/
I struggle a lot with Claude's non-existing short term memory. This should help a lot
Awesome! An Alzheimer's remedy for my Claude. Look forward to taking this for a spin.
Cool concept! How exactly does this integrate with Claude Code?
excited to try this out - our team is building agentic outreach workflows and remembering context from past outreach is key to what we do
eager to see if this can help us
congratulations on shipping. Do you feel like Claude will ever roll this into their own roadmap?
Hey HN! I’m Nadia, one of the builders. Happy to answer anything.
Some context on what “rules” are for people who haven’t seen them: Claude Code has a built-in system for structured context beyond claude.md files. Rules support path matching (apply context only to specific files/directories), scoped organization, and structured formatting.
We have been running CodeYam Memory on our own repo for the past few weeks. The main difference we see is fewer repeated mistakes and less manual context maintenance. It’s still early, but it has meaningfully improved how we work with Claude Code.
If discussion gets too long for HN threads, we also have a Discord for questions and feedback: https://discord.gg/eFPUs7CeFw