Comment by mcintyre1994
8 hours ago
> Communication. Opus 5.5 communicates more naturally than prior models. Early testers found its writing clearer and easier to follow, which addresses some of the common feedback we heard about Opus 5. It puts the most important information up front, and its style makes it a better work partner over long sessions. As one early tester put it, “it writes the way I do.” In our own use, this has made Opus 5.5’s work easier to follow and check—which is a safety benefit as well as a practical one.
I think this is what I'm most interested in. I mostly moved to Astra because I just can't work all day with the Claude Opus 5/Fable writing style. I don't think Astra is a better model, but it's the first OpenAI one that seemed good enough to me. Definitely keen to try Opus 5.5 and see if this claim is real.
I'm surprised that you're getting so many replies saying it's the same. So far in my usage today Opus 5.5 does seem like a noticeably better writer. Opus 5 frequently made me want to strangle it while 5.5 has been producing a lot less incomprehensible gobbledygook.
So far it seems the same. I used Opus 5.5 for an hour this evening and it was just as painfully verbose as Opus 5. It also used the term "load bearing" 4 separate times.
Due to this release note, I used it once to rewrite a doc, and was disappointed.
As someone who uses both, Astra was 100% the better model. I have yet to give 5.5 a spin so maybe that’ll be the new top contender.
I prefer Astra for creative uses, Fable seems better for hardcore coding.
Whoa, I'm exactly the opposite.
2 replies →
Yes this is a big part of what has turned me off Opus 5 completely. The other (more dangerous) one is how often it gets assumptions wrong. These both (along with Astra) caused me to split my time 50/50 now between the two models.
Not a day goes by when I push back on something, to which Opus 5 very unambiguously say "You were right, I was wrong" - this never happened so often with past models, nor with Fable.
We'll have to see how much Opus's ability to communicate has improved. It's already giving me better summaries of where we are in the conversation.
I did the same switch (that reason along with the newer models seeming more "lazy" and needing constant prodding to finish long-horizon tasks) but my issue with ChatGPT/Codex now is that it too roundabout and doesn't get to the point. I tried adding instructions and using the personalization settings to make it more efficient but haven't seen much change. Claude seemed to follow settings more closely. Has anyone had any success to make ChatGPT more succinct?
after a few hours use, my impression is that Opus 5.5 writes like gemini. drastic improvement over all opus 5.1's claudeisms.
and i think i was generally more tolerant of 5.1's writing style than most people.
The writing style is insufferable but it’s not just that. https://opusfived.dev/
I've been using Opus 5 since it was released and don't understand all the hate it gets. It very well could be something in my own local memories or Claude.MD files that prevents it, but I certainly have never experienced something like that site portrays.
That’s funny but I don’t really recognise that issue. I’m very confident that Opus 5 would correctly change the colour of just one button.
You are right and make an important insight. While well meaning and amusing, it did not reflect the entire spectrum of outcomes that could arise from the worktree.
Navigating the landscape of agentic levers certainly requires a more detailed approach than this and you were certainly correct to push back.
1 reply →
Nice, captured the flavour of 5's writing exactly.
Oh god yes.
Fable 5.1 is a lot better than Fable 5 btw (edit: in terms of writing style). Not sure about opus 5.5 yet since I’ve only got one session in so far.
Much better than Opus 5. prompt:
> hi, can you explain how the scheduler works. keep it brief, but include important correctness details
some excerpts:
>Flow: 1. Data arrives. The appender calls prepare/commit around the krolik write. The prepare step leaves a phantom row, so a write that is still in flight is tracked. The commit publishes STREAM_INPUT. 2. Poll. It first reclaims expired leases. Then it sweeps sdirty (a candidate index) in a rotating order, oldest since first, which prevents starvation. It re-derives the exact period and rewind for each candidate from snode_out/snode_in, then claims it: writes the sassign lease plus a per-edge sassign_edge snapshot. 3. Complete. Each edge's watermark is set to the snapshot taken at dispatch. Anything published after that gen stays dirty automatically. A failed or partial job writes nothing, so its dirt persists.
> - Folds are monotone single statements. gen only goes up, extents only grow, processed periods only union, rw_start only moves earlier. So replays, out-of-order writes, and concurrent writes can at worst hold a watermark back. The worst outcome is a spurious rerun, never lost work. There's no read-modify-write and no truncation of the dirty period, so a write that lands during a job can't be swallowed.
> - Rewrites are declared by the publisher, never inferred from overlap. An unflagged write that overlaps already-processed data means "unchanged", which makes retries and redelivered tasks free. Each publisher has its own reason for being sound (see the table in scheduler/CLAUDE.md). A new publisher needs a row in that table.
> - NULL means dirty, and DELETE is the fence. Every node and edge has a row from the moment it's created. A lost parent or a settings-only edit can't be derived, so both go through one forced-rerun path: capture_rewinds reads the processed span before the DELETE, and apply_rewinds publishes it as a rewrite on a config root.
All the non-standard programming jargon is stuff from the repo. I can actually read it and understand what it's talking about. I used Fable to handle Opus 5 as I just couldn't stand it. With this I'll probably go back to Opus.
That's the standard annoying pattern though: "Rewrites are declared by the publisher, never inferred from overlap." and "NULL means dirty, and DELETE is the fence." - still the same LLMisms. I didn't expect them to disappear, but it's not a radical improvement either.
This one is pretty terrible (right after “The worst outcome is a spurious rerun, never lost work.”). We’ve got lands, several "no X", hyphenation, strange noun/verb sentence order and an unnecessary analogy word (swallowed).
> There's no read-modify-write and no truncation of the dirty period, so a write that lands during a job can't be swallowed.
1 reply →
Oof thanks for sharing, that seems just as bad if not even worse than Opus 5 to me. Just about every sentence is painful. Particular standouts that a human would never write:
> Rewrites are declared by the publisher, never inferred from overlap
> NULL means dirty, and DELETE is the fence
Hah! You independently picked exactly the same sentences I flagged (I know you posted this 11min before me but the comment only appeared after I had submitted mine).
So still effectively nonsense.
> Rewrites are declared by the publisher, never inferred from overlap.
This style of writing is idiotic because it conveys no additional information. It's no different from stating
> Rewrites are declared by the publisher, never when moons collide.
The two sentences are actually logically identical. No idea why these models keep writing like this.
> Folds are monotone single statements. gen only goes up, extents only grow, processed periods only union, rw_start only moves earlier.
This is even more ridiculous.
Yes, it's unbearable. Hopefully they've actuallu lly fixed it.
Please update with your feedback
I haven't heard it say "load-bearing" yet (I've used it for 30 minutes now), so that's a start.
That's a sharp observation and you're hitting on something most people never even realize.
That's a sharp catch, and I think it exposes a real bug.
Worth flagging!
Opus 5 has made me question my sanity on a daily basis, especially as all my coworkers started lobbing Opus 5 slop grenades everywhere. It had the worst and most infuriating writing style I've ever seen.
I hope Opus 5.5 is better, if for no other reason than all the Claude slop I have to read will be at least more tolerable.
One funny side effect of all of this: realizing that coworkers that use AI for almost all the text they generate at work have their writing style change every time a new model ships.
I really wonder how it converged on its style. It's pretty unique and terrible. It's not like it's just mimicking something or it was purposefully design to be that way. I mean the reason may be diffuse and uninteresting... just the result of a lot of factors and lack of control over the writing style probably.
But oddly enough its still great at coding. Just like a lot of people it either interfaces well with people or machines but not both.
I assume it’s largely a side effect from the final RL in post training?
That’s the step that causes the most significant gains in agentic performance.
But the RL doesn’t care about anything except maximizing the score, so if you only score based on coding benchmarks, anything can happen to the writing style (as long as it doesn’t hurt the coding performance).
That’s why it often gets worse on models that simply had more RL post training from the same base.
2 replies →
It truly was bizarre. I've used every major model since 2022, and not a single one had a writing style as bad as Opus 5
1 reply →
Here's the part that nobody is talking about: corporate always had their jargons and unique writing style – LLMs have just created their own :)
Astra is better here, but the one I'm the most impressed with is Gemini. It's always been good, but 3.6 Flash is even better. It writes in a pleasant, human style. Not perfect, but it has a good balance between technical accuracy and readability that is better than what I've seen from any other mainstream model.
Yes, it made me want to vomit. If the new Fable only changed the writing style to just sound like a human, same performance for everything else, I'd be pretty happy.
Opus is only usable if you have a post-turn formatter that strips all comments from the generated source. I'm not even kidding it's that bad.
It's not X, it's Y, not A, not B, not C, and he haven't even woken up yet! Here's the catch, the detail is in the devils and the twist is that it's designed!
You're right to call this out, and what's more, it's not even solving the original problem. I overlooked this in pursuit of the load-bearing seams and finding the wedge needed to uptick engagement.
Here's the X that Ys the Z:
> especially as all my coworkers started lobbing Opus 5 slop grenades everywhere
People that produce slop have to be fired asap, they're just human relays anyway.