是我感觉错了,还是 Claude Opus 最近变差了?
4 分•作者: de6u99er•26 天前
自从最近的更新以来,我感觉 Claude Opus 在处理复杂任务时变得越来越笨拙。
以前在一个提示中就能顺利完成的事情,现在却完全失败。在编码工作流程中,它总是忽略强制性的 CLAUDE.md 项目规则,对不相关的文件进行未经请求的修改,并破坏可用的代码。它会基于过时的评论开始争论,在代码更改时未能更新文档,并且在不先实际验证代码库的情况下,基于盲目猜测进行编辑。
我甚至发现自己过去总是用 Opus 来完成的任务,现在却不得不使用 Fable 来获得像样的结果。
感觉 Anthropic 是在将他们的技术问题转嫁给付费用户。要么是他们使用了严格的安全过滤器,在不告知我们的情况下悄悄回退到更便宜的模型,要么是在高负载下为了省钱而降低了计算能力。
结果就是一种“缩水通胀”:我们支付相同的订阅价格,但却要消耗更多的 Opus 令牌来应对无休止的重试,或者被迫花费更多的钱购买更昂贵的 Fable 令牌,才能获得我们曾经拥有的质量。
这里有人成功地将 Claude 迁移出复杂的工程工作流程了吗?你们用什么来替代它,又是如何处理过渡的?
免责声明:作为一名德语母语者,我使用了 Gemini 来清理和润色这篇帖子的英文文本。
查看原文
Since the recent updates, I have the feeling that Claude Opus is becoming dumber on complex tasks.<p>Things that used to work cleanly in a single prompt now fail completely. In coding workflows, it constantly ignores mandatory CLAUDE.md project rules, makes unsolicited edits to unrelated files, and breaks working code. It starts arguing based on stale comments, fails to update documentation when code changes, and edits based on blind guesswork instead of actually verifying the codebase first.<p>I even caught myself using Fable for tasks that I always used Opus for in the past, just to get decent results.<p>It feels like Anthropic is shifting their technical problems onto paying users. Either they are using strict safety filters that silently fall back to cheaper models without telling us, or they are downgrading the compute under heavy load to save money.<p>The result is the same kind of shrinkflation: we pay the same subscription price, but we either burn way more Opus tokens on endless retries, or we are forced to spend money on more expensive Fable tokens to get the quality we used to have.<p>Has anyone here successfully moved away from Claude for complex engineering workflows? What are you replacing it with, and how are you handling the transition?<p>Disclaimer: As a native German speaker, I used Gemini to clean up and polish the English text for this post.