i tried 6 ways to share context between claude sessions. the one that stuck wasn't a feature.

part-time B2B consultant, 8 active clients. context is my entire job.

i kept losing context between claude sessions. tried:

1. dump it all in a custom instruction (gets too long, claude ignores half)
2. start each chat with a 4-paragraph context block (worked but cost me 5 min each time)
3. paste a "context.md" at the top (worked but i kept forgetting to update it)
4. claude memory (good but felt like i couldnt verify what was in it)
5. claude projects (good but you cant move chats between projects easily)
6. a personal claude skill that loads my standard context

what actually stuck: a single context.md file per client, version-controlled in a github repo i maintain. before any session about a client, i paste the latest context.md into claude. takes 10 sec.

the unsexy reason it works: maintaining the context.md forces me to actually think about what i know about each client. the act of curation is the value.

claude memory is great when the context is small. claude projects is great when the context is big and stable. for client work where context shifts weekly, the markdown file in a repo is somehow still the right answer.

curious if anyone else has converged on something similar or if im missing a better workflow.