GPT-5.6 Sol vs Claude Opus 5: what 10 developers chose.
409 opinions. 10 developers named a direct preference: GPT-5.6 Sol 7–3. Approval is 67% vs 33%.
If you want code quality, choose GPT-5.6 Sol. If you want cost & pricing, choose Claude Opus 5. The 7–3 direct split is not a landslide; it is a difference in working style.
Choose GPT-5.6 Sol if you…
- You want the higher overall approval and the larger body of reported use
- Code quality, speed and UX mentions carry the most weight
- You want the model most commenters in this sample switched to
Choose Claude Opus 5 if you…
- You need a second model for review and planning
- Per-token output price matters
- You can constrain it tightly and verify its work
Code quality for GPT-5.6 Sol. Cost & pricing for Claude Opus 5.
Net sentiment per topic: praise minus complaints, as a share of mentions. Positive means more praise than complaints. Hover a dot for the raw counts.
Net sentiment = praise minus complaints, as a share of each tool's mentions. The dot lanes are only for readability; position is the score.
View data table
| Topic | GPT-5.6 Sol | Claude Opus 5 | Mentions |
|---|---|---|---|
| Code quality | +47 | -20 | 99 / 60 |
| Cost & pricing | +69 | +14 | 26 / 7 |
| Reliability | -23 | -93 | 26 / 27 |
| Autonomy | 0 | -41 | 18 / 17 |
| UX | +71 | -90 | 7 / 21 |
| Speed | +75 | +20 | 16 / 5 |
| Usage limits | -9 | -100 | 11 / 3 |
The same decision, from both sides.
Paraphrased from comments where a developer named a preference or described a switch. Each links to the original.
Picked GPT-5.6 Sol 7 developers
A Claude Code user switched to Sol because Opus 5's prose was hard to read during frequent context switching.
When I say total market capture I mean in the March time frame. At that point Claude code / 4.6 was so far beyond any competition even meta abandoned their entire internal coding harness and fine tuning efforts in favor of large scale Claude code adoption. Codex was far behind, Gemini was a non entity, Chinese models hadn’t had their moment (and frankly aren’t practical to this day for enterprise work due to PRC concerns). The world was cursor, aider, and a few others with an unclear superior model. 4-6 was strikingly better - if could develop autonomously from a spec to done with generally hi
Reports that Opus 5 worked at launch but degraded, with no visibility into the model actually running.
Finds Sol writes much terser code comments and error messages than Opus 5, sometimes ten times shorter for the same prompt.
Picked Claude Opus 5 3 developers
The writing style is extremely frustrating/maddening! I’ve tried so many things and I have to beat Opus 5/Fable 5 over their head every time. With Opus 5, the failure to actually improve the writing is borderline comical. Both models have been building up tomes of memories on top of my core rules, all to be ignored. Nothing sticks mid-writing! The only lever is to ask to revise after the fact, a particularly futile proposition for anything non-trivial with Opus 5. In contrast, GPT 5.6 Sol Max absolutely obeys my edicts to write well. I selected the concise writing style and its default writing
Argues Sol was overhyped and, on one small auth ticket, wrote 25,000 lines over three hours.
Notes Opus 5 output costs less per million tokens than Sol and slightly beats it on agentic coding benchmarks.
The numbers.
| Metric | GPT-5.6 Sol | Claude Opus 5 |
|---|---|---|
| Approval | 67% | 33% |
| Last 90 days | 66% | 30% |
| Opinions | 247 | 162 |
| Developers | 206 | 148 |
| First-hand opinions | 210 | 136 |
| Direct picks | 7 | 3 |
| Type | Model | Model |
| Made by | — | — |
Related matchups.
GPT-5.6 Sol vs Claude Fable 5
10–4 direct picks, and a clear difference in what developers optimise for.
Claude Opus 5 vs Claude Opus 4.8
7–2 direct picks, and a clear difference in what developers optimise for.
Claude Fable 5 vs Claude Opus 5
5–4 direct picks, and a clear difference in what developers optimise for.
How to read this comparison.
Approval is the positive share of opinions that took a side, with the rank based on the lower bound of a 90% confidence interval. Direct picks count comments where a developer explicitly preferred one tool or described switching. Small samples are noisier; check the opinion counts.
Get the monthly report
Which AI coding tools gained or lost developer approval on Hacker News, and why people switched. One email a month.