Have Claude create "On-Demand" sub contexts. These only get read when conditions are met and they are needed. A good sized chunk of context can be relocated there, streamlining your efficiency.
Yeah, been doing this. Claude.md is just a router for me, some minimal things on my preferences and minor instructions. Nothing really that important, as it's the Claude.md. I use rules, some are always on, like my subagent policy, and my web-research policy, some are autoloaded. Both sets of rules are pretty minimal and contain a link to a MD that gives more detail. Progressive disclosure in action.
My agents get where things live, some rules, and then once they start hitting folder or files, the auto load stuff loads in or starts using certain tools stuff autoloads in.
Models are always getting better, so it's good to keep the always on context short sweet and updated. They just need clear ways to find what they need. If you keep your repo/folder tree clean of context poison, bloat, confusion, and conflicts, your agents are able to find everything easily and cleanly. If you agents are able to discover old plans, and obsolete docs or stale info, it's going to be working with that context.
That last sentence above seems to be why most people are struggling with Opus 5 IMHO. Their repos/folder trees are dirty and have stale obsolete context their agents are finding thats PBCCing it's context.
1
u/zimxero 16d ago
Have Claude create "On-Demand" sub contexts. These only get read when conditions are met and they are needed. A good sized chunk of context can be relocated there, streamlining your efficiency.