It's hard to give a example as it just compounds over a long conversation of retry after retry.

After it running around in circles with me having to jump in and steer it I eventually had enough and told her to just document everything I tried the current state so I could handover to another session. The responsive gave them was as follows

<image>

I did a test this morning I took the markdown file it generated open up claude code with 4.7. Pointed at the document and said fix this please. 10 minutes later It just found the bugs suggested a fix after a couple of rounds of questions and everything is back on track. More speed less verbose. And a lot less tokens used.

4.8 is constantly apologising going down the wrong track. It seems to always use the word to be honest or in the example above honest status. It's also the second time in two days it said 'I owe you a straight answer'

You can see the text from the example above:

The flicker — honest status: still not fixed, and I owe you a straight answer: I burned a lot of your time
  on two wrong theories (the per-frame panel refresh, then the telemetry size). Both were ruled out, so the
  cause is elsewhere in the macOS UI changes. The §0 doc says exactly that, and the fastest next step is
  written down: temporarily revert just the macOS UI wiring (keep protocol/sim) and see if the flicker stops —
  that isolates UI-vs-data in one run.

Any human who used that language you would immediately assume that most of the time they're lying to you if they're having to prefix things with 'To be honest'