Fable 5 is the biggest step up I’ve felt in our models since Opus 4.5 back in November. After 4.5 came out I uninstalled my IDE when I realized that I’d been doing 100% of my coding in a terminal for a few weeks. With Fable, it’s felt like Claude has stepped up from being a coding agent to a thought and design partner in building the product. Fable has judgement, taste, and dimensionality in a way that previous models didn’t, leading me to trust it more with the most complex work. I think the first time I had this realization was when I asked Fable to debug something. It is the first model I have used that was so methodical and precise, taking measurements and adding logs then verifying that it truly fixed the issue before declaring victory. There’s nothing in claude code’s prompting telling the model to do that, it’s just part of its personality. It really has this “big model smell” that I haven’t felt before.
Fable 5 是自去年 11 月的 Opus 4.5 以来，我在我们模型上感受到的最大一次跃升。4.5 发布后，当我意识到自己连续几周 100% 都是在 terminal（终端）里写代码时，我就把 IDE 卸载了。用了 Fable 之后，我感觉 Claude 已经从一个 coding agent（编程 agent）升级成了与我一起构建产品的思考与设计伙伴。Fable 具备以往模型所没有的 judgement（判断力）、taste（品味）和 dimensionality（维度感），这让我更愿意把最复杂的工作交给它。我第一次真正意识到这一点，应该是在我让 Fable 去 debug（调试）某个问题的时候。它是我用过的第一个如此有条理、如此精确的模型：会先做测量、添加日志，再确认问题确实被修复之后才宣告完成。claude code 的 prompting（提示词）里并没有任何内容要求模型这么做，这就是它个性的一部分。它确实有一种我以前从未感受过的“big model smell”。
We talk a lot about how important it is to set up self-verification loops. Especially in the age of powerful models that can run for long periods of time, self-verification is a key ingredient that enables the model to run for much longer, delivering a result that is closer to what you intended, so you can do more without having to constantly check in on Claude as it works. @delba_oliveira gives a great breakdown of what that looks like and why it matters
我们经常讨论，建立 self-verification loops（自我验证循环）有多么重要。尤其是在强大模型可以长时间持续运行的时代，self-verification 是一个关键要素，它让模型能够运行更久，交付出更接近你原本意图的结果，这样你就能做更多事情，而不必在 Claude 工作时一直不断去盯着它。@delba_oliveira 对这具体是什么样子、以及它为什么重要，做了非常出色的拆解。