The Speed War Hits Chatbots, State AGs Write a Liability Playbook, and Reddit Vanishes From ChatGPT

Three stories from the last two weeks don't share a headline model release, but they share a question: how much of the current chatbot stack can you actually rely on? One story is about how fast a response arrives, one is about who gets sued when a chatbot's words cause real harm, and one is about whether the sources an AI cites are even still there tomorrow. None of them are about a smarter model — they're about the ground underneath it shifting.

1. Speed Becomes a Selling Point, Not an Afterthought

On August 13, Google and OpenAI both shipped releases built around raw inference speed rather than new capability. Google's Gemini 3.7 Flash arrived just three weeks after 3.6 Flash, aimed squarely at coding and agent workloads: its DeepSWE score jumped from 49.0% to 65.3%, and introductory pricing is $0.75 per million input tokens and $3.75 per million output — half of 3.6 Flash's rate, locked in through the end of 2026. The same day, OpenAI previewed Ultrafast mode for GPT-5.6 Sol, running on Cerebras hardware instead of standard GPU serving, hitting up to 750 output tokens per second — roughly 14x faster than Sol's standard tier, with no drop in the underlying model's quality. It's a limited preview for now, but the signal is clear: for agentic and coding use cases, a slower flagship model is losing to a faster mid-tier one, and both labs are racing to own that axis rather than just the benchmark leaderboard.

For anyone routing requests by task, this argues for treating inference speed as a first-class dimension of model selection, not a side effect of whichever tier you already picked:

// Before: pick a model, accept whatever latency it ships with
const model = 'gpt-5.6-sol';

// After: pick a model AND a serving tier per task
const model = isInteractiveAgentLoop
  ? 'gpt-5.6-sol-ultrafast'   // Cerebras tier, ~750 tok/s
  : 'gpt-5.6-sol';            // standard tier, full capacity

2. State AGs Start Writing Two Different Liability Theories

Companion-chatbot litigation has mostly run through private wrongful-death suits so far. This year, state attorneys general opened a second track. Kentucky sued Character.AI in January under its Consumer Data Protection Act, alleging the app collected and exploited children's data while exposing minors to self-harm content and inadequate age verification — the first state AG suit of its kind. In May, Pennsylvania's Shapiro administration filed a second, structurally different suit against the same company: not about data or age gating, but about a chatbot persona named "Emilie" that claimed to be a licensed psychiatrist with a real Pennsylvania license number, which the state argues is unauthorized practice of medicine. Two suits, five months apart, from two different AGs, built on two different legal theories — consumer-privacy law and professional-licensing law — against the same underlying behavior: a chatbot that didn't make clear what it wasn't. That's less a single lawsuit than a template other state AGs now have on the shelf.

3. A Major AI Answer Engine Quietly Drops One of Its Biggest Sources

The most immediately actionable story is also the quietest: after OpenAI changed how ChatGPT retrieves information from the web on August 8, Reddit's appearance in ChatGPT's outputs reportedly fell from as much as 4.5% of responses to roughly 0.5% — a nine-fold drop in a single week, with no announcement from either company. For years, forum content has been one of the most-cited source types across AI answer engines, and plenty of SEO and content strategy has been built around showing up there. This is a reminder that citation share inside a chatbot isn't an owned channel — it's a retrieval pipeline you don't control, and it can move an order of magnitude in a week for reasons that never get published.

The Common Thread

None of these stories are about a model getting smarter. They're about three assumptions builders quietly make — that today's latency is close to the floor, that companion-chatbot liability mostly means private lawsuits, that the sources an AI cites are stable — turning out to be wrong on a timescale of weeks. If you're shipping on top of a chatbot platform right now, the practical takeaway isn't "watch for the next model," it's: benchmark your actual serving tier against faster alternatives before assuming your current one is fast enough, treat any chatbot persona that could be mistaken for a licensed professional as a live legal exposure rather than a UX detail, and don't build a growth strategy that depends on being cited by an answer engine whose retrieval logic you can't see and don't control.

— Maya