Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Opus 4.7 Sucks. Stop changing the models or I'm leaving.

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Opus 4.6 of one month ago was MUCH better than 4.6 of a week ago, and MUCH better than Opus 4.7. The quality has SIGNIFICANTLY regressed. You cannot keep doing this to your customers. I'm so close to going to codex.

What Should Happen?

STOP CHANGING YOUR MODELS - and especially, stop dishonestly calling them the same when you are changing their behavior. Where did your ethics go?

Error Messages/Logs

Steps to Reproduce

  1. Try opus 4.6 from a month ago
  2. Try opus 4.7
  3. Notice how opus 4.7 sucks.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.116

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by using an older version of Opus, specifically Opus 4.6 from a month ago, which is reported to have better quality.

Guidance

  • Try to obtain or revert to the previous version of Opus 4.6 that worked as expected to confirm if the issue is indeed a regression.
  • Compare the performance and behavior of Opus 4.6 from a month ago with the current versions (4.6 from a week ago and 4.7) to identify specific differences.
  • If possible, provide more details about what "MUCH better" means in terms of quality, such as specific metrics or use cases that have regressed.
  • Consider reaching out to the developers or support team to report the regression and request guidance on how to proceed, as the issue seems to be related to changes in the model's behavior.

Notes

The exact cause of the regression is unclear without more information about the changes made to Opus 4.6 and 4.7, but using an older version may provide a temporary workaround.

Recommendation

Apply workaround: Use an older version of Opus (4.6 from a month ago) until the issue is addressed by the developers, as it is reported to have better quality and is a known working version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Opus 4.7 Sucks. Stop changing the models or I'm leaving.