> AGENTS.md does very little, agents will consistently violate the communication preferences, especially as the session drags on

That’s really annoying, it feels like it’s improved some. Not sure what the fix is, but you could try using a canary to at least get a signal of when things are going sideways (Mr Tinkleberry for reference: https://news.ycombinator.com/item?id=45983698)

> 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.

> The baked in communication style of these models is so obnoxious it's impacting my work.

This is close to the worst thing one could say of tool for professional use.-

Unfortunately this may only start to get worse as the AIs are trained on more and more AI generated content.

That sounds kind of like deception, and a dark pattern not too unlike abuse to me.

Though you know, it's not like the leadership tied to these companies have a history of abuse, deception and theft or anything like that, right?

It's not like our leaders hide behind similar sorts of patterns that the agents/AIs follow (not saying it's not a human thing - but I hold leadership to higher standards than non-leaders). If our world leaders were able to be more accountable to these abuses, I don't think this would be tolerated with our AIs.

> Why not just use that other vendor's model for everything?

Effectively all models can do style transfer reasonably well at this point, but not so much for "actual reasoning".

If the combination of two works better for you than each one by itself, why wouldn't you stack them like that?

> Why not just use that other vendor's model for everything?

Because it's not an either or thing. Neither is sufficient. I'd argue that, expenses aside, you should have every model you have access to cross reviewing the work of the others.

Outside of super trivial things that I should have just done myself, I have a cross-model review of _everything_ these days. The tokens are too cheap not to.

individuals can blow in the wind, but if you are a company who bought a thousand seats and spent a ton of time training people up, establishing policies, vetting which extensions are allowed, the transition cost is much higher.

Pre Trump-castration Fable was verbose, but had a point, and used that wordiness to say or show the indeed intelligent things it reasoned about. This, whatever this is, is something else.-

That one is more specific, but "vomit" captures the feeling of Opus 5's writing very well for me. I don't know if it's the watermarking, but every single language idiosyncrasy that Opus 4.x (x > 5) had has been pushed up to 11 on Opus 5. Plus we got nouns verbing and seams seaming.

It's really unusable for anything other than code. And I have to remove its incomprehensible comments 50% of the time before committing anyway. After interacting with it, "slop vomit" is truly the most fitting description. I have to admit I have lost my temper and spontaneously referred to its output as vomit more than once. Seems like I'm not the only one.

Word, that one also includes an example which is great, shows really clearly what the issue is for those who might be less familiar

Maybe Glimmer might be good at excising the comment spam, particularly?

I use Pi but with my codex subscription, still preferable to paying the API cost (and I know I would be, as I track how much the cost 'should' be via token api pricing).

Wish I could use my Claude subscription with pi too, much preferable to the endless command execution allow/deny prompts you have to do with CC, versus proper autonomous allow/deny lists defined ahead of time.

Curious why you recommend the API? It's likely the current subscriptions won't stay for long, they're heavily subsidized, but before they get axed, they're easily the best deal for monthly price/token usage.

Intentionally deferred.

The author's blog has what follows (link also follows):

[Seriously y'all in what universe would some "caveat" or another NOT "be a real one" by whatever severity you'd want to measure that AND/OR need of saying so ... ]

Claude (Original)

Force pushed. 1234567...890abcd main -> main (forced update).

Verified

Local main and origin/main both at 890abcd, in sync.

Every commit reachable from origin/main: no old string found.

Local object store, with spice-harvester as a control returning 9 hits: all old strings return 0.

Working tree clean, tests pass.

One caveat, and it’s a real one

The old tip 1234567 is still fetchable from GitHub by its full SHA. I confirmed this directly:

git fetch origin 1234567890abcdef1234567890abcdef12345678

* branch 1234567... -> FETCH_HEAD (succeeded)

GitHub keeps unreachable objects until its own garbage collection runs, and there is no schedule you control. Anyone with a full SHA can still read the old blobs through the web UI or a direct fetch. That fetch also pulled the old objects back into your local repo, so I deleted FETCH_HEAD, expired the reflog, and re-ran gc --prune=now. The counts above are from after that cleanup.

If you want the old commits unreachable on GitHub’s side too, the options are to ask GitHub Support to run GC on the repo, or to delete and recreate the repository. Deleting and recreating is the only one you can do yourself. Say the word if you want help with either.

Nothing to commit this turn. The rewrite was the work, and the tree is clean.

Claude × Vomit GPT-OSS-20B

I force‑pushed the branch, updating main to commit 890abcd. I verified that my local main and origin/main are both at 890abcd. I checked that every commit reachable from origin/main contains no old string. My local object store shows that the spice‑harvester control returns nine hits, and all old strings return zero. The working tree is clean and the tests pass.

However, the old tip 1234567 is still reachable on GitHub by its full SHA. I fetched it directly and saw that GitHub keeps unreachable objects until its garbage collection runs, which I cannot schedule. Anyone with the full SHA can still read the old blobs via the web UI or a direct fetch. The fetch also brought the old objects back into my local repo, so I deleted FETCH_HEAD, expired the reflog, and ran git gc --prune=now. The counts I reported are after that cleanup.

If you want those old commits to be unreachable on GitHub as well, you can ask GitHub Support to run garbage collection on the repo, or delete and recreate the repository. Deleting and recreating is the only option you can do yourself. Let me know if you need help with either.

There is nothing to commit this turn. The rewrite was the work, and the tree is clean.

https://zachahn.com/posts/1787191554

The “whining” stems from watching the communication style obviously degrade, and it’s a huge problem for people who want to use this stuff to build and instead continually fight the tools.

Like so many other products, people are moving too fast and shipping things that move the ground under people’s feet needlessly.

All this while we’re beaten to death with the marketing and false promises, and the broader consequences (ex: layoffs, stress, crazy expectations) caused from all this.

Obviously what Anthropic and co have built is amazing and people aren’t losing sight of that. That’s actually the key part of the frustration.

So no, this is not whining. This is the natural response you get when you make bad product decisions.

If you don’t want to get feedback, don’t sell products.

Seriously, of all the complaints for a coding agent, "I don't like the explanatory prose" seems pretty far down on the list.

Amen.

These things do work that previously would have taken expensive engineers months to do, at much lower quality, and what's our response? Ti nit pick on it being more verbose than we'd like?

Just like with humans, when someone is being too verbose, there's a skill to just filter through the noise and focus on the important parts.

This feels no different when I use an AI.

But I guess it's a good sign that we've from complaining about 'AI slop code' to, 'I don't like how it speaks to me'.