Claude Opus 5.5 Fast Mode vs Normal Mode!
@SKatalystAI2,5 тыс. подписчиков
14 974 просмотра
14 комментариев
Комментарии из оригинального поста в X (Twitter)

@SKatalystAI
P.S. Here's the strange part: Yesterday, Opus 5.5 scored 7/9 on the same challenge. Today, Normal High dropped to 5/9 and Fast High reached 6/9
2 отметки «Нравится»

@SKatalystAI
Summarized results:
2 отметки «Нравится»

@thededale_
did both modes miss the same hidden checks or different ones? if it's the same ones i'd blame the model and stop paying extra for fast
1 отметка «Нравится»

@SKatalystAI
Mostly the same! Both missed GT-02 (payment concurrency), GT-03 (invoice atomicity), and GT-09 (voided invoice billing). Normal also missed GT-06 (N+1 queries), which Fast caught So Fast was 2.1× quicker but didn't resolve the three critical billing issues. What's more concerning is the consistency: Opus scored 7/9 yesterday on the same challenge, versus 5/9 Normal and 6/9 Fast today. These are signature-based results, but it's making me question the model's reliability more than the Fast Mode premium😅

@Delwo_A
What do you think, just the extra cost on speed justify the extra usage we pay
1 отметка «Нравится»

@LeifFC
Interesting
1 отметка «Нравится»

@zengshan9
多修一个缺陷签名那 0.15 倍的成本我认了,我自己用 AI 写代码也遇到过快跑完了但边界 case 还漏着,宁可慢一点把那个签名补上,后面排查比从头重来省事多了。
1 отметка «Нравится»

@SKatalystAI
Exactly! and that's what concerns me most. Both runs declared the repository ready to ship despite missing critical billing defects. 😅 Fast Mode was quicker and caught one additional signature, but neither actually completed the challenge. I'd rather have an agent take longer and catch the serious issues than finish faster with false confidence
1 отметка «Нравится»

@zengshan9
billing 这类边界缺陷多跑一轮把签名补全,后面踩坑的代价远大于慢一点。我自己跑 Claude Code 也是,边界 case 没跑通就不敢合。
1 отметка «Нравится»

@Seti_Here
Fsaat mode is such a scam
1 отметка «Нравится»

@ChrisLee207
2.1× 更快、1.85× 成本还改路径,说明 Fast 不是同轨迹加速,是另一条执行策略。落地:别拿单次跑决定开不开——同一验收集连跑 3 次,看缺陷签名和测试增量是否稳定;隐藏检查没过就宣称 ready,更说明要先钉验收再比速度。
1 отметка «Нравится»

@Laz01L
Wow this is crazy I need to try it

@aiceodev
Crazy how much faster Fast Mode is while still improving accuracy. If that 1.85× cost holds up, it could change how folks approach long coding sprints for real.

@Rolezn
I'd compare two Normal runs too. If those diverge just as much, the different execution paths may say more about run-to-run variation than Fast Mode.