GPT-5.6: what developers actually say
We read every Hacker News comment from Nov 2025 – Nov 2026 that gave a real opinion on GPT-5.6. 26 of the 33 opinions come from people who say they use it themselves.
Developers give GPT-5.6 a 76% approval score across 33 opinions, and 26 of those come from firsthand use. Code quality is the strongest signal at 11 positive and 2 negative mentions. Reliability is split at 5 positive and 5 negative, with complaints about ignored scope, deleted code, and refused tasks. Monthly approval fell from 89 in August to 56 in September on 8 opinions, so the 90-day score of 75 hides a recent dip.
Pick it if
- Want root-cause fixes in an existing codebase
- Care about clean interfaces and low token use
- Prefer clear communication from the agent
Look elsewhere if
- Need strict instruction following on scoped tasks
- Need an agent that never refuses security work
- Are on a tight budget
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.
How opinion has moved
What developers say
Praise
Complaints
Summaries are paraphrased. Each links to the original comment.
FAQ
Is GPT-5.6 worth it?
Most developers say yes for code quality. It scored 76% approval, and users report it finds root causes and uses fewer tokens than peers. The main cost is reliability: half the reliability comments were negative, citing mid-task stops and ignored instructions.
Is GPT-5.6 better than Claude Opus 4.8?
One developer preferred GPT-5.6 to Claude Opus 4.8, and another praised its communication compared with Claude. No one in the data preferred a competing model instead. The sample is small, so treat this as a weak signal.
How reliable is GPT-5.6 for coding?
Mixed. Reliability drew 5 positive and 5 negative comments. Complaints include deleting unrelated code, adding regressions, and leaving thinking in code comments. Some users also report refusals on security-testing prompts.