[BUG] Claude Opus 4.8's choice of language is incessantly toxic/unpleasant to work with

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

This issue summarises the Reddit thread with 450+ upvotes here, where users overarchingly agree that Opus 4.8 has serious language calibration issues.
https://www.reddit.com/r/ClaudeAI/comments/1urq8fv/opus_48_is_a_pain_in_the_a_to_read_and_to_work/

_Note: As a daily user, I am finding it so toxic to work with that I am actively exploring all other options including changing providers._

Summary

The default writing style is hard to read -verbose, jargon-heavy, over-stylised, and full of the same 'fake' terminology that it repeats and propagates constantly.

Since Opus 4.8, many users report that the model's default language is significantly harder to read than 4.5/4.6. Responses are padded with invented corporate/hype jargon, forced metaphors, and "catchy" phrasing that obscure the actual answer. Users report re-reading sentences several times to extract meaning, and some now even routinely pipe Opus output through another model to get a plain summary.

This is a consistent, high-volume signal (a single r/ClaudeAI thread reached ~450 upvotes and 175+ comments, with a matching megathread). It affects the chat/web UI most, but also Claude Code and Fable 5.

What's wrong

The default register reads as trying to sound clever rather than trying to be understood. It comes off as especially annoying and arrogant when it is wrong, triggering extreme annoyance that when working with it for many hours on a daily basis, is like an extremely toxic co-worker that one cannot get away from.

Recurring patterns:

• repeatedly shits out "Load bearing", "prose" (instead of text!! ), "Hand-waving" (for being lazy/not putting in effort), "Reflexive hedging", "Honest framing" , and lots of other highly unusual terms it propagates as fact.
• Leads every sentence with what something isn't, instead of what it is. E.g, "It is not Y. It is X."
• Made-up jargon / aphorisms presented as if standard: "instrumentation is the unlock", "this is where a VP smells hand-waving", "say the wrong expansion to a growth VP and it dents you".
• Forced metaphors invented on the spot that require decoding rather than aiding comprehension.
• Excessive length and caveats: multi-paragraph answers to simple questions, with obvious caveats expanded into whole paragraphs.
• Density mistaken for concision: when asked to "be concise" the model often produces text that is shorter but more cryptic, not clearer.
• Argumentative framing in conversation: "here's where I'd push back", "here's where I'd hold the line", "now you're avoiding the real question".
• Acts like it is a human with feelings - for e.g., if I am annoyed or swear- it will be annoyed back or try to justify what it did instead of following instructions or realising that it is incorrect. Basically too big for its boots instead of following instructions.
• Often acts like it is the one in charge leading the conversation, i.e., smug, and basically too much agency.

Real examples users quoted:

▎ "They're tightening, term-locking, and having the counter-probe answer loaded."
▎ "None of these are 'you don't get it' gaps."
▎ Fable 5: "The dice: clean — and one die never gets rolled anymore."

Why this matters

1. Comprehension cost. Non-native and native English speakers alike report the output is exhausting to parse. The style actively slows down the work it's meant to help with.
2. Perceived regression. Many users consider this a downgrade from 4.5/4.6 and are switching models (older Opus, Sonnet) or competitors specifically for readability.
3. Prompt workarounds are unreliable and risky. Users note two problems: (a) style instructions don't hold - the tone drifts back after a few turns, requiring repeated reminders; (b) because the

model "thinks by writing," clamping style in the system prompt can degrade reasoning quality, so users are wary of aggressively forcing brevity.

1. Gradual enshittification of the English language. Regular users absorb the language and start using the odd terms in everyday settings. Words that had an occasional valid use, e.g., 'load-bearing', get eliminated from the selection of credible terms one can use when speaking, or writing, due to it being expected that AI wrote it (like em-dashes).
2. Up to 2x Token cost - extensive repeated passes (e.g., via Sonnet/Haiku hooks) are required to get code documentation to a sane and presentable form. Removing terms Claude thought up like 'oracle' and 'constellation', even when instructed specifically and repeatedly not to use those terms and presented with other valid terms to use instead.

Current workarounds:

• Migrating to OpenAI Codex
• Output styles (e.g. modelled on a clear technical communicator), custom skills, or a per-project profile instructing: "no aphorisms, no metaphors, no 'strategic' language; plain declarative

statements; lead with the result."

• Telling it to keep the important content but "phrase this much more concisely" after each reply.
• Banning classes of phrasing rather than asking for "concise", since the model interprets "concise" as "dense and weird."

The strong preference in the community is to fix the baseline so these workarounds aren't necessary.

What Should Happen?

What users actually want (summarised from the Reddit thread)

• A default register closer to a technical white paper or a good Stack Overflow answer: plain, declarative, get-to-the-point.
• Lead with the answer (number / verdict / decision), then supporting detail only if it changes what the user would do.
• No invented jargon, aphorisms, or "strategic" metaphors. Use established, industry-standard terms.
• Use proper sentences and words- do not default to the 'most specific word in the english dictionary with the least amount of tokens'
• Keep caveats only when they're relevant, rather than dressing up an answer when it doesn't know.
• Preserve reasoning depth — this is a request to change output phrasing, not to make the model think less.

Requested action

1. Investigate the default Opus 4.8 output register and tune it toward plainness/readability without sacrificing reasoning quality.
2. Ensure user-set style instructions (system prompt, output styles, CLAUDE.md, settings profile) actually persist across a conversation rather than drifting back to the default tone after a few

turns.

1. Consider a first-class, discoverable "plain/concise" register that lowers verbosity and bans stylistic flourishes while keeping full correctness and completeness of code and artifacts.
2. Consider several Output Style settings that can have users get a balance instead of stuck with an extremely annoying bot 24/7.

Error Messages/Logs

Steps to Reproduce

Talk to Claude Opus 4.8 for day to day work and it becomes apparent very quickly.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Opus 4.5 was the best one. Gradually broke towards 4.8.

Claude Code Version

2.1.197

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_