Analysis of Opus 5's 'Contrition'
slowmovintarget
17 points
3 comments
July 28, 2026
Related Discussions
Found 5 related stories in 329.9ms across 15,236 title embeddings via pgvector HNSW
- Elevated Errors for Opus 5 TimCTRL · 93 pts · July 26, 2026 · 55% similar
- Benchmarking Opus 5 on SlopCodeBench dhorthy · 216 pts · July 27, 2026 · 54% similar
- Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6 forks · 32 pts · June 22, 2026 · 51% similar
- Claude Opus 4.7 meetpateltech · 1621 pts · April 16, 2026 · 51% similar
- Claude Opus 4.8 craigmart · 1365 pts · May 28, 2026 · 50% similar
Discussion Highlights (3 comments)
urbandw311er
Does this work? Appreciate honest testimonials from anybody unrelated to the OP or author.
nightshift1
Interesting. I will try some of of those instructions but I don't mind much about the tics. My actual complaint: end-of-turn summaries that are undecipherable unless you watched the session closely. Both Opus and Fable regularly ends hours of work with status updates phrased in crystal clear terms like: "**V2** debug-helper gate (R4d) | Medium-risk | Gate on `?debug=1` URL param at 3 fixture sites — **not** a localStorage flag (`browser_page` clears it every test). 284 debug-API calls ride the fixture, so R4d goes last+alone"
bomewish
Bit frustrating. any kind of benchmark or even a few examples showing that this produces better outputs would have been nice.