我为什么更喜欢Opus 5而不是Fable 5
我从这两个工具发布的那一刻起就开始进行实验。经过四款游戏、三个网站和两个内容创作引擎的尝试，我觉得可以分享一些我的经验和看法。
### 关于 Fable 的观察
1. **金进金出** - 这意味着我在给 Fable 提供启动信息和提示之前，最好先做出所有设计决策。让它自己做决策会更轻松，但这些决策它不会告诉你，除非你明确告知它可以和不可以自己决定的内容。
2. **它是一个黑箱** - 这在某种程度上是对上述观点的延伸。我在向他人描述时用过一个代理机构的类比，即它会接受一个简报（Fable 自己称之为“订单”），然后独立进行处理，直到完成后才会回来。我曾经让 Fable 独立工作了 9 个小时，为我构建一个客户自助服务门户。我只需在每 5 小时达到会话限制时输入“继续”。
3. **它的能力惊人** - 如果你在前期通过 Opus 对话理清一切，你可以获得令人震惊的结果。它会创建自己的子代理，进行测试和自我验证，并将完成的产品交给你。这让我大为震惊。
### 但我更喜欢 Opus 5
为什么？因为它不是一个黑箱。
1. **它会反馈** - 它似乎会在自然的阶段节点暂停，并更新它所产生的内容及原因。这种节奏让用户保持参与感。
2. **它同样能够生成子代理并进行测试和验证**。
3. **它确实便宜得多** - 例如，当 Fable 执行任务时，我的 Claude Max 限制大约在 30 到 45 分钟内就会耗尽（Fable 非常快）。但这让我只能无所事事。Opus 5 在某种程度上感觉更有条理（这可能只是因为它会反馈给用户，导致节奏较慢）。或者更好的说法是，Opus 让你作为开发者在整个过程中保持参与。它似乎更关注于给你确切想要的东西。而 Fable 则不这样做，它基本上只是接受简报，然后按照自己的方式进行。
我只是想分享我的经验，因为我很快就熟悉了这些工具，认为这对正在尝试这些前沿模型的其他人可能会有价值。
期待你的想法。谢谢。
查看原文
I've been experimenting with both since the moment each came out. 4 games, 3 websites and 2 content creation engines later - I think I'm ready to share a bit of my experience and opinion.<p>WHAT I'VE NOTICED ABOUT FABLE<p>1. Gold in, gold out - meaning I've had the best results by making all my design decisions before giving Fable the kickoff information and prompt. It's much more comfortable making decisions by itself - decisions it won't tell you about - unless you explicitly tell it what it can and can't decide for itself up front.<p>2. It's a black box - which is an extention of the point above in a way. I've used the analogy of an agency when I've described it to people, i.e. it'll take a brief (what Fable itself describes as "an order") and go off and run with it, only coming back once it's done. I once had a Fable conversation work independently for 9 hours buidling out a client self-service portal for me. All I had to do was type 'Continue' once it hit its session limits every 5 hours.<p>3. It's insanely powerful - so if you've got everything worked out up front by thinking and working through it with an Opus conversation, you can get the most staggering results. It creates its own sub-agents, does its own testing and self-verification, and ships you back a finished product. It blew my mind.<p>BUT I PREFER OPUS 5<p>Why? Because it's not a black box.<p>1. It reports back - it seems to pause at natural phase gates and give an update on what it produced and why. There's a rhythm to it that keeps you the user involved.<p>2. It's just as capable of spinning up sub-agents and doing its own testing and verification.<p>3. It genuinely is a lot cheaper - for example when Fable runs on a task my Claude Max limits burn out in roughly 30 to 45 minutes (Fable is FAST). But then that leaves me twiddling my thumbs. Opus 5 feels more methodical somehow (which might just be because it comes back to the user, resulting in a slower cadence). Or maybe the better way of putting it is that Opus keeps you the developer involved throughout. And it feels like it's more interested in giving you exactly what you want. Fable doesn't do that - it basically just takes the brief and does its own thing.<p>I simply wanted to share my experience as I've quickly reached the point of familiarity and thought that might be valuable to others who are experimenting with these frontier models.<p>Look forward to your thoughts. Cheers.