How do you manage your notes and context with Claude?

Your post will be reviewed shortly. (ALL posts are processed like this. Please wait a few minutes....) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/ClaudeAI) if you have any questions or concerns.*

This one is very easy for me, I have everything in folders and I just tell Claude to go fetch information in a specific folder and lately Claude seems to know my progress in certain topics without me telling it to remember. However, to be on the safe side I create md files of things I need to continue working on and again send Claude to get context in those. I don’t know if I’m making sense

Yes, that makes sense! How do you manage it across different devices? Do you mainly use Claude on one device, or do you store everything in Google Drive ? Do you instruct Claude on when and how to update the Markdown files?

Claude is pretty smart if you tell it a few times to do something, next time you’re performing a similar task it asks you if you want to… for example update a document. So far all files are just on the desktop of my MacBook. Which Claude has helped to neatly organise. I only have Claude on my phone and my pc, since I have it on my phone, all my scheduled runs take place even when my PC is not on. I don’t have a Mac mini yet

notion works pretty well i do not really believe claude memory and I will use notion as my ontology for work and other things

I built (with Claude's help) my own MCP server. It's connected to my self-hosted Dokuwiki, Gitea and NAS. So at any time, I can ask Claude to check some source code, make some modification and commit it, update a document and save it on my NAS, or summarize an entire chat session and save it in my wiki for next time. It works great for me.

I have a knowledge/memory folder + document system where I run Claude from. I track projects, save raw files, have a log with the sessions saved, and also have a wiki for stuff I want to remember (durable knowledge). I ask Claude to update and maintain it. Not everything goes in there, just the most important guidelines and knowledge. I do keep separate folders with all the details for my company, my projects, etc. So I have some helper documents that keep track of changes and where goes what on my knowledge folder that points to these. I don't use MCPs. I rely mainy on APIs/CLIs. For example, if I'm ending a session, the AI will suggest to create a task and use my ClickUp CLI to create it so I don't forget (I have a /session-end skill I use for this). You ned to actively maintain it by running some linting once per month. It basically maintains itself.

Mind maps for architecture. Claude can read Freeplane mind maps directly. For AI-specific needs (e.g. bugfix list, patch notes, improvement plans, etc) I use .md documents, which are very easy to process by a LLM.

I got super stuck with this exact problem on very large projects. So I built a central API with DB to store all my plans, tickets, and decision making as different 'ticket' types in this project https://github.com/evanjt/docket with a CLI application that claude can query and find related information to build better context around each task. You can see progress on it or the UI of the API. Having this dependency graph between work also helps to build some better documentation and build on past features. It's still a big mess, and I'm refining it, but I'm finding the output quality has improved a lot. I can send out ultracode investigation tasks to find bugs, then report them all as work tickets: investigation (requires more in-depth research), bugs, and duplicate or dead code, all linked to each other, creating dependent tasks that don't start until another finishes etc. It gives me questions that I can work through later on that unblock tickets, and I can assign release versions to stage bugs for the future. Then, when I'm ready to work on something, I can use the /lead skill that will manage and dispatch other agents that will work on each item in its own worktree. I can't guarantee it helps you at all, as it's a bit opinionated. I'm still finding a lot of problems with this method and modifying it a lot -- for example, working in so many worktrees create an obscene amount of merge conflicts and commits. I would recommend that you send an agent to the repo to get a better understanding of how it works and see if it can work for you.