LLM=True
blog.codemine.be
LLM=True
1–10 of 155 posts
Re: LLM=True
#2I never considered the volume of output tokens from dev tools, but yeah, I like this idea a lot.
Re: LLM=True
#3great idea. thought about the waste of tokens dozens of times when I saw claude code increase the token count in the CLI after a build. I was wondering if there's a way to stop that, but not enough to actually look into it. I'd love for popular build tools to implement something along those lines!
Re: LLM=True
#4could we not instruct the LLM to run build commands in a sub agents which could then just return a summary of what happened?
this avoids having to update everything to support LLM=true and keep your current context window free of noise.
Re: LLM=True
#5Speaking of obvious questions. Why are you counting pennies instead of getting the LLM to do it? (Unless the idea was from an LLM and the executive decision was left to the operator, as well as posting the article)
So much content about furnishing the Markdown and the whatnot for your bots. But content is content?
Re: LLM=True
#6could we not instruct the LLM to run build commands in a sub agents which could then just return a summary of what happened? this avoids having to update everything to support LLM=true and keep your current context window free of noise.
That would achieve 1 of the 3 wins.
Re: LLM=True
#7This is merely scratching the surface.
LLMs (Claude Code in particular) will explicitly create token intensive steps, plans and responses - "just to be sure" - "need to check" - "verify no leftovers", will do git diff even tho not asked for, create python scripts for simple tasks, etc. Absolutely no cache (except the memory which is meh) nor indexing whatsoever.
Pro plan for 20 bucks per month is essentially worthless and, because of this and we are entering new era - the era of $100+ monthly single subscription being something normal and natural.
Re: LLM=True
#8This is merely scratching the surface. LLMs (Claude Code in particular) will explicitly create token intensive steps, plans and responses - "just to be sure" - "need to check" - "verify no leftovers", will do git diff even tho not asked for, create python scripts for simple tasks, etc. Absolutely no cache (except the memory which is meh) nor indexing whatsoever. Pro plan for 20 bucks per month is essentially worthles…
codex seems chill
Re: LLM=True
#9could we not instruct the LLM to run build commands in a sub agents which could then just return a summary of what happened? this avoids having to update everything to support LLM=true and keep your current context window free of noise.
That would achieve 1 of the 3 wins.
Probably the main one, people mostly complain about context window management rather than token usage
Re: LLM=True
#10This is merely scratching the surface. LLMs (Claude Code in particular) will explicitly create token intensive steps, plans and responses - "just to be sure" - "need to check" - "verify no leftovers", will do git diff even tho not asked for, create python scripts for simple tasks, etc. Absolutely no cache (except the memory which is meh) nor indexing whatsoever. Pro plan for 20 bucks per month is essentially worthles…
>LLMs (Claude Code in particular) will explicitly create token intensive steps, plans and responses - "just to be sure" - "need to check" - "verify no leftovers", will do git diff even tho not asked for, create python scripts for simple tasks, etc. Absolutely no cache (except the memory which is meh) nor indexing whatsoever.
Most of these things can be avoided with a customized CLAUDE.md.