Between May and late July 2026, OpenAI and Anthropic shipped more than thirty user-facing products and features: new voice modes, health-record integrations, personal finance, a desktop redesign, rewritten memory systems, an enterprise agent product, and two frontier-model families apiece.
Most of them arrived with an announcement, a demo, a burst of press coverage—and then disappeared from public conversation.
I wanted to understand the gap between what companies announced and what users found worth discussing. Not what the press covered; the press covers almost everything. I looked instead at public conversations on Hacker News, Reddit’s AI communities, and X, then ranked launches by a deliberately simple question:
Did people care enough to argue about it?
That question reorganizes the last three months.
The one-sentence version
Users rarely talked about conventional product features. They talked about models, prices, outages, privacy, and who controls access.
Every top-tier discussion in this dataset concerned a model release, a governance fight, or something breaking. The few exceptions are instructive: they either solved a specific infrastructure problem or gave users something they could create and share with one another.
A note on the numbers
This is a study of public attention, not adoption, retention, revenue, or product value. Quiet features can be heavily used, and loud controversies can involve a relatively small population.
I reviewed English-language discussions posted between May 1 and July 28, 2026, on Hacker News, prominent AI-related subreddits, and X. The figures below are raw engagement counts from each platform, not a composite score; an HN point, Reddit upvote, X like, and comment are not equivalent units. Keyword searches also miss conversations that use unexpected names.
The cutoff particularly disadvantages late-July launches, which had only days to accumulate attention. Treat the rankings as a map of visible conversation—not a definitive measure of what succeeded.
Tier 1: The stories that consumed the conversation
1. The Fable 5 / Mythos 5 export-control saga
Anthropic launched Claude Fable 5 on June 9, its first publicly available Mythos-class model. Three days later, the US Department of Commerce issued a directive forcing Anthropic to suspend access to both Fable 5 and Mythos 5. The controls were lifted on June 30.
This was not primarily a product story. It was a sovereignty story, and it dwarfed almost everything else:
| Hacker News thread | Points | Comments |
|---|---|---|
| Statement on US government directive to suspend access | 3,158 | 2,314 |
| Claude Fable 5 launch | 2,626 | 2,160 |
| Commerce has lifted export controls | 977 | 692 |
| Feds freaked over Fable 5 after “fix this code” | 613 | 361 |
| Fable 5 is Back | 408 | 419 |
Reddit followed just as closely. “Fable 5 is coming back!” received 5,338 upvotes and 506 comments; “Access has been extended!” received 5,273 and 777; “Fable staying on Max” received 3,279 and 724.
What made the episode detonate was not only the model’s capability. A government had reached into a commercial service and switched off a model on which people already depended.
The discussion immediately moved beyond benchmarks and into arms-control law. One widely upvoted comment noted that the directives fell under the Arms Export Control Act, potentially treating model weights as technical data under ITAR. Another observed that the restrictions reportedly prevented Anthropic’s own foreign employees from accessing Mythos internally—a constraint likely to be commercially intolerable.
A substantial faction blamed Anthropic’s own political strategy:
“Would the US government have slapped Anthropic with this export control if Anthropic never fearmonger’ed about Mythos? I think the answer is very likely no. […] This is a failure of Anthropic’s politicking.”
Across dozens of threads, the durable conclusion was the same: access you do not control is conditional access. One commenter put it plainly:
“Open weights + deterministic orchestration feels like the only sane long-term bet.”
For much of June, this argument crowded almost everything else out.
2. GPT-5.6 Sol—and who gets to use it
OpenAI previewed GPT-5.6 Sol on June 26 and released it on July 9. It was the company’s largest story of the quarter by a wide margin: roughly 5,000 Hacker News points across the five leading threads, while the largest announcement post on X drew 6,212 likes and 976,000 views.
But the distribution of attention matters:
| Hacker News thread | Points | Comments |
|---|---|---|
| GPT-5.6 launch | 1,561 | 1,113 |
| U.S. government will decide who gets to use GPT-5.6 | 1,184 | 1,240 |
| Previewing GPT-5.6 Sol | 1,139 | 744 |
| GPT-5.6 used a prompt to close a 30-year gap in convex optimization | 600 | 391 |
| GPT-5.6 Sol Ultra produces proof of the Cycle Double Cover Conjecture | 538 | 443 |
The access-control thread attracted more comments than the launch itself. It expressed the same anxiety as the Fable 5 episode, this time around a different vendor: people were evaluating not only what the model could do, but whether they could build on it without a third party later changing the terms.
The other major branch of the Sol conversation was capability-real. Users discussed claimed mathematical advances and verified results rather than benchmark deltas. But practitioner complaints were equally concrete, especially when safety refusals consumed paid sessions:
“GPT-5.6 Sol finds a vulnerability but refuses to explain it. I think it would be a good practice to refund the session cost in that case. Otherwise a customer just spent some money in order to get exactly nothing.”
The model earned attention through capability. The service around it earned scrutiny through control and pricing.
3. Claude Opus 5—and an immediate split
Opus 5, released July 24, produced the largest single engagement number in the dataset. Anthropic’s announcement on X reached 61,266 likes and 23 million views. The Hacker News launch thread drew 1,777 points and 1,329 comments; Reddit’s drew 2,916 upvotes and 672 comments.
Within 72 hours, however, the mood split:
- “Claude Opus 5 is ridiculously good at web design”—643 likes
- “How are we feeling about Opus 5 so far?”—2,453 likes
- “I do not like Opus 5 as much as I hoped to :(”—2,428 likes
- Three separate Hacker News threads about elevated Opus 5 errors reached the front page in four days
The recurring technical complaint concerned defaults more than raw capability:
“I was using Opus 4.6 until 2 days ago with no CLAUDE.md or anything and it was great. Tried out Opus 5 and it’s been a super annoying experience out of the box.”
A Reddit post titled “A week on Opus 5—best value at the frontier, but 3 default settings aren’t good” captured the emerging consensus. Users often liked the model and disliked the configuration in which it arrived.
That distinction matters because it describes a fixable product problem. Benchmarks can reveal capability; forum complaints reveal the friction between that capability and its default presentation.
Some heavy users still preferred the older, more expensive Fable 5 for difficult work:
“I believe Fable is the sharpest and most effective instrument I’ve ever used in AI.”
4. Claude Opus 4.8
Opus 4.8, released May 28, generated 1,774 Hacker News points and 1,376 comments. Its central pitch—roughly four times less likely than 4.7 to overlook flaws in its own code—addressed a problem its audience had already been discussing.
It produced one large thread, landed cleanly, and remained unusually uncontroversial. In this dataset, that is a compliment.
Tier 2: Real, but second-order
Claude Code became a political object
Claude Code appeared in 5,559 Hacker News comments, but its most prominent threads were rarely about new features:
| Hacker News thread | Points | Comments |
|---|---|---|
| Claude Code is steganographically marking requests | 2,445 | 750 |
| Claude Code uses Bun written in Rust now | 608 | 849 |
| Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k | 706 | 396 |
| Microsoft starts canceling Claude Code licenses | 493 | 466 |
| I used Claude Code to get a second opinion on my MRI | 566 | 715 |
Trust, token efficiency, procurement, and off-label medical use dominated. The period’s actual feature releases—dynamic workflows, nested subagents, and background code review—barely registered independently.
Claude subagents attracted 237 comments, and the strongest-performing subagent thread was itself a complaint: “Claude Code has a hardcoded instruction telling Opus 5 not to use subagents.”
The lesson for developer-tool companies is simple: at sufficient scale, the changelog stops being the story. The product’s behavior becomes the story.
Usage limits: the feature nobody shipped and everybody discussed
Usage-limit discussions produced 223 Hacker News comments, while Reddit’s “Dear Anthropic, This Has to STOP.” drew 2,673 upvotes and 555 comments.
Pricing and rate limits generated more sustained, emotionally intense discussion than voice, health, memory, personal finance, and the desktop redesign combined.
“I’m not in a position to drop $200/month […] for coding tasks Kimi 2.6 has been about the same as Sonnet in my experience.”
“That’s the difference between ‘I don’t use it for anything serious because I constantly run into limits’ and…”
Every limits thread doubled as a churn thread. They read like unsolicited exit interviews and repeatedly named the same alternatives: Kimi, DeepSeek V4, GLM, and local models.
This may be the most commercially dangerous conversation surrounding either company. It is not a feature problem; it is the point at which pricing and reliability determine whether capability can become habit.
Security and privacy incidents outperformed launches on Reddit
The largest substantive Reddit post in the dataset was not a launch. “You can view a lot of shared conversations via Google” drew 8,066 upvotes and 1,340 comments, while a companion post about the same apparent exposure received 4,221 upvotes.
Together, those posts attracted more engagement than Opus 5, Sonnet 5, and Claude Skills combined.
Incidents travel further than announcements because they transform an abstract risk into a personal one. A feature asks users to imagine value. A privacy failure asks them to imagine themselves as the victim.
Claude Sonnet 5
Sonnet 5, released June 30, received 1,266 Hacker News points, 784 comments, and 2,760 Reddit upvotes. Its one-million-token context window mattered to practitioners building context-heavy systems.
It also received the period’s most brutal one-line headline—“Sonnet 5 Is Dead in the Water”—which seems to reflect, at least in part, the extraordinary saturation created by the Fable 5 political drama surrounding its launch.
Exception one: MCP’s stateless transport
The July 28 MCP revision attracted only 118 Hacker News points and 37 comments. By raw volume it was niche, but the responses came from practitioners who had already encountered the problem and were unusually consistent:
“I’d made the shift to HTTP/Stateless from MCP a few months ago. It’s the right thing to do IMHO. Reliability up, problems down.”
“URL Elicitation works well if a human is driving the client. Unfortunately MCP client support is patchy but I expect that will change now the protocol is stateless.”
This is the first exception to the general pattern. A conventional feature generated modest attention but high-quality discussion because it solved an identifiable infrastructure problem.
There was a meaningful countercurrent. Some developers argued that the protocol remained unnecessary:
“You can get better results with skills SKILL.md + linked .md files with curl commands inside… Just plain HTTP(S).”
Low volume does not necessarily mean low importance. In infrastructure, a few dozen comments from people who have already migrated can be more informative than thousands of launch-day reactions.
Exception two: Claude Skills spread by themselves
On Hacker News, “Claude skill” was nearly a rounding error: 34 comments. On Reddit, however, Skills produced one of the strongest organic signals in the dataset—and the energy came from users rather than Anthropic:
- “I made a Claude Code skill that turns a photo of your handwriting into an installable font”—3,437 upvotes
- “New: Teach Claude a skill”—2,712 upvotes
- “Whoever created the ADHD skill god bless you”—2,621 upvotes and 405 comments
The last example is the tell. It is not applause for a launch. It is one user thanking another for something that changed their day.
The smaller Hacker News discussion also described genuine diffusion into nontechnical teams:
“That’s how I see most of my less technical coworkers reason about using AI. ‘Is there a Claude skill for that?’ is a question I hear multiple times a week.”
“I thought about MCP, but found that having it as a Claude skill is much simpler (since it can be installed as a plugin, and only depends on md files and also doesn’t need to run a server all the time).”
Skills spread because they are user-authored, legible, and shareable. Most features in this dataset are things a company does for—or to—its users. Skills are things users do for one another. That gives the discussion a different character: organic rather than reactive.
There is a counter-signal worth respecting. Some power users reported Skills degrading performance on newer models: “saw my skills start causing degradation”; “removing skills like ‘superpowers’ reduces token consumption.”
Skills have a bloat problem. But bloat is often the problem successful platforms acquire after people begin building on them.
Tier 0: Shipped into near-silence
The following products were staffed, built, and announced during the same period. Within the sources and searches used for this analysis, their visible public reaction was minimal:
| Feature | Shipped | Discussion found |
|---|---|---|
| ChatGPT Voice in Chat, Work, and Codex | Jul 23 | No dedicated discussion distinguishable from unrelated voice threads |
| New ChatGPT desktop app, unifying Chat, Work, and Codex | Jul 16 | 2 points, 1 comment |
| Health in ChatGPT, including Apple Health and medical records | Jul 23 | 32 points / 54 comments, plus 8 / 7 |
| OpenAI Presence, enterprise voice-and-chat agents | Jul 22 | 64 points, 51 comments in one thread |
| Rebuilt ChatGPT memory | Jun 4 | No dedicated thread above background noise |
| Codex Remote general availability | May/Jun | 2 stories, 3 points total |
| ChatGPT personal finance / Plaid | May 15 | 7 points, 1 comment |
| Retiring group chats | Jul 9 | 2 points, 0 comments |
| GPT-5.2 / GPT-4.5 deprecation | Jun 12 / 26 | 9 points total |
| Claude voice-mode expansion | Jul 23 | No signal distinguishable from background noise |
The silence does not establish that these products went unused. It does show that they failed to become stories within the communities examined.
Voice is expensive silence
Both companies shipped substantial voice work within a day of each other in late July. Neither generated meaningful discussion in this dataset.
Voice demos beautifully. Among people who publicly discuss software, however, it has yet to produce a comparable culture of use, argument, or user-created artifacts. That gap—between demo appeal and visible practitioner enthusiasm—is worth investigating with actual usage data.
Health deserved attention and received suspicion
Connecting medical records to a general-purpose chatbot may be the most consequential product OpenAI shipped all quarter. The leading thread drew 32 points.
The little discussion that did appear was skeptical. Adjacent headlines framed the product as “ChatGPT wants access to your health records so it can be a better not-doctor,” alongside coverage of a lawsuit.
For a launch this sensitive, silence combined with distrust is not neutral. It suggests that the company has not yet established the legitimacy required for users to evaluate the value proposition on its own terms.
The memory rewrite arrived after users had formed their verdict
The memory redesign appears to represent substantial engineering: time-aware resynthesis, costs reportedly reduced by roughly five times, and broader availability for free users.
Yet users mostly discussed memory to complain about it:
“This thing is better disabled because it’s intrusive.”
“I found Opus’s 4.8 memories largely lacking value. I disabled memory for the web UI.”
Improving a system after users have disabled it creates a distribution problem. The company is no longer merely shipping a better feature; it must persuade users to revisit a decision they believe they have already settled.
Codex Remote may have a naming problem
Starting a coding task from a phone is plainly useful, and people were independently building similar products. Hacker News featured projects titled “Zedra—Mobile control plane for AI coding agents” and “ShellTeam.”
Yet Codex Remote itself produced only three points of visible discussion.
The market appeared to recognize the job while overlooking OpenAI’s implementation of it. That can happen when a product name describes internal architecture rather than the moment of user value. “Remote” says where the task runs. It does not say: start work from your phone, let it continue elsewhere, and return to a finished result.
What the conversation was really about
The public AI conversation of the last three months followed a surprisingly consistent hierarchy:
- Capability earns attention. Frontier models still create the largest launch moments, especially when they demonstrate results that feel real rather than benchmark-shaped.
- Control turns attention into argument. Export restrictions, procurement decisions, safety refusals, privacy incidents, and changing access terms dominate once users begin depending on a system.
- Price and reliability determine habit. A brilliant model that is unavailable, error-prone, or exhausted after a few sessions cannot become infrastructure.
- User-created artifacts generate affection. Skills stood apart because users could make them, exchange them, and thank one another for them.
- Quiet features remain genuinely hard to judge from public discussion. Silence may mean indifference, poor positioning, invisible success, or simply that a product does not produce stories.
That last point is the limit of this analysis, but it is also a useful product question. If a feature is valuable yet nobody talks about it, a company should know whether it has built quiet infrastructure or merely shipped into a void.
The biggest AI stories of this period were not really about feature velocity. They were about dependency.
Users are beginning to treat these systems as tools they build work and identity around. Once that happens, the decisive questions change. What can it do? remains important, but it is joined by harder ones:
Can I afford it? Can I trust it? Will it still be available tomorrow? And can I make it mine?
Those were the questions people cared enough to argue about.
Top comments (0)