Claude Code Degraded Before Opus 4.8 Release
Claude Code experienced a significant drop in its pass rate prior to the release of Opus 4.8. This decline lasted for five consecutive days before recovering immediately after the new version was launched. The performance tracking highlighted the importance of monitoring day-to-day changes in model performance.
- ▪Claude Code's pass rate dropped below its established baseline before the Opus 4.8 release.
- ▪The degradation lasted for five days and was statistically significant.
- ▪The pass rate rebounded sharply once Opus 4.8 was released on May 28.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Marginlab |
| Canonical URL | https://marginlab.ai/blog/claude-code-degraded-before-opus-4-8/ |
| Publication time | Fri, 29 May 2026 12:43:59 +0000 |
| Retrieval time | 2026-05-29T12:50:00.410Z |
| Last seen | 2026-05-29T12:50:00.410Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | XEdqn5QcXejF |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Back to blog claude-code degradation swe-bench-pro Claude Code degraded for the week before Opus 4.8's release Our SWE-Bench-Pro tracker caught a statistically significant, weeklong drop in Claude Code's pass rate just before Opus 4.8 shipped, and the recovery that followed. JB · May 28, 2026 We run Claude Code against a curated subset of SWE-Bench-Pro every day, in the plain CLI with the current SOTA model and no custom harness. The point is to catch the thing that benchmarks published at launch can’t: silent, day-to-day changes in how a model actually performs in production. In the week leading up to the Opus 4.8 release, the tracker caught exactly that.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Marginlab.
Discussion
0 commentsMore from Marginlab
