On April 16, 2026, Anthropic officially released Claude Opus 4.7, a major model upgrade following Opus 4.6. The model was rolled out on the Claude web interface, app and API, and made available to enterprise customers through cloud platforms including Amazon Bedrock, Google Vertex AI and Microsoft Foundry. Anthropic positioned it as "the most powerful generally available model to date", focusing on improvements in complex programming, long‑range reasoning, vision tasks and knowledge work capabilities.
However, within 24 hours of the release Opus 4.7 ran into a "backfire" controversy. Numerous users on Reddit, X and GitHub reported that in practical use the model exhibited increased hallucination rates, regression in instruction‑following and reduced stability on complex engineering tasks, with some calling it a "serious regression." This sharply contrasted with Anthropic's publicity and quickly sparked industry debate.
Official claims vs. user tests: polarized performance
In its announcement Anthropic emphasized significant progress in agentic coding and long‑horizon reasoning:
- Support for a 1M‑context window (available to some users via specific commands);
- Optimization of the tokenizer to improve long‑context handling efficiency;
- Improved understanding of high‑resolution images and code screenshots in vision tasks, and the ability to generate reliable repair suggestions.
However, user feedback was sharply divided. In communities such as Reddit r/ClaudeAI, multiple developers reported:
- Higher hallucination rates: On tasks requiring strict factual accuracy, 4.7 is more prone than 4.6 to fabricate details or omit key information. Some users said, "the hallucinations are far worse than 4.6."
- Performance regression: In complex multi‑file projects, instruction‑following and execution stability declined, with frequent "lazy" behavior (refusing to engage deeply or skipping steps).
- New tokenizer impact: Opus 4.7 introduced a new tokenizer that increased token consumption for the same input by 0% to 35% (depending on text type and language). Although Anthropic claimed this improved model understanding, many users reported substantially higher token usage without corresponding performance gains, increasing usage costs.
Anthropic's migration guide noted token changes from the new tokenizer but did not anticipate such strong negative reactions to overall performance. Some analysts speculate Anthropic may have "nerfed" the model in late 4.6 to control compute costs, and that 4.7 was intended to address that, but the optimization direction diverged from user expectations.
Root of the controversy: the safety‑vs.‑cost trade‑off
This controversy is not isolated. A prior Claude Code source leak exposed security concerns, and the Opus 4.7 release has renewed doubts about Anthropic's model iteration strategy. Users generally believe:
- There was noticeable "degradation" (regression) in later stages of 4.6, suspected to be intentional adjustments to reduce compute costs;
- Although 4.7 shows improvements on official benchmarks, it fails to fully address 4.6's shortcomings on real‑world complex tasks and raises adoption barriers due to the new tokenizer.
Anthropic has not issued a formal response to the broad user feedback, stating only in technical documentation that Opus 4.7 continues the "Constitutional AI" principles and embeds stricter refusal boundaries. Community signals show some users beginning to migrate to OpenAI GPT‑5.4, Google Gemini or open‑source alternatives (such as GLM‑5.1).
Industry impact: a trust crisis in model iteration
The Opus 4.7 controversy highlights a core dilemma in AI model iteration: a gap between promoted performance and real user experience. As AI capabilities advance rapidly, balancing compute costs, safety constraints and user perception is a common challenge for all vendors. Anthropic already faced a trust deficit after the Claude Code leak, and the 4.7 "backfire" has amplified the issue.
For developers, this is a reminder to thoroughly test closed‑source models rather than rely solely on vendor benchmarks. Open‑source models (such as GLM‑5.1 and the Llama family) gained attention during this controversy for their transparency and controllability.
For the industry, the Opus 4.7 incident underlines the importance of AI safety and reliability. Future model iterations must prioritize real‑world usability and user trust alongside parameter counts and benchmark scores. Whether Anthropic can recover reputation through rapid fixes and transparent communication will directly affect its competitiveness in the enterprise AI market.
Conclusion: the cost of AI progress
The release of Claude Opus 4.7, intended as a technical victory for Anthropic, has been overshadowed by divergent user experiences. Increased token consumption from the new tokenizer and regressions in certain tasks have disappointed many loyal users. The episode reminds the AI industry that user experience must remain central amid the race for frontier capabilities.
From the Claude Code leak to the Opus 4.7 controversy, Anthropic is undergoing a trial in trust rebuilding. As more model iterations and community feedback accumulate, whether AI can become a reliable productivity partner will take time to prove. One clear takeaway is that user demands for model stability and transparency are becoming a driving force in AI development.
▶️ Enjoyed this article? Creating content is hard work!
Follow our YouTube channel:
AI Rosetta
Your likes, subscriptions and shares are our greatest support! 🙏
More AI news at: https://www.airosetta.com