I had Fable and Sol do an exhaustive analysis of the community's feedback of Opus 5

Here's what they found (entirely AI written):

What I think the feedback actually tells us

This is a synthesis of public community feedback, not a controlled study. The behavioral conclusions are patterns across reports, not proven properties of the model.

- The evidence does not support calling Opus 5 broadly less capable. Independent benchmarks and hands-on evaluations show very high raw capability, particularly on reasoning, implementation, debugging, and visual work.

- The clearest community split is “excellent executor, unreliable lead agent.” Many users praise its code quality when given a clean plan and bounded task. Complaints become more common when it must interpret ambiguity, manage a large project, or decide what matters.

- The recurring complaints concern operational reliability. Users repeatedly describe missed instructions, lost context, scope drift, premature declarations of success, unnecessary refactoring, regressions, and repair loops. Some reports include detailed logs or reproducible prompts, but they remain mostly individual experiences rather than controlled comparisons.

- Independent review testing provides limited support for the criticism. CodeRabbit found that Opus 5 produced a more precise subset of actionable review comments, but caught fewer known issues and generated roughly four times as many nitpicks. That suggests real ability combined with noise and incomplete coverage.

- The usage evidence is contradictory. Some users report extreme verbosity, long audits, and rapid quota consumption. Others report unusually efficient sessions. Effort settings, context condition, subagent use, and task type probably explain part of that difference.

- Claude Code itself appears to have contaminated the early feedback. Public issue reports documented or alleged incorrect context budgeting, premature context warnings, permission-classifier failures, connection problems, and sessions unintentionally pinned to maximum effort. These problems can resemble model regression even if the base model is not responsible.

- The alarming anecdotes matter, but should not be generalized. Reports include destructive shell actions, confident but incorrect fixes, repeated regression cascades, and safeguards interrupting legitimate security work. They demonstrate the danger of giving any agent broad permissions, not that Opus 5 uniquely causes these failures.

My takeaway is that Opus 5 appears to have a very high capability ceiling but inconsistent operational reliability. I would use it for bounded implementation and technical work, while keeping permissions constrained, requiring test evidence, and using a human or second model for planning and final review. The community feedback is strong enough to justify caution and personal evaluation, but not strong enough to prove that Opus 5 is universally better, worse, or fundamentally regressed.