The new “concise” output option that just shipper in Claude Code seems to help.
Vomit: Clean up Claude 5's token output with a separate LLM
231–240 of 315 posts
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#232Earlier quoted context omitted.
Kind of both. On the one hand, it is “verbose” in the sense that it will tell me every little nit that it can think of while doing a task, it will tell me a narrative about its thought process, and it will tell me every other detail it can think of. But it does so in a way that tries to be incredibly dense to the point that I have to struggle to figure out what it is saying. I wonder if there are any “legibility benc…
I quite like https://surgehq.ai/benchmarks/hemingway-bench
I wish this had non-model comparisons. If Opus 5 is in the top ten, it’s clear that the entire benchmark is somewhere between “Tom Clancy” and “Dan Brown” and about 1,000 new model releases away from Hemingway.
When you see, “Wow, Fable is number one”, you might think it’s a good writer, but that’s not what the benchmark says.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#233Re: Vomit: Clean up Claude 5's token output with a separate LLM
#234Earlier quoted context omitted.
Honest take, you genuinely forgot to flag the flags ...
I'm going to be honest with you, I've hacked the pentagon and used their super computer to complete your todo list.
[And this folks is the true reason we are out of ammo in the middle east ...]
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#235Earlier quoted context omitted.
I asked Claude to do the following: > hello i would like to configure a new output style for you. it should keep the coding instructions (as you will still be coding!) and otherwise produce the same output, but with two new caveats. first, long detailed replies are still permitted, but if employed they must end in a bullet pointed summary whose points are all brief; if the summary attempt ends up not being so brief,…
I've noticed that most people seem to consider the core problem of Claude's output as "too verbose" but I don't think this actually cuts to the heart of the matter at all. It's almost, in some weird way, the opposite: like the text is far too _dense_. It tries too hard to invent odd terminology to try to condense stuff, but it doesn't tell you up front that it is going to call your company wide error-handling mechani…
Exactly, it’s absurdly dense, it’s almost impossible to follow. An it always omits the subject of each sentence.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#236Earlier quoted context omitted.
Claude is the Deepak Chopra of computer programming. Reviewing PR's created by it is 90% digesting the meaningless word salads in the comments, and the rest is figuring out that it has nothing to do with the code it is commenting.
Because it is somehow incapable of separating the conversation with its human operator from the code it is generating and commenting on. Incidentally, this is also why prompt-injection works. No one wants to know about the three other approaches tried when reading the first sentence of a function's documentation. No one cares that the implementation was planned in six phases and "Phase 3" will implement this interfac…
Spot on
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#237I feel like Opus 5 is going to need a postmortem once they figure out what makes it so obnoxious. It's clearly something like an artifact of getting the model to reach deeper for tokens, possibly because it has some positive impact on coding and/or tool calling. But man is it bad for general communication, like borderline unusable.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#238I've been grappling with this for weeks, not just in Claude but in Codex as well, which isn't quite as bad but still annoying. AGENTS.md does very little, agents will consistently violate the communication preferences, especially as the session drags on. It's incredible to me that there's no good way to reliably change the way an LLM responds to you that a workaround like this would even be necessary. It seems like s…
I’ve been using this skill:
https://github.com/luchasarie/bro-skill
but I still can’t understand what Claude wants to say when solving complex problems.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#239I like the "Claudish to English" name better. https://github.com/gvzdv/claudish-to-english
The funniest part is that that project's own readme includes lots of good Claudish. > If CLAUDISH_MODEL names a model you have not pulled, every rewrite is skipped — with the one-time notice above.
Was gonna say that, the README is unreadable
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#240I've been grappling with this for weeks, not just in Claude but in Codex as well, which isn't quite as bad but still annoying. AGENTS.md does very little, agents will consistently violate the communication preferences, especially as the session drags on. It's incredible to me that there's no good way to reliably change the way an LLM responds to you that a workaround like this would even be necessary. It seems like s…
I'm probably going to be going against the grain here, but I think it's not as bad as it looks at first. I was similarly frustrated a few months ago, but have noticed I've started to learn the idiom. Its use of "dense jargon" and "stilted metaphor" is actually surprisingly consistent - it's speaking its own dialect, and you get used to it. After a while it gets much easier to read and even becomes somewhat efficient,…
It's almost like learning sdk every time new model is released.
It's ironic how initially it was sold as "coding in plain English", and now we are back to sdk ))