I'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…
> especially as the session drags on. This is because these harnesses are missing a very important feature. Anything like this needs to be included with every turn, otherwise the LLM quickly drifts. I first noticed it when I wrote a harness for D&D (because it's so damn noticeable there), but now I include this for any harness I write.
Vomit: Clean up Claude 5's token output with a separate LLM
61–70 of 315 posts
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#62Ahh! Author here. Thanks for posting! In case anyone wants to share in my frustration, I also wrote a blog post about this.
Blog post: https://zachahn.com/posts/1787191554
The prompt I use to tell the LLM what to fix: https://github.com/zachahn/vomit/blob/main/internal/config/s...
Wasn't received too well on Lobsters haha, wrote a small extra blurb about it there: https://lobste.rs/s/juekuk/how_fix_claude_5_s_token_vomit
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#63Re: Vomit: Clean up Claude 5's token output with a separate LLM
#64Just set the following incantation: You must use ASD-STE100 Simplified Technical English (STE) when it doesn't detract from meaning.
I'll give that a try. Hopefully it reduces the text vomit Claude tends to do. Right now all I have is > - Give terse and concise answers unless the user asks you to elaborate. Big walls of text are not usefull when trying to communicate.
Don't bother, no incantation can fix it.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#65I have very little in my agents.md file wrt style, except for:
> Caveats belong inline, no "one thing to note" or "it's worth mentioning" footer. If it is worth raising or calling out, do so where it is most relevant and not as a foot note.
Opus 5 has a god awful habit of always doing a Columbo on every single response, and it is such a jarring read that it amps my cognitive burden having to back-read everything.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#66Just set the following incantation: You must use ASD-STE100 Simplified Technical English (STE) when it doesn't detract from meaning.
I actually changed the output style for Claude Code to use ASD-STE100 and it still doesn't help that much. It still comes up with a lot of stupid words like this gem "Standing where it stood"
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#67With a whole separate LLM? FWIW you can also consider using something deterministic like vale.sh [1] , it's pretty easy to write prose violation plugins [2]
[1] https://vale.sh/
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#68I'm surprised by this reaction to Claude's verbiage recently. I don't have any issue immediately understanding what it's saying, but then again I read regularly and a lot of the people I know complaining think it's an accomplishment in literacy to get through Dungeon Crawler Carl.
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#69Earlier quoted context omitted.
> especially as the session drags on. This is because these harnesses are missing a very important feature. Anything like this needs to be included with every turn, otherwise the LLM quickly drifts. I first noticed it when I wrote a harness for D&D (because it's so damn noticeable there), but now I include this for any harness I write.
https://code.claude.com/docs/en/hooks https://learn.chatgpt.com/docs/hooks
[deleted]
Re: Vomit: Clean up Claude 5's token output with a separate LLM
#70I like the "Claudish to English" name better. https://github.com/gvzdv/claudish-to-english
The Claudish example seems to have more information.
Are people really having trouble parsing this??