AI Intel: Qwen 3.6-Plus Crashes the Party, OpenAI's $122B War Chest, Codex Goes Pay-Per-Token

Alibaba just dropped Qwen 3.6-Plus, and the benchmarks are hard to ignore. A 1-million-token context window, agentic coding scores that put it in Claude Opus territory, and Apache 2.0 licensing on the open-source variants. Meanwhile, OpenAI closed the largest funding round in tech history and quietly rewired how Codex charges for work. Here's what matters this Friday.

Qwen 3.6-Plus: Alibaba's Coding Model Catches Up Fast

Alibaba released Qwen 3.6-Plus on April 2nd, and it's the third proprietary model they've shipped this week alone. The headline numbers: a default 1M context window, agentic coding benchmarks that rival Claude 4.5 Opus, and strong performance on task breakdown, code generation from screenshots, and debugging workflows.

This matters for a few reasons. First, the Qwen family now covers an absurd range — 0.8B to 397B parameters — all under Apache 2.0 for the open-weight versions. That means you can run smaller Qwen models locally for free while routing harder tasks to the proprietary 3.6-Plus via API. Second, Qwen 3.5/3.6 leads or ties on 5 of 8 major benchmark categories, including LiveCodeBench and SWE-bench. These aren't vanity metrics; they're the benchmarks that actually predict real-world coding performance.

The timing is interesting too. Several key Qwen executives resigned earlier this year, including Lin Junyang who led development on Qwen3-Max and Qwen3.5. There was real concern that Alibaba might pull back from open source. Instead, they doubled down. The company publicly committed to continuing its open-source focus, and 3.6-Plus is the proof.

For developers already using Qwen through API gateways, the upgrade path is straightforward — just swap the model name. If you're exploring alternatives to Claude or GPT for coding tasks, Qwen 3.6-Plus deserves a serious look, especially at its price point.

OpenAI Raises $122 Billion, Codex Switches to Token Pricing

OpenAI closed a $122 billion funding round this week, the largest in tech history. Revenue has crossed $2 billion per month. Enterprise now makes up over 40% of that, on track to reach parity with consumer by year-end. Their APIs process more than 15 billion tokens per minute. Codex alone serves over 2 million weekly users.

Those are staggering numbers. But the more interesting move happened quietly: as of April 2nd, Codex pricing shifted from subscription tiers to API token-based rates. You can still use Codex through ChatGPT Plus or Pro subscriptions, but the new API Key tier lets you pay only for the tokens Codex actually consumes. No subscription required.

The new Codex lineup includes GPT-5.4, GPT-5.3-Codex, and a research preview called GPT-5.3-Codex-Spark for Pro users. Free tier users get basic access. Plus users get "a few focused coding sessions each week." Pro users get 6x higher limits and priority processing. The API Key path skips cloud features like GitHub code review and Slack integration but gives you raw token access at standard API rates.

This is OpenAI acknowledging what the market already figured out: developers don't want to guess whether their $20/month subscription covers their workload. They want to see exactly what they're spending. The shift to token pricing also makes it easier to compare Codex costs against Claude Code, Cursor, and other coding agents on an apples-to-apples basis. For teams running Codex through an OpenAI-compatible gateway like KissAPI, the API Key tier means you can route Codex requests alongside Claude and Gemini calls through a single endpoint.

Claude Code Leak: The Fallout Isn't Over

The Claude Code source leak from earlier this week continues to ripple through the developer community. For those catching up: Anthropic accidentally shipped full source maps in the Claude Code npm package, exposing 512,000 lines of TypeScript. The leak revealed internal codenames (Capybara models, KAIROS daemon mode), anti-distillation defenses, and the full architecture of how Claude Code orchestrates tasks.

Reddit's been picking this apart all week. The enterprise security angle is the one that stings most — companies running Claude Code in their CI/CD pipelines are now auditing what data those source maps might have exposed. Anthropic pulled the source maps quickly, but the code is archived everywhere at this point.

The developer reaction has been split. Some are impressed by the engineering (512K lines of well-structured TypeScript is no joke). Others are using the leaked architecture as a blueprint for building their own coding agents. A few enterprise security teams are using it as ammunition to push for self-hosted alternatives.

The practical takeaway: if you're building on Claude Code in production, audit your npm lockfiles and make sure you're not pulling in anything unexpected. And if you're evaluating coding agents, the leak actually gives you an unusually detailed look at how Anthropic's agent architecture works — which is useful context regardless of which tool you end up choosing.

#QuitGPT Holds at 4M, But the Energy Is Shifting

The #QuitGPT boycott crossed 4 million supporters this week, but the conversation on Reddit is evolving. Early posts were pure outrage about OpenAI's Pentagon deal. Now the threads are more practical: people sharing their migration setups, comparing Claude vs Gemini for different workflows, and debating whether boycotting actually changes anything when enterprise contracts dwarf consumer revenue.

The migration wave is real though. Claude's daily active users have been climbing steadily since the boycott started, and the ChatGPT-to-Claude pipeline is well-documented at this point. Reddit's r/ClaudeAI is full of "I switched and here's what I learned" posts. The consensus: Claude is better for coding and long-form writing, ChatGPT still wins on multimodal tasks and plugins, and most power users end up keeping accounts on both.

For API users, the boycott is mostly noise. You're paying per token regardless of which company's CEO you disagree with. But the broader trend — users wanting flexibility to switch between providers without rewriting code — plays directly into the multi-model gateway approach. One API key, multiple models, no vendor lock-in.

Quick Hits

• Meta teasing a new model. No official announcement yet, but multiple sources point to a Llama 4 follow-up dropping soon. After Llama 4 Scout and Maverick's mixed reception, Meta needs a win here.
• AI agent ecosystem keeps expanding. The coding agent market crossed $6.5B earlier this year and shows no signs of slowing. New entrants are popping up weekly, most built on top of Claude or GPT APIs. The real bottleneck isn't the models — it's reliable tool use and context management.
• Claude Pro users still unhappy about limits. Despite Anthropic's recent tier adjustments, Reddit threads about hitting Claude Pro rate limits during peak hours continue. Power users burning through their allocation by noon isn't a great look when you're charging $20/month.