Three builders ship "de-slop Claude" tools in the same week

Three separate teams have built tools to solve the same annoyance with Claude Code and Claude 5: the output can sound overly polished, padded out, and strangely self-congratulatory.

Nobuzz, Vomit, and Caveman all take a similar approach. They pass an AI response through a second model or editing layer that strips back the tone and makes it shorter, plainer, and more direct. Vomit reached Hacker News’ front page, drawing 293 points and 285 comments. Caveman is reportedly gaining 718 GitHub stars a day and claims its terser style can cut token use by 65%. Nobuzz reached 89 points by routing responses through Gemini CLI to flatten the tone. You can see the discussion around Vomit in the Hacker News thread.

The interesting part is not which tool wins. It’s that three unconnected builders landed on the same answer in the same week: one AI increasingly needs another AI to edit it before a person sees the result.

For a business owner, this is a useful reminder. AI output is rarely ready to send just because it is technically correct. If your team uses AI for customer emails, proposals, reports, code documentation, or internal updates, tone and brevity need a quality check. A second-pass editor can reduce review time, avoid generic corporate language, and lower usage costs when it produces fewer tokens. This is the kind of thing we build into an AI command centre, where AI outputs can be checked against the style and standards your business actually wants.