DevConsensus
Models / GPT-5.5
Model · HN opinions Nov 2025 – Nov 2026

GPT-5.5: what developers actually say

We read every Hacker News comment from Nov 2025 – Nov 2026 that gave a real opinion on GPT-5.5. 203 of the 236 opinions come from people who say they use it themselves.

69%approval, all opinions
67%approval, last 90 days
#16of 45 models ranked
221different developers

Developers give GPT-5.5 69% approval across 236 opinions from 221 authors, and 203 of those opinions come from firsthand use. Code quality drives the score with 91 positive mentions against 23 negative, and speed is the cleanest signal at 13 to 1. Reliability is close to even at 17 positive and 15 negative, and long sessions after context compaction draw repeated complaints. Approval held at 73 to 74 in May and June, fell to 57 in July, and sits at 67 over the last 90 days on thin recent volume.

Pick it if

  • Want high code quality marks (91 positive mentions to 23 negative)
  • Care about speed (13 positive to 1 negative)
  • Already work in Codex or Copilot and want a cheaper option

Look elsewhere if

  • Need steady reliability across long sessions (17 positive to 15 negative)
  • Depend on context compaction to keep a plan on track
  • Need clean edits without extra indirection or missed formatting steps

Strengths and weaknesses

Each row counts opinions that mentioned the topic. Bars to the right of the line are praise, bars to the left are complaints.

PraiseComplaints
Code quality
23
91
Reliability
15
17
Cost & pricing
8
10
Autonomy
6
9
Speed
1
13
Usage limits
2
3
UX
2
1

How opinion has moved

050100Apr '26May '26Jun '26Jul '26Aug '26Sep '26
Monthly approval (line) and number of opinions (bars). Months with fewer than 3 opinions are left out.

What developers say

Praise

Uses GPT-5.5 in Copilot for heavy Visual Studio work, calling it more than sufficient for under $100/month.HN comment · Oct 19, 2026
Finds GPT-5.5 medium much better for embedded Lisp and C, with clearer, more direct output.HN comment · Sep 22, 2026
Says GPT-5.5 is still their main driver for coding work.HN comment · Sep 13, 2026
Finds GPT-5.5 models more than enough for most programming tasks.HN comment · Aug 20, 2026
Calls GPT-5.5 the fastest model they have used, finishing a similar task far sooner than Qwen 3.8.HN comment · Aug 19, 2026
Says GPT-5.5 and 5.6 are both quite capable.HN comment · Aug 14, 2026
Has not moved off GPT-5.5 in Codex and finds it better for their work than Claude.HN comment · Aug 14, 2026
Moved four drifting long Codex sessions from GPT-5.6 Sol to GPT-5.5 to check their goals.HN comment · Aug 10, 2026

Complaints

Says GPT-5.5 struggled with standard GHC Haskell, needing more turns than for Java or TypeScript.HN comment · Sep 25, 2026
Says GPT-5.5 compaction had major issues and its reasoning output became less coherent.HN comment · Sep 17, 2026
Says GPT-5.5 did not stay on track after context compaction.HN comment · Sep 5, 2026
Says GPT-5.5 was bad, and usage resets and bugs made them stop paying $200/mo.HN comment · Jul 19, 2026
Says some bugs in their Elixir app elude GPT-5.5 and Opus.HN comment · Jul 12, 2026
Says GPT-5.5 keeps adding pointless indirection to functions in their main project, hurting productivity.HN comment · Jul 10, 2026
Says GPT-5.5 couldn't reliably apply a reasonably sized formatting skill, so they switched.HN comment · Jul 10, 2026
Switched away from GPT-5.5 after it refused to build a downloader tool.HN comment · Jul 10, 2026

Summaries are paraphrased. Each links to the original comment.

GPT-5.5 compared

FAQ

Is GPT-5.5 worth it?

Approval sits at 69% across 236 opinions, 203 of them from firsthand use. Code quality is the main reason, at 91 positive mentions against 23 negative. Recent approval is 67 over the last 90 days.

Is GPT-5.5 better than Claude Opus 4.8?

Developers split on it. Twelve preferred GPT-5.5 over Opus 4.8, and eight preferred Opus 4.8. Against Opus 4.7 the gap is wider at 12 to 3, while 8 developers chose Claude Fable 5 over GPT-5.5 against 5 the other way.

Why do developers stop using GPT-5.5?

The common reasons are context compaction losing the thread and edits that add unneeded indirection. A few cite refusals on tool builds and bugs in Elixir. One developer dropped a $200/month plan over usage resets and bugs.