| This is a bit off-topic, this repo isn't even .NET. I work with a very large ( 280+ project ) .NET semi-monolithic semi-services code base with internal nuget packages. I've only a handful of times hit the limits on a team plan and even then only minutes before the window refreshes. I'll chime in with some of my workflow and tips when I have a more appropriate place to do so as it feels disrespectfully off-topic to elaborate further here about too much .NET specific. As a general tip for working with large code-bases, if you have: /docs
/src
/src/projectA
/src/sub-projectB
/src/sub-projectC
/src/sub-sub-depdencyD
/tests/
etc.Then don't just run claude at the root directory (/). Run it in ./src/projectA and then use /add-dir to bring in only the depenedencies you care about for the problem you're working on. Or even run it in /docs and then bring in just the places where it needs. It will prompt to ask to read from / semi-often, but you can just deny it, either explicitly through claude.settings.local, or just through a prompt for that action. By carefully controlling the scope, you limit what it tries to read. If you catch it trying to read from /sub-project-B and you think it's irrelevant, you can not just deny it, but ask it why it thought it wanted to read from it, and then update your documentation (or your priors) appropriately. I've found the worst time for just blowing through credits / usage is when I hit a problem that's just not solvable, but more on that another time. |
Anyways, I do appreciate the tips. I am going to attempt to not use Sonnet 4.5 for planning and see if opus does a better job of limiting scope.