AI Intel

AI Intel: #QuitGPT Crosses 4M, Claude Code Leak Triggers Enterprise Security Panic, The Great Migration Accelerates

The #QuitGPT boycott just crossed 4 million supporters, up from 2.5 million barely three weeks ago. What started as a Reddit protest over OpenAI's Pentagon ties has turned into the largest consumer revolt in AI history. And it's reshaping the entire market in real time.

#QuitGPT Hits 4 Million: From Hashtag to Movement

The numbers tell the story. Four million people have now publicly committed to canceling or boycotting ChatGPT, according to tracking across Reddit, X, and the movement's own site. That's a 60% jump since mid-March.

The trigger, if you've been living under a rock: OpenAI president Greg Brockman and his wife donated $25 million to a Trump Super PAC in 2025. When that became widely known in February 2026, Reddit's r/technology and r/ChatGPT lit up. The hashtag spread to X, then to mainstream media. Guides on "how to cancel ChatGPT" started ranking on Google. AtomicMail published a full migration walkthrough three days ago that's already one of the top results.

What makes this different from typical tech boycotts: people are actually leaving. ChatGPT uninstalls spiked 295% in March. Claude is now #1 in five country app stores. NxCode reported this week that 2.5 million users are actively boycotting, with the broader supporter count pushing past 4 million when you include people who've switched without formally joining the movement.

For developers, the practical impact is clear. If you're building products on OpenAI's API, some of your users care about this. Not all of them, but enough to matter. Having a multi-model fallback isn't just a reliability play anymore. It's a brand risk play.

Claude Code Leak: The Enterprise Security Fallout

Three days after Anthropic accidentally shipped a 59.8 MB source map file inside Claude Code v2.1.88 on npm, the security implications are still unfolding. VentureBeat published an enterprise security advisory just hours ago outlining five actions security leaders should take immediately.

Quick recap: on March 31, an intern at Solayer Labs spotted the source map, posted a download link on X, and within hours the full 512,000-line TypeScript codebase across 1,906 files was mirrored on GitHub and picked apart by thousands of developers. Anthropic confirmed it was "a release packaging issue caused by human error, not a security breach." No customer data was exposed.

But the damage goes beyond the code itself. The leak revealed unreleased features including a Tamagotchi-style "pet" system, an always-on daemon mode called KAIROS, references to unreleased Capybara models, and anti-distillation defenses. For competitors like Cursor, this is a literal blueprint for building a high-agency AI coding agent.

The enterprise angle is what matters this week. Claude Code has hit $2.5 billion ARR, with 80% of that from enterprise customers. Those customers are now asking hard questions about Anthropic's release pipeline security. If your npm package can accidentally ship full source maps, what else might slip through? VentureBeat's advisory recommends auditing all Anthropic package versions, reviewing supply chain controls, and checking whether any internal tooling ingested the leaked code.

For developers using Claude Code through API gateways like KissAPI, the leak doesn't change your security posture directly since the API layer is separate from the npm package. But if you're running Claude Code locally in enterprise environments, it's worth reviewing what version you're on and whether your security team has flagged it.

OpenAI's Enterprise Credibility Problem

Reddit's AI communities spent the week questioning whether OpenAI can hold its enterprise market. The conversation has shifted from "ChatGPT is getting worse" to "should we trust OpenAI with our business?"

The concerns stack up. The Pentagon deal alienated a chunk of the consumer base. GPT-5.4's pricing drew mixed reviews, with the 1M context window costing significantly more past 272K tokens. Quality complaints about ChatGPT have been a drumbeat since late 2025. And now the QuitGPT movement is creating reputational risk for companies that build on OpenAI's stack.

Enterprise buyers think in terms of vendor risk. When your AI provider is generating weekly negative press cycles, that's a line item on the risk register. It doesn't mean everyone's leaving OpenAI tomorrow. But it means procurement teams are asking for multi-vendor strategies, and "Claude as primary, GPT as fallback" is becoming a common architecture.

The irony: OpenAI's models are still good. GPT-5.4 is genuinely capable. But capability alone doesn't win enterprise deals when trust is eroding. Anthropic's own leak this week shows nobody's immune to mistakes, but the difference is Anthropic's mistake was technical. OpenAI's problems are political.

The Great Migration: ChatGPT to Claude, By the Numbers

The ChatGPT-to-Claude migration wave that started in February is accelerating, not plateauing. Reddit threads this week are full of users sharing their switch stories, and the pattern is consistent: people try Claude, find it better for their use case, and don't go back.

Some numbers from the past month:

The migration isn't just consumers. Developer communities on Reddit report switching their coding workflows from Copilot and ChatGPT to Claude Code and Cursor (which defaults to Claude). The coding agent market crossed $6.5 billion, and Claude is eating the largest share.

For anyone running API-dependent applications, this migration creates both opportunity and infrastructure pressure. More users on Claude means more demand on Anthropic's servers, which means more rate limits and quota issues. We covered the Claude Code quota crisis yesterday. If you're building on Claude's API, having a gateway that can route to multiple providers when Claude is overloaded isn't optional anymore. It's table stakes.

Don't Get Locked Into One Provider

KissAPI gives you Claude, GPT-5, Gemini, and 200+ models through one OpenAI-compatible endpoint. Switch models per-request. No vendor lock-in.

Get Started Free →

Quick Hits

That's your Thursday briefing. The AI market is splitting along political lines in a way nobody predicted a year ago, and the technical landscape is shifting just as fast. Build for flexibility.