Claude · 近 7 天
Claude Opus 5.5
0–100 分,越高代表社区使用体验越正面,不代表能力测试成绩。
更新于 2026-10-01 17:02 UTC · 2026-09-24 – 2026-10-01 UTC体感分80.7/100960 条评论 · 近 7 天
大家怎么看
有用户认为 Claude Opus 5.5 在提供高层次对抗性"该不该做"的建议上优于 GPT-6.1,因为 GPT-6.1 会顺着任何错误路径一路走下去。有用户认为Claude Opus 5.5现在每次提示消耗的token比刚发布时明显增多。
样本与评分说明
截至 2026-10-01 17:07:03 UTC,Claude 家族的 Claude Opus 5.5 在近 7 天有 960 条明确归属该版本的社区反馈,社区口碑分为 80.7/100。部分有效分类评分:通用文本 77.8/100 (n=359);编程 83.3/100 (n=103);推理 89.2/100 (n=282)。 评分方法与数据来源
社区评论
精选近 7 天的不同意见,摘录条数不代表真实好评比例。
3 条精选摘录
额度评价来自社区体验,不能据此推算官方实际配额。
展开原文
I feel like im using way more tokens per prompt than i did when it launched.
展开原文
opus now is heavy loaded, so expect the slop to taste worse
展开原文
The prompt cache has likely expired, so your next message will re-cache about 864k tokens.
展开原文
better at giving a high level adversarial
查看评论上下文
我发现 Opus 5.5 更擅长提供高层次的对抗性「你一开始就应该这样做」,而 GPT-6.1 则乐于走上任何错误的道路。
机器翻译展开原文
I find Opus 5.5 is better at giving a high level adversarial "should you do this to begin with" where GPT-6.1 is happy to go down any wrong path.
展开原文
super happy with opus 5.5
展开原文
5.5 fixes this in my experience, if you give it a clear task and an environment where it can freely document it's progress as it goes it keeps going with lazer focus like this.
查看评论上下文
Opus 5 则恰恰相反,你给它一大串任务,它大约完成 10-25% 就提前退出,解释它为什么停下来,而不是去调查它在途中发现的那些复杂问题。
机器翻译展开原文
Opus 5 was the opposite where you give it a big list of tasks, does about 10-25% of it then drops out early explaining why it stopped instead of just investigating the complications it found on the way.
展开原文
Between cost, spend, and code quality I can literally prove that something has changed.
查看评论上下文
在过去的六天里,Opus 5.5(O5.5)在 Claude Code 中对我的表现非常出色。开箱即用的架构优先、DRY/SOLID 编码,出色的沟通风格,惊人的 token 效率。从上周三开始,我基本上不间断地使用它,每天大约 12 个小时。 但就在今晚我的月度限额重置前后,我注意到沟通风格和编码行为发生了*极端*的转变,感觉可疑地像 Opus 5(O5)。在过去一周里,O5.5 会接受我的需求并立即开始工作,通常几分钟内就能完成一个功能,在实现、用户体验、架构和 token 效率方面都做得令人难以置信。而今晚,我看到的情况截然不同。
机器翻译展开原文
Opus 5.5 (O5.5) has been exceptional for me in Claude Code over the last six days. Architecture-first, DRY/SOLID coding out of the box, exceptional communication style, phenomenal token efficiency. I’ve been working with it basically nonstop, ~12 hours a day, since last Wednesday. But right around the time my monthly limit reset this evening, I noticed an extreme shift in communication style and coding behavior that feels suspiciously like Opus 5 (O5). For the last week, O5.5 would take my requirements and immediately get to work, usually knocking out a feature in minutes and doing an incredible job across implementation, UX, architecture, and token efficiency. Tonight, I’m seeing something very different.
O5.5 一直始终如一地尊重 DRY 原则和现有架构,而今晚创建的模块却突然乐于重新发明之前已有的每一个轮子。能力上的差异并不微妙。 *另一个*迹象是 token 使用量。与 O5 相比,O5.5 的效率惊人,而 O5 绝对是一个吞噬 token 的怪物。我用 O5.5 以一小部分 token 使用量完成了多得多的功能工作。而今晚,简单的任务和相对较小的功能突然以更接近 O5 的速度吞噬 token。 我对此特别敏感,因为每次达到消费上限时我都必须申请提高额度。用 O5 时,我几乎每天都要提交一次请求。用 O5.5 时,我整个星期都不需要提交一次。然后今晚,我在大约一个小时内从约 70% 的使用量跳到了 90%。
机器翻译展开原文
Where O5.5 consistently respected DRY principles and the existing architecture, the modules created tonight are suddenly happy to reinvent every wheel that came before them. The difference in ability is not subtle. The other tell is token usage. O5.5 has been startlingly efficient compared with O5, which was an absolute token-eating monster. I’ve been getting substantially more feature work done with O5.5 at a fraction of the token usage. Tonight, simple tasks and relatively small features are suddenly devouring tokens at a pace that feels much more like O5. I’m especially sensitive to this because I have to request an increase in my spend limit every time I hit it. On O5, I was sending a request almost every day. On O5.5, I hadn’t needed to send a single one all week. Then tonight I jumped from roughly 70% to 90% usage in about an hour.
展开原文
also set to just use opus 5.5 for harder tasks
展开原文
I’ve had opus5.5 push back… in one case I explained it’s a game, and yeah, we made a game that does exactly what I wanted to do.
展开原文
in terms of creativity, creating new things, yeah opus 5.5 is fantastic
展开原文
Opus feels faster and lets people work longer
查看评论上下文
更广泛的抱怨是一致的:Sol 6.1又慢又耗配额,而Opus感觉更快,让人在用量表开始报警之前能工作更久。
机器翻译展开原文
The broader complaints line up: Sol 6.1 is slow and quota-hungry, while Opus feels faster and lets people work longer before the usage meter starts screaming.
展开原文
I can’t even put reasoning traces in front of opus 5.5 without hitting a “reasoning extraction” claude code notice guardrail?
展开原文
it catches many mistakes made by Opus 5.5
查看评论上下文
SOL 5.6 和 6.1 都是高水平后端编码的怪兽。
机器翻译展开原文
SOL 5.6 and 6.1 both are monsters for high level backend coding.
展开原文
i am still getting the same push back
查看评论上下文
我刚尝试切换到"接受编辑开启"模式,我仍然遇到同样的拒绝。
机器翻译展开原文
I just tried switching to the "accept edits on" mode, i am still getting the same push back.
我会手动登录我的网上银行,我会让 Claude 选择收款人,然后通过 playwright 或 chrome connect 输入支付金额。我将是授权支付的人,但使用 Opus 5.5 和我尝试过的其他几个版本(包括 Sonnet),它似乎拒绝做任何工作!
机器翻译展开原文
I would manually log into my online banking, I would let Claude select the payees and then insert the amount to pay via playwright or chrome connect. I would be the one authorising the payment, but with the Opus 5.5 And a few other versions that I've tried, including Sonnet it seems to refuse to do any of the work!
展开原文
made a very simple mistake, and another simple mistake, again
展开原文
nearly unlimited use
展开原文
it is also little slow even compared to Astra
展开原文
It solved all the issues I had in 2 days, when I was thinking about working for 10 days with GPT
展开原文
I thought Astra was good until I had Opus 5.5 look at the code it generated
展开原文
Opus 5.5 is better at code reviewing than 6.1 Sol
展开原文
waiting on my weekly reset there
查看评论上下文
Opus 5.5 迄今为止要好得多。
机器翻译展开原文
Opus 5.5 is by far much better.
不过,已经用完了我每周(5倍计划)用量的 76%。
机器翻译展开原文
Used up 76% of my weekly (5x plan) usage, though.
展开原文
Agent rules are more strongly adhered to than claude.mds are at least with Opus 5.5
展开原文
outright ignores what the user has stated as facts and doesn't ask when those dont align
展开原文
Opus 5.5 is a mind blowing leap and barely sips use.
展开原文
I get about the same amount of usage with opus 5.5 on the claude 20$ sub as I get with astra on the 200$ plan. very worth switching.
展开原文
claude opus 5.5 in VS code extension does not
查看评论上下文
截至最新更新,我甚至无法让 Opus 5.5 在我的测试数据库中创建一个虚构用户来测试登录界面,因为它完全拒绝处理密码输入。
机器翻译展开原文
As of the latest update, I cannot even get Opus 5.5 to create a fictional user in my test database to test the login UI because it refuses to handle password inputs altogether.
展开原文
Opus 5.5 (I use it for work writing C#) seems faster than Opus 5, but it doesn't seem demonstrably better to my eyes and is still prone to word vomit
展开原文
I have yet to have Opus 5.5 block me from doing any of my usual security testing, validation, and remediation work under the CVP.
展开原文
Opus is clearly better in logic and processing steps, but often skips some or does something else entirely
展开原文
graphics would be 10x better
查看评论上下文
它始于我输入到Claude Code中的一条提示词:“*仅使用像素直接重制一个精美的宝可梦红重制版……绝对的像素艺术完美。
机器翻译展开原文
It started from one prompt I typed into Claude Code: "*using only pixels directly remake a beautiful pokemon red remake … absolute pixel art perfection.
* 完全没有图像文件。 游戏逐像素绘制到 320×180 的屏幕上。
机器翻译展开原文
* No image files at all. The game draws into a 320×180 screen pixel by pixel.
展开原文
Opus 5.5 has significantly better vision, which might mean for game dev you're using it more
展开原文
Fr I cant stress enough how amazing Opus 5.5 is in that category.
查看评论上下文
我把我的 Minecraft 模组文件给了 Opus 5.5,并告诉它制作一个预告片
机器翻译展开原文
I gave Opus 5.5 my Minecraft mod file and told it to create a Trailer
展开原文
Its super fast too. Not better than astra but atleast 5x faster
展开原文
Opus 5.5 provides the smoothest LLM experience i ever had, but it did one very odd thing where my macbook ram went full and i had to restart the machine to continue
展开原文
Neither Astra nor Opus 5.5 could recognize that a UI design with cropped borders—caused by insufficient padding—was problematic.
近 7 天暂时没有符合此筛选条件的精选评论。