(I’m building memU, and this is part of why. I’m not trying to present it as a neutral comparison, just share my workflow here) After a few months with cc, my CLAUDE.md had become a junk drawer: the problem is that these notes have different scopes. A rule about this repo should load every time. A lesson from one weird incident probably should not. A workflow I use across several projects definitely should not be trapped in one project’s instructions. This is the split I’m trying now: CLAUDE.md - How to work in this repo - Commands, conventions, constraints, architecture rules - Things the team should share Claude Code project memory - Short, project-specific lessons - “Run this migration before the backfill” - “This integration test flakes when X happens” Personal memory (memU) - My preferences, decisions, recurring workflows, and lessons - Things that should survive a new project, machine, or agent Like, I’ve got this rough process for debugging stuff in production, right? It’s usually like, narrow down the time, check logs, figure out how to roll back, then actually change things. That’s not really tied to one specific repo though. I wanna keep using that even if I jump from Claude Code to Codex, or if I’m working on a different machine. But I also don’t want every old note shoved into every single prompt, you know? So the idea isn’t to make the agent remember everything . It’s more about keeping the always-loaded context small, and only pulling in older stuff when it’s actually gonna help. I’m kinda thinking it breaks down like this: Stuff about the codebase stays with the codebase. My own personal knowledge, that should follow me around. memU is what I’m trying for that second part. It’s like, a personal wiki I can actually look at, that can bring useful context with me across different agents and devices. It’s all open-source too, Apache 2.0. submitted by /u/Pure_Bend5514
Originally posted by u/Pure_Bend5514 on r/ClaudeCode