Oh it does... but what happens after 6 months is an entirely different story.
A codebase that has exploded in size 2-3 times in just a few months,... internal architecture that is not layers of simple parts anymore, but, layers of complex architectures corresponding to individual agentic runs,... a codebase that now has 10 times more if-else and individual codepaths because you were not clear enough in your requirements, and used the phrase "handle all cases",... a codebase that neither you, nor anyone else now understands properly, thus, can't comment on what's possible anymore, and and at what costs when your manager or PM asks,...and finally, due to combined effect of these, a need for an ever increasing token budget, and constantly increasing fragilty of new AI-generated code due to repeated context compactions.
And we haven't even touched on the security and performance elements yet.
The right way to use these tools is to use them as, what I like to call, "code-monkeys". You tell them exactly what you want, where you want, how to do it, and how to architecture it, and more.. and then make them code.
Some years ago I toyed with the idea of running a minecraft server inside github actions,
I used tailscale to create a public endpoint and saved the world in an artifact that was re-loaded on the next run. It worked really well, but the point was never to actually use it for real.
Different companies and websites will very often have TOS's that contradict each other. TOS is contract law, so any single TOS only represents that one company's interests.
> Where did the litellm files come from? Do you know which env? Are there reports of this online?
> The litellm_init.pth IS in the official package manifest — the RECORD file lists it with a sha256 hash. This means it was shipped as part of the litellm==1.82.8 wheel on PyPI, not injected locally.
Same here, the API calls have always been heavier for me than the storage costs. It of course depends upon each use case, but this is overall a win for how I've been using it.
Even with the storage increase, still way more affordable than S3 or many of the other alternatives out there.
reply