问HN：Claude Opus的性能会受到时间的影响吗？
我非常喜欢Claude Opus，因为它在理解功能请求方面表现得非常出色，并且通常能够与我的代码库保持一致（我的代码库完全是用Opus从零开始编写的）。<p>我最近注意到，当我在晚上（美国东部时间）使用Opus时，它在处理我定期提交的相同类型请求时，常常会陷入极端的思维误区。它更倾向于进行一些会破坏代码的重构，然后在这些错误上反复迭代，形成一种螺旋式的错误循环。一个通常只需3-4分钟的请求，可能会变成一次10分钟的冒险，直到我撤回更改，指出错误，然后再试一次。它会乐于承认错误，但这种模式似乎一直存在。<p>我还没有进行过类似的对比测试，这会很有趣，但有没有其他人注意到同样的问题？
查看原文
I am a big fan of Claude Opus as it has been very good at understanding feature requests and generally staying consistent with my codebase (completely written from scratch using Opus).<p>I've noticed recently that when I am using Opus at night (Eastern US), I am seeing it go down extreme rabbit holes on the same types of requests I am putting through on a regular basis. It is more likely to undertake refactors that break the code and then iterates on those errors in a sort of spiral. A request that would normally take 3-4 minutes will turn into a 10 minute adventure before I revert the changes, call out the mistake, and try again. It will happily admit the mistake, but the pattern seems to be consistent.<p>I haven't performed a like for like test and that would be interesting, but has anyone else noticed the same?