LLM=True • Hacker News Board

Re: LLM=True

#151

Post by mrweasel » Thu, Feb 26, 2026, 8:06 AM UTC

jen729w wrote: post #150

mrweasel wrote: post #50

Earlier quoted context omitted.

That can be read in two ways: 1) It's only $100, well worth the money. 2) Surprisingly little value was provide for all that money.

I'm not sure how you'd read it the second way.

$100 per month is a lot of money, in that case "wow is that all?" must refer back to how little you got from it.

Re: LLM=True

#152

Post by jakub_g » Thu, Feb 26, 2026, 12:01 PM UTC

A potential problem I see with "LLM=true" being set by claude and friends is that some tools whose authors don't like LLMs might be tempted to e.g. don't output anything at all (and don't do what the CLI is supposed to do), out of principle, when they detect LLM is running things.

Just the (small) probability of this being true might be enough for the big players to not consider creating that var. (Although, if it's easy enough to unset it, then maybe not an issue).

Re: LLM=True

#153

Post by wizzwizz4 » Thu, Feb 26, 2026, 12:35 PM UTC

mikkupikku wrote: post #76

lelanthran wrote: post #71

Earlier quoted context omitted.

That's not specific to unix though.

I didn't say it was, but I simply don't care what problems any other kind of system has because they aren't my problems. Last time I had windows on any of my computers it was windows 98.

With the right DOS flags, Windows 98 had pretty well standardised on /?. Of course, when you changed those flags, some programs would stick with their hardcoded /?, others would change to -?, and yet others would just fall over.

Re: LLM=True

#154

Post by adwn » Thu, Feb 26, 2026, 1:52 PM UTC

sgarland wrote: post #140

adwn wrote: post #114

Earlier quoted context omitted.

"Finished conversion of xyz.mp3 to xyz.ogg" is valuable progress information to a regular user, not just to developers, so it belongs in INFO, not DEBUG.

I suppose this is subjective, but I disagree. If I want to know the status of each item, I’d pass -v to the command. A simple summary at the end is sufficient; if I pass -q, I expect it to print nothing, only issuing a return code.

> If I want to know the status of each item, I’d pass -v to the command.

I don't disagree. In my opinion, the default log level for CLI applications should be WARN, showing errors and warnings. -q should turn this OFF (alternatively, -q for ERROR, and -qq for OFF), -v means INFO, -vv DEBUG, -vvv TRACE. For servers and daemons, the default should probably be INFO, but that's debatable.

Re: LLM=True

#155

Post by nrds » Fri, Feb 27, 2026, 7:34 PM UTC

skerit wrote: post #54

> Then a brick hits you in the face when it dawns on you that all of our tools are dumping crazy amounts of non-relevant context into stdout thereby polluting your context windows. I've found that letting the agent write its own optimized script for dealing with some things can really help with this. Claude is now forbidden from using `gradlew` directly, and can only use a helper script we made. It clears, recompiles…

> This works so much better.

Pi coding agent does this by default with all outputs but Claude (all versions tested, including opus 4.6) just completely ignores this capability. Even when the tool output explicitly tells the agent that the full output is saved in a particular file, Claude reruns the command.