Rate limiting has not been a problem for me. I need time to review the proposals, the actual source code and to meddle with it in between
One must also always be aware that an LLM WILL ALWAYS DO what you ask it for. Often you ask for the wrong thing. And you need to rethink.
Maybe I am inefficient though I really only use at the most two additional work trees at the same time.
> ... LLM WILL ALWAYS DO what you ask it for.
What? That's not my experience at all. Especially not "always"
Yes, yes they do. If you ask it to refactor something and integrate it somewhere else; it will do exactly that even if in the course of it you would find that that would dramatically increase complexity not reduce it.
I cannot count how many times that or something like that has happened to me.
Most of the time, maybe. Absolutely not always. I'll tell it to "implement feature a, ignore typescript errors". And it happened multiple times for me that it did the exact opposite, fix TS errors, and feature is barely mentioned in the response. Or more recently (with deep research) "Give me list of {some_product_name}, make absolutely sure to make a CSV and output a CSV. Columns are a,b,c,..". Does it give me the data? No, I get a wall of text with absolutely no data. Ok, you may argue this is some agent, etc. but user may not see a difference.
Don't take me wrong, I'm a big fan and constant user of all these things, but I would say it frequently have problem following prompts.
Or reduce complexity: https://xkcd.com/221/
If I hit the rate limit in 2 hours and got value out of each prompt I ran, that's better than doing the same amount of work in 6 hours and not hitting the limit.
Personally, I'm running 2 accounts and switching between them for maximum productivity. Just as a function of what my time is worth it is a no brainer.
Having a nice way to manage the work trees sounds great, but the rate limiting still sounds like an issue to this approach.
https://docs.anthropic.com/en/docs/claude-code/common-workfl...