@PawelHuryn claude sonnet better than opus?
원본그래서 실제 업무로 GPT-6.1 Sol을 테스트해 봤습니다: 저장소 2개, 심어놓은 버그 105개. 찾아서 가능한 한 고쳐봐. 그냥 너프된 GPT-5.6 Terra였던 기존 GPT-6 Sol과는 달리, 이건 진짜다. 결과: - GPT-6 Astra (max): $33에 45개 - GPT-6.1 Sol (max): $6.56에 44개 - GPT-5.6 Sol (max): $95.35에 43.5개 - Opus 5.5 (max): $58.53에 41.7개 - GPT-6 Sol (max): $9.33에 29.3개 이런 모델이 있다면, $200 플랜이 50% 인하된 건 중요하지 않다. n=1. 더 많은 실행 횟수와 다양한 노력 수준에서의 결과는 이 스레드에 계속 올라옵니다 ove
0
0
0
0
댓글 42
-
-
@PawelHuryn Sonnet 5.5 in first, what?
원본 -
@PawelHuryn @grok explain
원본 -
@PawelHuryn GPT 6.1 sol has been absolutely stupid for me. https://x.com/cyberpeterg/status/2105313537543303596?s=20
원본 -
@PawelHuryn what was the 1 bug Astra caught that Sol missed?
원본 -
@PawelHuryn Nuts
원본 -
@PawelHuryn 44 bugs, $6.56. Cost-per-fix is the ladder.
원본 -
@PawelHuryn WOWIE! amazing results :)
원본 -
@PawelHuryn @grok sol 6.1 is clearly cutting into OAI's margins. Is this "race to the bottom" reminiscent of early 2000's internet prices? When did this race start? When did it end? Outcomes?
원본 -
@PawelHuryn Просто на подписке за 200$ можно было бы бесконечно пользоваться 6.1 sol ultra и не покупать кредиты, openai это непонравилось😂
원본 -
@PawelHuryn do the fixes get checked for new bugs too, or just whether the planted ones are gone?
원본 -
@PawelHuryn Opus 5.5 at 41.7 for $58.53 against 6.1 Sol at 44 for $6.56 is the line that matters here. Once you log a few more runs, I'd love to see whether the misses overlap or whether Opus catches bugs Sol never touches, because that decides routing versus just picking one.
원본 -
@PawelHuryn how much you got from openai? "With a model like this, the 50% cut to the $200 plan doesn't matter." all these are just for this sentences to plant the idea it's ok. it's not ok bro.
원본 -
@PawelHuryn Short: 6.1 Sol finally sits on the right shelf. Not the bug king. The king of cost per bug found.
원본 -
@PawelHuryn Interesting
원본 -
@PawelHuryn There is alternative 3D visualization of the results, can make 3 axis comparison easier. https://icauro.com/toabundance?benchmark=bug-hunt
원본 -
@PawelHuryn The only problem? "remove the xx button from the page" ... 'valutating bla bla bla' ..... 10 minutes later 'button removed, i'll now verify if the button is not visible' ..... . 15 minutes... 'the button is removed and not present on the page' (but still in temp page) 30m tot
원본 -
@PawelHuryn thanks for running this and sharing the test results!
원본 -
@PawelHuryn A bit useless to show the highest level of AI. The real challenge comes when you test on medium.
원본 -
@PawelHuryn is it just me or is gpt 6.1 sol slow? what tps are you getting?
원본 -
@PawelHuryn In terms of criticality (identifying more impactful bugs), was GPT-6.1 Sol on par with GPT-6 Astra and Fable 5.1? Btw, thanks for this, this is gold! 🤝
원본 -
@PawelHuryn https://x.com/SlovenskiGlas1/status/2105265982948180341
원본 -
@PawelHuryn GPT 6.1 Sol is basically a telenovela: the cast is great, young, and gorgeous, the costumes are stunning, but almost nothing actually happens. You could easily skip four episodes and still not miss a beat.
원본 -
@PawelHuryn TY
원본 -
@PawelHuryn Glad you're adding n=3. I'd put a bug-by-bug stability view next to the totals: fixing 44 different bugs each run creates a different review workload from reliably fixing the same 44.
원본-
@jakestone2306 It's not 100% deterministic. Bugs differ a lot between runs. This view: https://bughunt.productcompass.pm/?preset=featured&view=coverage
원본-
@PawelHuryn @jakestone2306 GPT-5.6 Sol + GPT-6.1 Sol looks like an interesting combination or is it just a coincidence that one finds bugs at the end the other one missed ?
원본-
@PawelHuryn @jakestone2306 Uh, just saw that GPT-5.6 Sol is horrible expensive, I would get away cheaper with Astra ! ... but combination of multiple models might be a cost effective approach to try.
원본-
@SvenMeyer It could be complementary coverage, or just run-to-run variation. I'd compare two passes of one model with one pass each of two models, at the same total budget. Count newly fixed bugs on the second pass, not just the combined score.
원본
-
-
-
-
-
@PawelHuryn For finding bugs, does it make sense to first run Sol 6.1. Then run Opus 5.5 with the knowledge of known bugs from Sol. Can it lower the total cost while catching more bugs?
원본 -
@PawelHuryn i used 6.1 for bug findings. it was much better than opus 5.5. but opus is much better in performance, design and smart code
원본 -
@PawelHuryn 跟我在實際工作中使用6.1 sol xhigh 的體感一樣，有好又省！好像有點慢？
원본 -
@PawelHuryn I would advise against testing every model on Max reasoning. Most tend perform better on Medium or High, like my test here where Terra and Luna both suffer on Max:
원본 -
@PawelHuryn The real story is the price ratio, not the score — 44 bugs for $6.56 vs 45 for $33. At one-fifth the cost you can just run five passes and brute-force the gap. Makes the whole "Astra got shelved for safety" line look more like a pricing problem.
원본 -
@PawelHuryn 6.1 sol’s performance for the price is honestly wild.
원본 -
@PawelHuryn Great overview! Are you planning to also check gpt-6.1-luna?
원본 -
@PawelHuryn it matters. this model ships far more slop than 6 sol did
원본 -
@PawelHuryn Would be nice to see amount of slop and regressions introduced. Gemini for me was terrible for fixing things, it wasn't using good architecture, patterns and introduced a lot of regression. But the results may actually vary by how good your agentic context is in the workspace.
원본
스크롤하면 더 불러옵니다