I got tired of Claude losing context every time a session ended, so I built a plugin that gives it a persistent, self-maintained notebook for each project.
What it does:
- Claude keeps its own notes on the project as it works (architecture decisions, gotchas, TODOs, etc.)
- Notes persist across sessions β no more re-explaining the same context every time you start a new chat
- Hooks into the Claude Code lifecycle to keep notes fresh and relevant automatically
- Lightweight, no external dependencies beyond Node
Repo: https://github.com/git-aditya-star/project-notes
Explainer page: https://git-aditya-star.github.io/project-notes/project-notes-explained.html
Would love feedback β especially if anyone tries it on a large/messy codebase and something breaks, or if the note-freshness logic feels off. Also open to feature requests.
(Full disclosure: I'm the author, sharing because I think others might find it useful.)
Top comments (2)
How did you handle note persistence across sessions in your plugin, and would you consider open-sourcing it? I'd love to swap ideas on this.
So, in the same project folder it creates notes, indexes them and passes on the index in each session. So that way all sessions can see the notes of different sessions in the repo. Its on github and opensource, please check the readme and page link for more details on installation