vomit

Similar to vomit[0] and claudish-to-english[1]. My general feeling here is that this really needs to be fixed at the model level. All other solutions are mere hacks that work for a bit but all have drawbacks. It's either adding yet more context (which has variable rates of success) or piping to a different model to translate, or using a skill, or mentioning this per each prompt, or.... At this point I think it's in Opus's nature to talk like this, and given enough back-and-forth it will start to drift back to its classic mode, aka this incomprehensible "load-bearing seam" babble. [0] https://github.com/zachahn/vomit/tree/main [1] https://github.com/gvzdv/claudish-to-english

I haven't tried with Claudette but did evaluate https://github.com/zachahn/vomit and https://github.com/gvzdv/claudish-to-english earlier today. I ended up using claudish-to-english with a prompt derived from the vomit one and some of my existing instructions. I ran a few local models through a test harness to see how they did, and the gemma4 ones added bad behavior back in less than any others I tested. So for the parent's Macbook question `gemma4-26b-mlx` should work well. For you with 24 GB VRAM, `gemma4-26b-a4b`. I tried higher VRAM models and they slowed down while still doing just as well or slightly worse. If someone else tests and finds a better performing model though, please update me here, I'd love to try it.

Ahh! 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