Does anyone here run a second brain alongside Claude day to day? Not a notes app you never open, but memory Claude actually reads. Here's how mine works, in case it's useful: - I keep a folder of small text files: one per client, one per project, plus a short index that Claude loads at the start of every session. Nothing fancy, plain markdown. - Every time I correct Claude twice on the same thing ("shorter emails", "never suggest meeting times without checking my real calendar"), that correction becomes one line in a file. It never makes that mistake again. - When a client replies after 3 weeks of silence, I don't re-read the whole thread. Claude already knows the history: what we agreed, what they objected to, what tone works with them. - The result: proposals, follow-ups and content come out in my voice with my context, instead of generic AI output. Setup time was basically zero. It's a living project that grows a little every day as you feed it with your daily work, one file at a time. By now, starting a session feels like talking to someone who's been in the business with me for months. Curious what others do: do you keep client or student context somewhere Claude can read, or do you re-explain your business every chat? What's working for you?

I kept using Claude for more and more of my work but had no idea which parts were actually burning tokens. Built a small routine that runs every morning and reports on my token usage from the day before. Breaks down where the spend went, flags anything that looks wasteful, tells me if I'm using a bigger model than a task actually needed. Nothing fancy, just a report and if something spikes I catch it same day instead of burning tokens without clue. Anyone else tracking their AI spend this closely? Or just checking the bill once a month ?