I woke up on April 2, 2026, refreshed my Twitter feed, and the first thing I saw was the @cursor_ai announcement: Cursor 3 is live. After months of watching the AI coding tool race intensify, Anysphere just shipped the biggest update in the company's history.

This isn't an incremental update. Cursor 3 introduces the Agents Window — a completely new interface, built from scratch, designed around one idea: you manage agents, agents write the code. Run them locally, in worktrees, over SSH, or hand them off to the cloud so they keep working while your laptop is shut.

Meanwhile, Google's Antigravity has been sitting at 76.2% on SWE-bench Verified since November 2025, offering a free agent-first IDE powered by Gemini 3 Pro. And Claude Code is quietly eating market share from the terminal with Anthropic's Opus 4.6 underneath.

Three very different tools. Three different philosophies. One question: which one should you actually be using right now? I've gone deep on all three, and I have a real opinion.

What Is Cursor 3? The Agents Window Explained

Cursor 3 is the most significant release Anysphere has shipped since the company forked VS Code in 2023. Announced on April 2, 2026, it adds the Agents Window — a standalone interface that lets developers run multiple AI agents in parallel across local machines, worktrees, SSH environments, and cloud setups, all without interrupting the main coding session.

The core product philosophy has shifted. Previously, Cursor was an AI-enhanced editor. Now, the goal is explicit: you are the architect, agents are the builders. The IDE is still there. You can switch back to it anytime. But the default experience in Cursor 3 is managing a fleet.

To access the Agents Window right now: upgrade Cursor, then type Cmd+Shift+P -> Agents Window. You can run it side-by-side with the IDE or as a standalone view.

What I find genuinely interesting about Cursor 3 is the cloud handoff feature. Start a task locally, then push it to a cloud agent so it keeps running after you close your laptop. Longer-running overnight jobs, no interruptions. That's not a gimmick. That solves a real daily annoyance.

Cursor crossed $2 billion in annual revenue as of early 2026, doubling in three months, with roughly 25% market share among generative AI software buyers. By mid-2025, over 50% of Fortune 500 companies had adopted Cursor. Nvidia, Uber, and Adobe are on that list. Those numbers give Anysphere the budget to build things like the cloud agent infrastructure that powers Cursor 3.

What Is Google Antigravity? Gemini 3 in an IDE

Google Antigravity is a free agent-first IDE released in November 2025 alongside Gemini 3, powered by Gemini 3.1 Pro and Claude Opus 4.6. It scored 76.2% on SWE-bench Verified and 54.2% on Terminal-Bench 2.0, two benchmarks that measure real coding agent performance.

The origin story is worth knowing: Google acquired the Windsurf team, including CEO Varun Mohan, for $2.4 billion in July 2024. That team delivered Antigravity in under six months. It is not a VS Code fork — Antigravity is built from the ground up as a native agent-first environment.

Antigravity has two primary views. Editor View is essentially VS Code-familiar — syntax highlighting, an agent sidebar, inline completions powered by Gemini 3 Flash. Manager View is where Antigravity gets interesting: a mission control dashboard for dispatching up to five parallel agents simultaneously, monitoring their progress in real-time, and reviewing their work as Artifacts — task plans, screenshots, browser recordings — before accepting any changes.

The Artifacts system is Antigravity's standout idea. Every agent action generates a verifiable record. Developers don't need to review every line of code; they review whether the agent's plan and test results match what they asked for. That's a different kind of trust model than Cursor's, and honestly, it's the smarter one for enterprise compliance.

The honest downside: Antigravity is still early-stage. Early 2026 saw real stability problems — context memory errors, version compatibility bugs, agents terminating mid-task. MCP support doesn't exist yet. The ambition is there; the reliability isn't fully there yet.

Cursor 3 vs Antigravity vs Claude Code: Full Comparison Table

Here's the side-by-side across every dimension that actually matters for developer decisions:

My take on this table: the MCP support gap is Antigravity's biggest weakness right now. Cursor's marketplace has hundreds of plugins. Antigravity has none. For teams already running MCP workflows — Figma, Amplitude, tldraw in chat — switching to Antigravity means giving all of that up.

Cursor 3 Key Features Breakdown

Agents Window

The Agents Window is a new interface built from scratch — not a panel bolted onto the IDE. It supports multi-workspace layouts, letting you and your agents work across different repos from one place. Agent Tabs allow side-by-side or grid views of multiple chats. Native worktree support has moved here from the Editor, with better UX for managing multiple workspaces.

Design Mode

Design Mode lets users click and drag to annotate UI elements directly in an embedded browser, then point the agent at exactly the component they want changed. This is faster than describing UI elements in text — a 5-minute explanation becomes a 10-second click. For frontend developers iterating on designs, this alone is worth the upgrade.

Composer 2 and Real-Time RL

Composer 2 is Cursor's proprietary coding model, trained with real-time reinforcement learning on actual user interactions. The results from Cursor's internal A/B testing: agent edit persistence in codebases improved by +2.28%, dissatisfied follow-up messages dropped by -3.13%, and latency dropped -10.3%. Typical tasks complete in under 30 seconds. On Terminal-Bench 2.0, Cursor uses the official Harbor evaluation framework and reports results across five iterations per model-agent pair.

Cloud Agents and Automations

Cursor Automations, which launched before Cursor 3, lets developers trigger agents based on events like code commits, Slack messages, or scheduled timers. Security agents are currently reviewing more than 3,000 internal PRs per week, catching over 200 vulnerabilities weekly. Cursor 3 extends this further with cloud handoff — push a local session to the cloud mid-task and it keeps running.

New Commands

Two new commands worth knowing: /worktree for isolated task execution in separate git worktrees, and /best-of-n for running the same task across multiple models and comparing results. The second one is underrated — it effectively lets you A/B test model output without leaving the IDE.

Google Antigravity Key Features Breakdown

Manager View and Artifact System

Manager View is Antigravity's most genuinely novel contribution to the AI IDE space. Dispatch five agents on five independent tasks simultaneously, monitor real-time status, and receive diffs, test results, and screenshots as Artifacts before accepting any changes. For debugging and compliance use cases, this transparency is invaluable.

Planning Mode vs Fast Mode

Antigravity gives agents two operating modes. Planning Mode externalizes the agent's reasoning — it generates a task list and walkthrough as an Artifact before writing a single line. Fast Mode skips the planning phase and executes directly. For production code, Planning Mode is the right default. Fast Mode is for throwaway prototypes and boilerplate.

Gemini 3.1 Pro and Multi-Model Support

Antigravity centers on Gemini 3.1 Pro but also supports Claude Sonnet 4.6, Claude Opus 4.6, and GPT-OSS-120B. More interestingly, you can assign different models to different agents — Gemini 3.1 Pro for architecture planning, Claude Sonnet 4.6 for implementation, Gemini 3 Flash for unit test generation. Cursor lets you switch models, but per-agent model assignment at this level is more flexible in Antigravity.

2 Million Token Context Window

Antigravity's Gemini 3 Pro context window processes up to 2 million tokens — your entire codebase, in context, at once. Ask questions like 'Where is the authentication middleware defined?' and get accurate answers from the full codebase. Cursor works with project-wide embeddings and is strong here, but raw context window size is Antigravity's structural advantage.

Chrome Extension and Browser Automation

A Chrome extension allows agents to interact directly with the browser — recording actions, validating UI flows, running tests against local websites. Cursor 3 also has built-in browser interaction, but Antigravity's implementation supports browser recording as an Artifact, giving you a replayable record of what the agent did.

Pricing: Cursor Pro vs Antigravity Free vs Claude Code API

This is where the conversation gets real. Antigravity being completely free with Gemini 3.1 Pro and Claude Opus 4.6 included is a meaningful market pressure on Cursor and Anthropic.

My honest opinion: $20/month for Cursor Pro is fair value if you're using it daily on production code. The Composer 2 quality and MCP ecosystem justify it. But if you're a solo developer or student who just wants to build things, Antigravity's free tier with Opus 4.6 access is a remarkable deal that I don't think the market has fully priced in yet.

The Cursor Ultra plan at $200/month is aimed at power users who need guaranteed compute. 20x model usage and priority access make sense for teams with predictable high-volume workflows. Most individual developers don't need this tier.

Benchmarks: SWE-bench, Terminal-Bench 2.0, and Real-World Tests

Google Antigravity scores 76.2% on SWE-bench Verified, one of the highest published scores for a coding agent as of April 2026. For context: Devin, which launched in 2024 as the first 'autonomous software engineer,' scored 13.86% at launch. The gap between what was considered impressive then and what's standard now is staggering.

Antigravity also scored 54.2% on Terminal-Bench 2.0, an agent evaluation benchmark for terminal use maintained by the Laude Institute. Cursor's score on Terminal-Bench 2.0, computed using the official Harbor evaluation framework with five iterations per model-agent pair, is reported in the March 2026 release notes as top-3 alongside Antigravity and Kiro IDE.

Claude Code, using Claude Opus 4.6, scores approximately 72% on SWE-bench Verified — slightly below Antigravity's 76.2%, but within the margin of variation across evaluation runs. The practical difference in day-to-day coding tasks between 72% and 76.2% is likely small for most use cases.

Antigravity scored 1487 Elo on the WebDev Arena leaderboard, demonstrating strong performance specifically for web development tasks.

One number I'd push back on: SWE-bench Verified measures specific, reproducible GitHub issues. It is a useful proxy but not a perfect measure of how productive a tool makes you in your actual codebase. Cursor's Composer 2 improvements in A/B testing on real user interactions — the +2.28% edit persistence, -3.13% dissatisfied follow-ups — are arguably more predictive of real developer experience than benchmark scores.

Which AI Coding IDE Should You Use in 2026?

The honest answer is that the right choice depends on what you're actually building and how you work. But I'll give you my real opinion instead of the safe 'it depends' non-answer.

Use Cursor 3 if: you work on production codebases, your team has existing .cursorrules and workflows, you need MCP integrations, or you want the most mature day-to-day coding experience. The Composer 2 quality, Design Mode, and cloud agent infrastructure make this the professional developer's default in 2026. The $20/month Pro price is justified for anyone using it seriously.

Use Google Antigravity if: you're experimenting with agent-first workflows, building in the Google ecosystem (Firebase, Google Cloud, Gemini API), want a free Opus 4.6 coding environment, or need the Artifacts transparency system for compliance or debugging. The Manager View is genuinely novel. The 2M token context window is a structural advantage. Just be patient with the stability issues.

Use Claude Code if: you're terminal-native, want the deepest MCP integration, need editor-agnostic agents that work across your whole setup, or are already on Anthropic's API for other purposes. Claude Code is also the best option for complex multi-step refactoring tasks where you want to track every change.

My personal setup: I'm running Cursor 3 for daily coding and switching to Antigravity's Manager View for larger refactoring sessions or new feature builds that I can define cleanly as independent tasks. At $20/month plus free Antigravity, it's the highest-ROI combination I've found.

The contrarian take worth saying out loud: most developers are still running a single-agent workflow when multi-agent parallel execution is already available. The productivity ceiling hasn't been hit yet. Cursor 3 and Antigravity both push that ceiling significantly higher — but only if you actually restructure how you work, not just how you open your IDE.

Want to build AI agents and apps using tools like Cursor 3, Antigravity, and Claude Code?
Join Build Fast with AI's Gen AI Launchpad — an 8-week program to go from 0 to 1 in Generative AI.
Register here:

Frequently Asked Questions

What is Cursor 3?

Cursor 3 is the latest major release from Anysphere, launched on April 2, 2026. It introduces the Agents Window — a new standalone interface for running multiple AI agents in parallel across local, SSH, worktree, and cloud environments. Features include Design Mode for UI editing, Composer 2 for fast code iteration, cloud handoff for overnight tasks, and new /worktree and /best-of-n commands.

How do I access the Agents Window in Cursor 3?

Upgrade to the latest version of Cursor, then press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux) and type 'Agents Window.' You can run the Agents Window alongside the IDE simultaneously or as a standalone view. To revert to the classic IDE interface at any time, switch back through the same shortcut.

Is Google Antigravity better than Cursor for coding?

Google Antigravity scores 76.2% on SWE-bench Verified compared to Cursor's top-3 placement on Terminal-Bench 2.0. Antigravity has advantages in raw context window size (2M tokens), pricing (free), and parallel agent transparency (Artifacts system). Cursor has advantages in MCP ecosystem maturity, day-to-day polish, VS Code extension compatibility, and the Composer 2 model's production reliability. Neither is universally better — the right choice depends on your workflow.

What is Design Mode in Cursor 3?

Design Mode is a Cursor 3 feature in the Agents Window that lets developers click and drag directly on browser-rendered UI elements to annotate and target them for the AI agent. Instead of describing a UI component in text, you point to it visually. This enables more precise feedback and faster iteration cycles, particularly for frontend developers working on component-level changes.

How much does Cursor 3 cost?

Cursor 3 has three pricing tiers: Free (limited model usage), Pro at $20/month (unlimited Composer 2, priority access), and Ultra at $200/month (20x model usage, enterprise features and guaranteed compute). Google Antigravity is currently free in public preview with Gemini 3.1 Pro and Claude Opus 4.6 included at no cost. Claude Code pricing is based on Anthropic API usage, which runs approximately $100/month or more for heavy professional use.

Does Google Antigravity support MCP servers?

As of April 2026, Google Antigravity does not support MCP (Model Context Protocol) servers. This is a significant limitation for teams that rely on MCP integrations for tools like Figma, Amplitude, or custom enterprise plugins. Cursor has a mature MCP marketplace with hundreds of plugins. If MCP support is a requirement, Cursor or Claude Code are the better choices for now.

What is the SWE-bench score for Cursor vs Antigravity?

Google Antigravity scores 76.2% on SWE-bench Verified as of its public preview release. Claude Code with Opus 4.6 scores approximately 72% on the same benchmark. Cursor does not publish a single SWE-bench number for the full product but scores in the top-3 on Terminal-Bench 2.0 using the Harbor framework with five-iteration averages. Devin, for context, scored 13.86% at its 2024 launch.

Can I use both Cursor 3 and Google Antigravity together?

Yes, and many developers in 2026 are doing exactly this. A common setup: Cursor 3 for daily coding assistance, tab completion, and MCP-connected tools; Antigravity Manager View for larger autonomous refactoring sessions or new features with well-defined independent tasks. Since both have free or low-cost tiers, there's no cost barrier to running both.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1. Claude Code vs Codex: Which Terminal AI Tool Wins in 2026?

2. Cursor Composer 2: Benchmarks, Pricing & Review (2026)

3. Best AI for Coding 2026: Nemotron vs GPT-5.3 vs Opus 4.6

4. 7 AI Tools That Changed Developer Workflow (March 2026)

5. Claude Code Auto Mode: Unlock Safer, Faster AI Coding (2026 Guide)

References

12.  Meet the New Cursor (Cursor 3 Official Announcement) — Cursor Blog

13.  Cursor 3 Changelog — Cursor Official Changelog

14.  Cursor 3: Agents Window Discussion — Cursor Community Forum

15.  Google Antigravity vs Cursor: AI-Powered Coding IDEs Differences — Metana

16.  Google Antigravity: Agentic IDE Powered by Gemini 3 vs. Cursor & Claude Code — Vertu

17.  Antigravity vs Cursor 2026: Which AI Coding IDE Should You Choose? — Antigravity Lab

18.  Google Antigravity Review: Free Agent-First IDE With Claude Opus Built In — OpenAIToolsHub

19.  Cursor Releases Automations Platform for AI Coding Agent Management — MLQ.ai

20.  Cursor Release Notes March 2026 — Releasebot

I woke up on April 2, 2026, opened my feed, and Google had quietly dropped the biggest open-model release of the year. Four models. Apache 2.0 license. Built on the same research as Gemini 3. Runs on your phone, your laptop, a Raspberry Pi, or a single NVIDIA H100. I have been waiting for Google to go fully open for years, and Gemma 4 is that moment.

Google DeepMind's Gemma 4 launched on April 2, 2026, as a family of four open-weight AI models designed to run on everything from Android smartphones to developer workstations. The 31B Dense model currently ranks #3 on the Arena AI text leaderboard, beating models 20x its size. And every variant ships under a fully permissive Apache 2.0 license for the first time in the Gemma family's history.

This is not a small release. It is a statement.

What Is Google Gemma 4?

Google Gemma 4 is Google DeepMind's latest family of open-weight AI models, released on April 2, 2026, under the Apache 2.0 license. Built from the same research and architecture that powers Gemini 3, the commercial flagship, Gemma 4 brings that frontier-level intelligence to the open-source community.

The name "Gemma" (from the Latin for gem) has been Google's open-model brand since 2024. The first Gemma models launched in 2B and 7B sizes. Since then, the series has crossed 400 million total downloads and spawned over 100,000 community variants. Gemma 4 is the fourth generation, and by every measurable metric, it is the biggest leap yet.

What separates Gemma 4 from every previous Gemma release comes down to three things: intelligence-per-parameter efficiency that beats models 20x its size, native multimodal capabilities baked into the architecture from day one (not bolted on after), and a truly permissive license that enterprise legal teams will actually accept.

Google DeepMind CEO Demis Hassabis called them "the best open models in the world for their respective sizes." That is a bold claim. The benchmarks, which I will walk through below, mostly back it up.

Gemma 4 Model Sizes and Variants Explained

Gemma 4 ships in four sizes: E2B, E4B, 26B MoE, and 31B Dense. These are split into two deployment tiers: edge models for phones and embedded devices, and workstation models for GPUs and servers.

The naming convention here trips people up. The 'E' prefix in E2B and E4B stands for effective parameters, not total parameters. The E2B has 5.1 billion total parameters but activates only 2.3 billion during inference, which is what matters for speed and memory consumption.

The 26B MoE is my personal pick for most developers. It activates only 3.8 billion parameters per token during inference while delivering 97% of the dense 31B model's output quality. That ratio is remarkable. You get 27B-class reasoning at 4B-class speed. Running it on a 24GB GPU with Q4 quantization is entirely realistic.

The E2B and E4B models also include native audio processing, meaning speech recognition and speech-to-translated-text entirely on-device. The larger models process images and video but not audio. It is an unusual split that probably surprised a few people.

Gemma 4 Benchmarks: How Good Is It Really?

On AIME 2026, the mathematical reasoning benchmark, Gemma 4 31B scores 89.2%. Gemma 3 27B scored 20.8% on the same test. That is not incremental improvement. That is a completely different model.

I will be honest: I was skeptical reading these numbers. A 31B model ranking third on the Arena AI leaderboard against models with hundreds of billions of parameters felt like benchmark cherry-picking. But the Codeforces ELO jump from 110 to 2,150 is not a cherry-picked stat. That is a real, independently measured signal about coding capability.

The 26B MoE model deserves a separate call-out. It scores 88.3% on AIME 2026 with only 3.8B active parameters. For comparison, the dense 31B activates 30.7B parameters for every token. You are getting nearly identical reasoning quality at roughly one-eighth the inference compute. If you are building a production coding assistant or agentic workflow, the MoE variant is almost certainly the right choice on cost grounds alone.

The long-context story is also genuinely improved. On multi-needle retrieval tests, the 31B model went from 13.5% accuracy with Gemma 3 to 66.4% with Gemma 4 at a 256K context window. That is the difference between a model that loses track of what you told it 50 pages ago versus one that actually uses your entire document.

Is Gemma 4 Open Source? (The Apache 2.0 License Shift)

Yes. Gemma 4 is fully open source under the Apache 2.0 license. This is a significant change from every previous Gemma release, which shipped under a custom 'Gemma License' with usage restrictions and terms Google could update at will.

For enterprise teams, this matters more than most people realize. The old Gemma license required legal review. Compliance teams flagged edge cases. Some organizations simply could not use Gemma because their legal frameworks required standard open-source terms. Apache 2.0 eliminates all of that friction.

Hugging Face co-founder Clement Delangue described the licensing shift as "a huge milestone" for the open-source AI ecosystem. The Qwen and Mistral model families have both used Apache 2.0 for a while, which pushed enterprise adoption toward them over Gemma. That competitive disadvantage is now gone.

Apache 2.0 means you can use Gemma 4 commercially, modify it, redistribute it, fine-tune it and sell the result, and deploy it in products without restriction. The only requirement is attribution. For AI developers building products, this is the license you want.

Gemma 4 Architecture: What Makes It Different

Gemma 4 uses a hybrid attention architecture that alternates between local sliding-window attention and global full-context attention layers. This design enables the 256K context window without exploding memory consumption, which is the hard engineering problem that has limited most open models.

There are two architectural features worth understanding if you plan to deploy or fine-tune Gemma 4.

Per-Layer Embeddings (PLE): A second embedding table feeds a small residual signal into every decoder layer. Each layer gets a token-identity component tailored specifically to its role in the network. This is a quiet innovation that contributes to the quality jump, and it is not something competitors have widely adopted yet.

Shared KV Cache: The final N decoder layers share key-value states from earlier layers, eliminating redundant KV projections. This reduces memory usage during long-context inference without a meaningful quality hit. For teams running 256K-token inference on codebases or long documents, this translates directly to GPU memory savings.

The MoE architecture in the 26B model is also worth a note. Google chose 128 small experts with 8 active per token plus one always-on shared expert, rather than the pattern of a handful of large experts used by other models. The result is a model that benchmarks at 27B-to-31B dense quality while running at roughly 4B-class throughput. That is not just a benchmark curiosity. It directly affects what hardware you need and what it costs to serve.

How to Download and Run Gemma 4 with Ollama

Ollama is the fastest way to get Gemma 4 running locally. You can have the E2B model generating responses in under five minutes on any modern laptop. Here is exactly how to do it.

Step 1: Install Ollama

Download Ollama from ollama.com/download. It supports Windows, macOS, and Linux. Run the installer and confirm it works:

ollama --version

Step 2: Pull Your Preferred Gemma 4 Model

# Smallest — runs on most phones and laptops (5GB RAM)
ollama run gemma4:e2b
# Recommended for 16GB+ RAM laptops
ollama run gemma4:e4b
# MoE — best quality/cost ratio on 24GB GPU
ollama run gemma4:26b
ollama run gemma4:31b  # Max quality — needs 80GB H100

Hardware Requirements at a Glance

Ollama handles the chat template complexity automatically. Once the model is running, it exposes a local API at http://localhost:11434, which is compatible with the OpenAI SDK. Any application that supports OpenAI models can be pointed at your local Gemma 4 instance with no code changes.

If you prefer a GUI, LM Studio and Google AI Edge Gallery both support Gemma 4 on day one. You can also access the 31B and 26B models directly in Google AI Studio without any local setup.

Gemma 4 vs Qwen3 vs Llama 4: Which Should You Use?

At the small-to-medium size tier, Gemma 4 now leads. Qwen 3.5 still holds an edge at massive scale (the 397B flagship is a different class of model), and Llama 4 offers a 10-million-token context window that Gemma 4 does not match. But for most practical deployments, Gemma 4 wins on the metrics that matter.

My honest take: use the Gemma 4 26B MoE if you are building a coding assistant, document processing pipeline, or agentic workflow and your documents fit in 256K tokens. Use Llama 4 Scout if you need that absurd 10-million-token context for truly massive codebases or multi-document reasoning. Use Qwen 3.5 if you need deep multilingual support for CJK or other non-Latin scripts, where Qwen's 250K-vocabulary advantage still holds.

The bigger shift in this release is not benchmark position. It is the Apache 2.0 license. Enterprises that had been blocked by Gemma's custom license terms now have no reason to avoid it.

Gemma 4 Real-World Use Cases

Gemma 4 is built for agentic workflows first. Google designed function calling and structured JSON output into the architecture from the ground up, not as a post-training patch. Here are the concrete use cases this unlocks:

Private coding assistant: Run the 26B MoE locally on a workstation. Feed your entire codebase in a single 256K-token prompt. Get bug fixes and feature implementation without sending a single line of proprietary code to a cloud server. This is directly supported in Android Studio using Agent Mode with Gemma 4 as the local model.

On-device multilingual voice interface: The E2B and E4B models support native audio input for automatic speech recognition and speech-to-translated-text. 140+ languages, processed entirely on the phone, with no internet connection required. For healthcare, field service, or multilingual customer interaction use cases, this replaces an external ASR pipeline entirely.

Edge AI and robotics: On a Raspberry Pi 5, Gemma 4 E2B achieves 133 tokens per second prefill throughput and 7.6 tokens per second decode throughput via LiteRT-LM. That is fast enough for real-time smart home controllers and voice assistants running completely offline.

Long-document analysis: At 256K tokens, Gemma 4 can process approximately 200 pages of text in a single prompt. The multi-needle retrieval accuracy of 66.4% (up from 13.5% in Gemma 3) means it actually uses that context rather than losing information halfway through.

Fine-tuning for specialized domains: Under Apache 2.0, you can fine-tune Gemma 4 and distribute the result commercially. Google has already demonstrated this with Yale University's Cell2Sentence-Scale for cancer research and INSAIT's Bulgarian-first language model. Your fine-tuned variant is yours to deploy however you want.

FAQ: Everything People Are Asking About Google Gemma 4

What is Google Gemma 4?

Google Gemma 4 is a family of four open-weight AI models released by Google DeepMind on April 2, 2026. The models come in four sizes (E2B, E4B, 26B MoE, 31B Dense), support multimodal input including text, images, audio, and video, and are built from the same research as the Gemini 3 commercial model. The entire family is released under an Apache 2.0 license.

Is Gemma 4 open source?

Yes. Gemma 4 is released under the Apache 2.0 license, which is the most permissive open-source license widely used in AI. This is a change from previous Gemma versions, which used a custom Gemma License with commercial restrictions. Apache 2.0 allows commercial use, redistribution, and modification with no special restrictions beyond attribution.

How do I download and run Gemma 4 with Ollama?

Install Ollama from ollama.com/download. Then run 'ollama run gemma4:e2b' for the smallest model or 'ollama run gemma4:26b' for the recommended MoE variant. The E2B model runs with under 1.5 GB of memory. The 26B MoE needs approximately 18 GB in Q4 quantization. Ollama handles the full setup automatically.

What is the parameter count of Gemma 4 E4B?

The Gemma 4 E4B has approximately 8 billion total parameters but only 4.5 billion effective parameters during inference. The 'E' in the name denotes effective parameters, which is what determines actual speed and memory requirements. This makes E4B well-suited for 16GB laptops and modern mobile devices.

Is Qwen3 better than Gemma 4?

It depends on the task and size tier. Gemma 4 31B outperforms Qwen 3.5 32B on AIME 2026 math reasoning (89.2% vs approximately 85%) and LiveCodeBench coding. However, Qwen 3.5 has superior multilingual vocabulary coverage (250K-token vocab vs Gemma 4's 256K context) for CJK and non-Latin scripts. For most English-language and coding tasks, Gemma 4 now leads at the 26-31B size tier.

What is Google Gemma 4 31B performance on benchmarks?

Gemma 4 31B Dense scores 89.2% on AIME 2026, 80.0% on LiveCodeBench v6, a Codeforces ELO of 2,150, 85.7% on GPQA Diamond graduate-level science reasoning, and 76.9% on MMMU Pro visual reasoning. It currently ranks third on the Arena AI text leaderboard with an estimated LMArena score of 1,452, outperforming models with up to 20x more parameters.

Can Gemma 4 run on a consumer GPU?

Yes. The Gemma 4 26B MoE runs on a 24GB GPU such as an NVIDIA RTX 3090 or 4090 with Q4 quantization. The 31B Dense model fits on a single 80GB NVIDIA H100 at full bfloat16 precision, or on consumer GPUs using quantized versions. The E2B and E4B models run on CPUs, including Raspberry Pi 5 and Apple M-series Macs.

What platforms support Gemma 4 on day one?

Gemma 4 has day-one support across Hugging Face Transformers, Ollama, LM Studio, llama.cpp, MLX, vLLM, NVIDIA NIM and NeMo, Unsloth, SGLang, Docker, Keras, and Google AI Studio. The model weights are downloadable from Hugging Face, Kaggle, and Ollama. Google AI Edge Gallery supports E2B and E4B for mobile devices.

Recommended Blogs

These are real, published posts from buildfastwithai.com that are directly relevant to readers of this Gemma 4 piece:

Google Releases Gemma 3 — Here's What You Need To Know

How to Run Google's Gemma 3 270M Locally: A Complete Developer's Guide

Supercharge LLM Inference with vLLM

How to Build a General-Purpose LLM Agent

Sarvam-105B: India's Open-Source LLM for 22 Indian Languages (2026)

References

All sources cited in this blog post. Every link verified as live on April 3, 2026.

Google DeepMind

Official Gemma 4 launch announcement — model family overview, benchmark data, licensing details, and available platforms

Hugging Face

Gemma 4 technical deep-dive by the Hugging Face team — architecture details, Per-Layer Embeddings, Shared KV Cache, MoE design, and LMArena scores

VentureBeat

Analysis of why the Apache 2.0 license change matters more than benchmarks — enterprise deployment implications, architecture details, and inference economics

Unsloth

Official local run guide for Gemma 4 — VRAM requirements per model, GGUF quantization options, llama.cpp commands, and Unsloth Studio setup

Ollama Library

Official Ollama page for Gemma 4 — pull commands, model tags (e2b, e4b, 26b, 31b), chat template documentation, and sampling configuration

Google AI Developers

Official guide to running Gemma 4 with Ollama — setup instructions, curl API examples, model management, and integration documentation

Lushbinary

Independent benchmark analysis — AIME 2026 scores, Codeforces ELO, LiveCodeBench v6, and head-to-head comparison vs Qwen 3.5 and Llama 4

I opened X this morning and the top post from Z.ai stopped me mid-scroll: they shipped a vision model that doesn't just understand code. It sees your screen, reads your design draft, watches your bug replay video, and then writes the code to fix it. That's a genuinely different product.

GLM-5V-Turbo is Z.ai's first native multimodal vision coding model, and it launched April 1, 2026. Not a gimmick, not a slight update. A full multimodal architecture built specifically for agentic engineering workflows, with deep integrations into OpenClaw and Claude Code.

The timing matters. Z.ai (formerly Zhipu AI) IPO'd on the Hong Kong Stock Exchange on January 8, 2026 at HK$116.20 per share, valuing the company at HK$52.83 billion. They now serve more than 12,000 enterprise customers and 45 million developers. This isn't a lab experiment. It's a production product from one of China's most serious AI companies.

Here's the full breakdown.

What Is GLM-5V-Turbo?

GLM-5V-Turbo is Z.ai's first native multimodal agent foundation model, built specifically for vision-based coding and agent-driven tasks. It natively handles image, video, and text inputs, and is designed to complete the full loop of perceive, plan, and execute.

That phrase matters. Most vision-language models stop at 'perceive.' They describe what they see. GLM-5V-Turbo is built to close the loop: see a UI mockup, plan the component structure, and execute the code. That's a harder problem, and it's what makes this launch worth paying attention to.

The model supports a 200K context window with a maximum output of 131,072 tokens. You can load extensive technical documentation, lengthy video recordings of software interactions, and full design systems into a single session without hitting limits.

Z.ai positions this as a specialist model, not a generalist. And I think that's the right call. Generalist models that can 'also do vision coding' almost always disappoint on the vision coding part.

How the Architecture Actually Works

The core technical distinction is Native Multimodal Fusion. Here's what that means in plain terms.

Older vision-language models used a two-step pipeline: first, a vision encoder turned the image into a text description; then, a language model processed that text. The visual information was already degraded before the LLM ever saw it. Fine-grained spatial details, coordinate relationships, layout hierarchy -- all of that got flattened into words.

GLM-5V-Turbo treats multimodal inputs as primary data during training. Images, videos, design drafts, and document layouts are trained on natively, not converted. Two specific architectural choices make this possible:

•        CogViT Vision Encoder:

•        Processes visual inputs while preserving spatial hierarchies and fine-grained visual details. This is what lets the model identify exact coordinates of UI elements rather than just describing them vaguely.

•        MTP (Multi-Token Prediction) Architecture:

•        Improves inference efficiency and reasoning, which is critical when outputting long code sequences or navigating complex GUI environments. You want fast, reliable token generation when debugging a production system at 2am.

The 200K context window isn't a marketing number. For agentic engineering workflows, you regularly need to load design specs, existing code, error logs, and video transcripts simultaneously. GLM-5V-Turbo's architecture was built to hold all of that at once.

The 30+ Task RL Training That Solves the See-Saw Problem

The 'see-saw' effect is the most persistent unsolved problem in vision-language model development. Improve the model's visual recognition, and its programming logic degrades. Improve the coding ability, and visual understanding suffers. Most VLMs live somewhere in this uncomfortable middle.

Z.ai's approach: train across 30+ tasks simultaneously using Joint Reinforcement Learning. The model doesn't optimize for one capability at a time. It maintains balance across all of them concurrently.

The tasks span four domains that matter for engineering specifically:

•        STEM Reasoning -- maintaining the logical and mathematical foundations required for code

•        Visual Grounding -- precisely identifying coordinates and properties of UI elements

•        Video Analysis -- interpreting temporal changes, essential for debugging animations and user flows

•        Tool Use -- enabling the model to interact with external APIs and software tools

The result is a model that doesn't trade off visual ability for code quality. This is particularly relevant for GUI agents that must see a graphical interface and generate the code or commands to interact with it.

My hot take: joint RL training across 30+ tasks is the most interesting technical detail of this launch. Most labs solve the see-saw problem by just... accepting one side of the tradeoff. Z.ai actually built infrastructure to fight it. Whether the fix holds up at scale will be the question.

OpenClaw and Claude Code: The Deep Integrations

GLM-5V-Turbo isn't a general-purpose model with optional tool support bolted on. It was built for deep adaptation inside two specific agentic ecosystems: OpenClaw and Claude Code.

Why OpenClaw Integration Matters

OpenClaw is an open-source framework for building agents that operate within graphical user interfaces. As I broke down in depth in our post on GLM-5-Turbo's OpenClaw integration, the share of skills in OpenClaw workflows has risen from 26% to 45% in recent months. That growth is exactly why a specialized vision model for OpenClaw makes commercial sense.

GLM-5V-Turbo handles environment deployment, development, and analysis within OpenClaw workflows. Its ability to process design drafts and document layouts is used to automate the setup and manipulation of software environments. You give it a screenshot of the current state, a design doc for the target state, and it plans the execution path.

Claude Code Workflows

The integration with Claude Code is specifically useful for what Z.ai calls 'Claw Scenarios.' A developer provides a screenshot of a bug, or a Figma mockup of a new feature, and GLM-5V-Turbo interprets the visual layout and generates code grounded in the visual evidence. No verbal description required.

This is the workflow I'm most excited about personally. I've spent years translating design screenshots into written specifications before any code gets written. Having a model that reads the screenshot directly and writes the code skips an entire cognitive step that introduces error every single time it happens.

If you've already been running Claude Code in your workflow (I wrote a full breakdown in our Claude Code vs Codex 2026 comparison), GLM-5V-Turbo slots into that ecosystem as the visual perception layer.

Benchmarks: CC-Bench-V2, ZClawBench, and ClawEval

Three benchmarks are central to evaluating GLM-5V-Turbo's performance:

I want to flag something here: ZClawBench and ClawEval are Z.ai's own benchmarks. Self-reported benchmark performance from any AI lab should be treated with appropriate skepticism until external validation happens. That said, Z.ai has a track record worth noting. The GLM-5 base model scored 77.8% on SWE-bench Verified externally, the highest of any open-source model. They have historically backed up their internal numbers.

The more interesting benchmark comparison is how the broader GLM-5 family positions against frontier models. GLM-5.1 (the coding-focused sibling) reached 94.6% of Claude Opus 4.6's score on Z.ai's coding eval, while GLM-5 scored 62.0 on BrowseComp compared to Claude Opus 4.5's 37.0. Context: the BrowseComp gap is significant for web-navigation tasks. For pure vision coding, GLM-5V-Turbo is the specialized answer.

Pricing and API Access

GLM-5V-Turbo is available through Z.ai's API and on OpenRouter with straightforward pricing:

Z.ai also runs a GLM Coding Plan with subscription pricing starting at roughly $9/month. Pro subscribers get early access to new models. If you're running the GLM Coding Plan primarily for text coding tasks, GLM-5V-Turbo adds vision capability without a separate setup.

For comparison: Claude Opus 4.6 charges $5/$25 per million input/output tokens. At $1.20/$4.00, GLM-5V-Turbo is approximately 4x cheaper on input and 6x cheaper on output. For vision-intensive agentic workflows where you're processing many screenshots or design files, that cost gap compounds quickly.

GLM-5V-Turbo vs Other Vision Coding Models

The honest comparison here is harder than it sounds, because 'vision coding model' is a new enough category that direct competitors are limited. Let me be specific about what I'm actually comparing.

A few things stand out. First, GLM-5V-Turbo is the only model in this list purpose-built specifically for vision coding in agentic workflows. GPT-5.4's computer use is impressive but general; Gemini's multimodal is strong but not coding-focused. Second, the price-to-capability ratio for vision coding tasks specifically is where GLM-5V-Turbo wins.

The Kimi K2.5 comparison is worth noting separately. Kimi's native multimodal approach is similar -- I covered it in our Kimi K2.5 review vs Claude for coding. But GLM-5V-Turbo has the OpenClaw integration advantage for teams already in that ecosystem. And GLM-5V-Turbo's CogViT encoder is specifically tuned for spatial accuracy in GUI tasks, not just general visual understanding.

Contrarian take: the model to actually worry about is the one nobody's comparing against. DeepSeek V4's multimodal architecture is coming, and that price point ($0.28/M input) will make every other comparison irrelevant if the vision coding quality holds up.

Who Should Actually Use GLM-5V-Turbo?

Not everyone. Let me be direct about this.

GLM-5V-Turbo is the right choice if you're building or running agentic workflows that involve visual input -- design-to-code, GUI automation, screenshot-based debugging, or video-grounded development. If your coding workflow is entirely text-based, GLM-5 or GLM-5.1 will serve you better and cost less.

Specifically, I'd recommend testing GLM-5V-Turbo if:

•        You're building OpenClaw agents and need the model optimized for that execution environment

•        You regularly hand off Figma mockups, design drafts, or UI screenshots to an AI for code generation

•        You're debugging visually -- sending error screenshots or bug replay recordings to an AI

•        You need 200K context for large documentation plus visual inputs in a single session

•        You're already using the GLM Coding Plan and want to add vision capability without a new integration

If you want to explore the broader GLM ecosystem and how it fits against Claude alternatives, I walked through the full picture in our GLM OCR vs GLM-5-Turbo comparison and the GLM-5.1 review vs Claude Opus 4.6.

Want to learn how to build AI agents that use vision models like GLM-5V-Turbo?

Join Build Fast with AI's Gen AI Launchpad -- an 8-week structured program to go

from 0 to 1 in Generative AI.

Register here

Frequently Asked Questions

What is GLM-5V-Turbo?

GLM-5V-Turbo is Z.ai's first native multimodal vision coding model, launched April 1, 2026. It handles image, video, and text inputs natively using a CogViT Vision Encoder and MTP architecture, and is built specifically for agentic engineering workflows in OpenClaw and Claude Code environments. Context window: 200K tokens. Max output: 131,072 tokens.

What is the difference between a GLM and an LLM?

LLM stands for Large Language Model -- any large-scale AI model trained primarily on text. GLM (General Language Model) is Z.ai's specific model family, originating from Tsinghua University research. GLM-5V-Turbo extends the GLM family into vision-language territory by adding native multimodal training, making it a VLM (Vision-Language Model) rather than a text-only LLM.

How much does GLM-5V-Turbo cost?

GLM-5V-Turbo costs $1.20 per million input tokens and $4.00 per million output tokens on OpenRouter as of April 2026. The context window is 202,752 tokens with up to 131,072 output tokens per response. Z.ai also offers GLM Coding Plan subscriptions starting at approximately $9/month for developers who want plan-based access.

What is OpenClaw and why does GLM-5V-Turbo support it?

OpenClaw is an open-source framework for building AI agents that operate within graphical user interfaces. The share of skills in OpenClaw workflows has grown from 26% to 45% in recent months. GLM-5V-Turbo was specifically aligned during training on OpenClaw task patterns, meaning its tool-calling behavior, visual grounding, and multi-step execution are tuned for that environment.

What benchmarks does GLM-5V-Turbo use?

The three primary benchmarks are CC-Bench-V2 (multimodal coding across backend, frontend, and repo-level tasks), ZClawBench (agent performance in OpenClaw-specific scenarios), and ClawEval (multi-step execution and environment interaction). Note that ZClawBench and ClawEval are Z.ai's proprietary benchmarks; independent validation on these specific evals has not yet been published as of April 2026.

How does GLM-5V-Turbo compare to GPT-4V or Claude for vision coding?

GPT-5.4 offers computer use via OSWorld scoring 75%, but this is general computer control rather than specialized vision coding. Claude Opus 4.6 accepts image inputs but is not a native VLM trained from scratch on multimodal data. GLM-5V-Turbo is purpose-built for vision coding with the CogViT encoder trained natively, OpenClaw integration, and a price point of $1.20/$4.00 per million tokens versus Claude's $5/$25.

What is the see-saw effect in vision AI models?

The see-saw effect is the performance trade-off in vision-language models where improving visual recognition causes programming logic quality to degrade, and vice versa. GLM-5V-Turbo addresses this through 30+ Task Joint Reinforcement Learning, simultaneously optimizing across STEM reasoning, visual grounding, video analysis, and tool use rather than optimizing each capability independently.

Is GLM-5V-Turbo open-source?

GLM-5V-Turbo itself is a proprietary API model as of April 2026. The GLM-5 base model (the text-only foundation) is available open-source under the MIT License on Hugging Face at zai-org/GLM-5. Z.ai has not announced an open-source release timeline for the vision model variant.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1. GLM-5.1 Review: Can It Beat Claude Opus 4.6? (2026)

2. GLM OCR vs GLM-5-Turbo: Which AI Model Should You Use? (2026)

3. GLM-5-Turbo: Zhipu AI's Agent Model Built for OpenClaw

4. Claude Code vs Codex: Which Terminal AI Tool Wins in 2026?

5. Build AI Agents with OpenClaw + Kimi K2.5: Full Guide (2026)

References

1.     Z.ai Launches GLM-5V-Turbo -- MarkTechPost (April 2026)

2.     Z.ai Official X Announcement -- @Zai_org (April 2026)

3.     GLM 5V Turbo -- API Pricing & Providers -- OpenRouter

4.     Z.ai Developer Documentation -- New Released

5.     Z.ai Debuts GLM-5 Turbo for Agents -- VentureBeat

6.     Z.ai Wikipedia -- Company Overview

7.     zai-org/GLM-5 -- Hugging Face Model Card

512,000 lines of proprietary code. On a public npm registry. For three hours.

That's what happened to Anthropic on March 31, 2026. And by the time anyone inside the company noticed, the code was already spreading across GitHub, X, Reddit, LinkedIn, and decentralized repositories where takedown becomes more challenging.

I've spent the last day going through every credible source, developer analysis, and community thread about this leak. This post covers the full timeline, what was actually inside the code, how Anthropic responded, what the social media storm looked like, and the uncomfortable questions nobody at Anthropic is answering publicly.

The short version: this wasn't a hack. It wasn't corporate sabotage. It was a single misconfigured build file. And it may turn out to be one of the most consequential accidental open-sourcing events in AI history.

1. What Actually Happened: The Technical Breakdown

The leak came down to one file type that most developers have shipped carelessly at some point: a .map file.

When you build JavaScript or TypeScript for production, your bundler compresses and minifies everything into a single blob of code. Source maps are the debugging bridge. They connect that compressed output back to the original, human-readable source. They're essential during development. They're supposed to stay private.

Anthropic uses Bun as their bundler for Claude Code. Bun generates source maps by default unless you explicitly configure it not to. Someone forgot to add *.map to the .npmignore file, or missed the configuration flag. That's it. That's the entire root cause.

When version 2.1.88 of @anthropic-ai/claude-code was pushed to the npm registry on March 31, 2026, it shipped with a 59.8 MB JavaScript source map file. That map file contained a reference to a zip archive hosted on Anthropic's Cloudflare R2 storage bucket. The zip was publicly accessible. Inside: 1,900 TypeScript files, 512,000+ lines of code, every slash command, every built-in tool, the full agent orchestration system.

The Register's analysis put it plainly: a single misconfigured .npmignore or files field in package.json can expose everything. Anthropic confirmed this in a statement: 'This was a release packaging issue caused by human error, not a security breach.'

My honest take: this kind of mistake is embarrassingly common. I've seen it in open-source projects, enterprise repos, and side projects. What makes this remarkable is scale. This wasn't a personal project. This was the source of a product generating $2.5 billion in annualized revenue.

2. The Timeline: How 512,000 Lines Went Public in 3 Hours

The sequence of events is almost cinematic in how fast it moved.

Chaofan Shou's post, acted as a digital flare across the developer community. The original X thread alone hit 16 million views. This was not a slow-burn story. Within hours, the codebase was mirrored across GitHub and analyzed by thousands of developers.

One detail I find genuinely funny: the leaked source contains an entire system called 'Undercover Mode,' specifically built to prevent Anthropic's internal information from accidentally appearing in git commits. They built a whole subsystem to avoid leaking details. Then shipped the entire source code by accident.

3. What Was Inside: Secrets Revealed in the Source Code

This is the section everyone was actually interested in. And the discoveries are genuinely surprising.

The KAIROS Autonomous Agent Mode

Referenced over 150 times in the source code, KAIROS, named after the Ancient Greek concept of 'the right time,' is an unreleased autonomous daemon mode. When active, Claude Code operates as an always-on background agent. It handles background sessions and runs a process called autoDream: memory consolidation while you're idle.

The autoDream logic merges disparate observations, removes logical contradictions, and converts vague insights into concrete facts. A forked subagent handles these tasks to prevent the main agent's context from being corrupted by its own maintenance routines. This is a mature engineering approach to a real problem: long-running AI agents getting confused by their own history.

The Three-Layer Self-Healing Memory System

At the core of Claude Code's architecture is a memory system built around MEMORY.md, a lightweight index of pointers (roughly 150 characters per line) that is perpetually loaded into context. Rather than storing everything and retrieving selectively, this system acts as a persistent map of where the important things are.

Developers analyzing the source described this as Anthropic's solution to 'context entropy,' the tendency for AI agents to hallucinate or lose coherence as long sessions grow in complexity. The solution isn't bigger context windows. It's a smarter index.

Internal Model Codenames

Capybara = Claude 4.6 variant, Fennec = Opus 4.6, Numbat = still unreleased.

The code also reveals Anthropic is on Capybara v8, and that v8 has a 29-30% false claims rate, compared to 16.7% in v4. That regression is significant and explains some of the inconsistencies developers have noticed in Claude Code's outputs on complex refactoring tasks. There's also an 'assertiveness counterweight' built into the system to prevent the model from making aggressive rewrites unprompted.

Undercover Mode

Undercover Mode is a feature designed to prevent Claude Code from revealing Anthropic's internal codenames in public git commits. The irony of this system existing while the entire source shipped via npm needs no further commentary.

Buddy: The Tamagotchi

I am not making this up. The source contains a full Tamagotchi-style companion pet system called 'Buddy': deterministic gacha mechanics, species rarity, shiny variants, procedurally generated stats, and a soul description written by Claude on first hatch. The whole system lives in a buddy/ directory and is gated behind a compile-time feature flag. It was almost certainly the planned April 1st release for 2026.

4. How the Internet Reacted: X, Reddit, LinkedIn, and GitHub

The social media response to this leak was, to put it mildly, enormous.

On X (Twitter): The original thread by Chaofan Shou hit 16 million views. Developers started posting analysis within the hour. Key voices: @himanshustwts broke down the memory architecture, Gergely Orosz (The Pragmatic Engineer) analyzed the DMCA situation, and dozens of AI researchers chimed in with competitive analysis.

On GitHub: One fork reportedly hit 32,600 stars and 44,300 forks before DMCA concerns prompted the original uploader to pivot the repo to a Python feature port. Multiple clean-room reimplementations appeared within the same day, including multiple clean-room reimplementations in different programming languages.

On Reddit: Threads on r/MachineLearning, r/programming, and r/LocalLLaMA blew up. The sentiment ranged from engineers impressed by the architecture to competitors gleefully bookmarking the memory system design. The Buddy/Tamagotchi discovery was the most-shared lighthearted moment.

On LinkedIn: AI founders and product leaders posted takes about what this means for closed-source AI tooling. The recurring theme: 'Anthropic's architecture is genuinely impressive, and now every competitor has a free masterclass in production-grade agent design.'

The search trends told their own story. Within 24 hours, queries for 'claude code leaked source github,' 'claude code source code download,' 'is claude code open source,' 'claude code github leak,' and 'instructkr claude code github' all spiked dramatically. developers worldwide were actively discussing the incident across multiple platforms.

5. Anthropic's Response: DMCA, Statements, and Damage Control

Anthropic moved on two fronts simultaneously: public communication and legal action.

On the public side, Anthropic's spokesperson issued this statement across multiple outlets: 'Earlier today, a Claude Code release included some internal source code. No sensitive customer data or credentials were involved or exposed. This was a release packaging issue caused by human error, not a security breach. We're rolling out measures to prevent this from happening again.'

On the legal side, Anthropic filed DMCA takedown notices against GitHub repositories hosting the material. GitHub complied within hours. The original uploader repurposed his repo to host a Python feature port instead, citing legal liability concerns.

Here's where it gets complicated. DMCA works on centralized platforms. It does not work on decentralized infrastructure. Within hours, the code appeared on Gitlawb, a decentralized git platform, with a simple public message: 'Will never be taken down.' Torrents and mirrors proliferated across infrastructure that no legal letter can reach.

The practical reality: reports suggest the code spread widely across multiple platforms. Every DMCA notice Anthropic files is a game of whack-a-mole against infrastructure designed to resist exactly this kind of takedown.

I'll also note: this is apparently the second Claude Code source exposure in twelve months. Business Standard reported this is the second incident, with the first occurring in February 2026. Anthropic has not publicly elaborated on that prior incident.

6. The Security Fallout: Supply Chain Attack Warning

SECURITY ALERT

If you installed or updated Claude Code via npm on March 31, 2026,

between 00:21 and 03:29 UTC, you may have installed a trojanized

version of axios (1.14.1 or 0.30.4) containing a Remote Access Trojan (RAT).

Recommended actions:

1.   Check your lockfiles (package-lock.json, yarn.lock, bun.lockb) for those versions

2. Search for the dependency 'plain-crypto-js' in your project

3.   If found: treat the machine as fully compromised, rotate all secrets, and perform a clean OS reinstallation

4.   Migrate to Anthropic's native installer: curl -fsSL https://claude.ai/install.sh | bash

The security situation got worse fast. Within 24 hours of the leak becoming public, attackers had registered suspicious npm packages specifically targeting developers trying to compile the leaked source code. Security researcher Clement Dumas flagged packages published by 'pacifier136,' including color-diff-napi and modifiers-napi. These are empty stubs now, but the supply chain attack playbook is clear: squat the name, wait for downloads, push a malicious update.

The Hacker News thread on this was the most alarming technical discussion I read. The window where the trojanized axios version was live overlaps with Claude Code's normal update cycle for developers running automated dependency updates. If your systems auto-pull npm packages without pinned versions, check your lockfiles today.

7. The Legal and Copyright Mess Nobody Can Solve

The DMCA situation raises questions that don't have clean answers.

Question 1: Does Anthropic actually own the copyright on this code?

Anthropic's CEO has implied that significant portions of Claude Code were written by Claude itself. The DC Circuit upheld in March 2025 that AI-generated work does not carry automatic copyright. The Supreme Court declined to hear the challenge. If large chunks of the Claude Code codebase were authored by Claude, some legal experts have raised questions about copyright in AI-generated code.

Question 2: Are clean-room rewrites legally protected?

Yes, according to Gergely Orosz and the legal precedent from Phoenix Technologies v. IBM (1984). A clean-room reimplementation that uses the behavior specification but not the original source code is a new creative work. The Rust reimplementation by Kuberwastaken explicitly follows this legal pattern: an AI agent analyzed the source and produced behavioral specs, a separate AI agent implemented from the spec alone, never referencing the original TypeScript. DMCA-proof by design.

Question 3: Was this actually an accident?

The Dev.to post that asked this question most bluntly noted a suspicious detail: some reports suggest there may have been previous exposure incidents. A draft blog post about the Capybara/Mythos model was accidentally publicly accessible just days before. Two leaks in five days, both generating massive press coverage about Anthropic's upcoming roadmap. I'm not claiming it was intentional. But I'd note that Anthropic's engineering teams continued normal product operations through the fallout, including announcing a new /web-setup feature for GitHub credential management during the chaos. Make of that what you will.

8. What This Means for Developers and Competitors

The strategic implications are significant. Axios put it best: 'The leak won't sink Anthropic, but it gives every competitor a free engineering education on how to build a production-grade AI coding agent.'

For Cursor, Copilot, Windsurf, and Codex: they now have a detailed blueprint of Anthropic's memory architecture, orchestration logic, and agent harness design. The KAIROS autonomous mode, the three-layer memory system, the anti-distillation mechanisms — none of this was visible from the outside before March 31. Now it's in every competitor's hands. I already did a deep comparison of Claude Code vs Codex in my Claude Code vs Codex: Which Terminal AI Tool Wins in 2026? post. That analysis now has a new dimension.

For enterprise users: the leak revealed that Anthropic is deeply aware of the performance gaps in its current Capybara model. A 29-30% false claims rate is a number enterprise security teams will pay attention to, especially after reading my earlier post on Is Claude Code Review Worth $15-25 Per PR?.

For developers: the security warning above is real and should be actioned immediately. Beyond that, the clean-room reimplementations (Rust and Python) give the community a starting point for understanding and extending Claude Code's architecture without legal risk. If you're interested in what Claude Code actually does at a technical level, the Claude Code Auto Mode guide I published last week now makes a lot more sense in the context of what the source reveals.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•       Claude Code vs Codex: Which Terminal AI Tool Wins in 2026?

•       Claude Code Auto Mode: Unlock Safer, Faster AI Coding (2026 Guide)

•       Is Claude Code Review Worth $15-25 Per PR? (2026 Verdict)

•       Claude AI 2026: Models, Features, Desktop and More

•       7 AI Tools That Changed Developer Workflow (March 2026)

Want to understand how AI agents like Claude Code actually work, and build your own?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured program

to go from 0 to 1 in Generative AI.

Register here

Frequently Asked Questions

Did Claude Code source code actually get leaked?

Yes, confirmed by Anthropic. On March 31, 2026, version 2.1.88 of the @anthropic-ai/claude-code npm package shipped with a 59.8 MB JavaScript source map file containing references to a publicly accessible zip archive with 512,000+ lines of TypeScript source code. Anthropic called it 'a release packaging issue caused by human error.'

Where can I find the Claude Code source code on GitHub?

Original GitHub mirrors were taken down via DMCA notices issued by Anthropic. However, clean-room reimplementations remain available, including unofficial clean-room reimplementations created by independent developers. These are new creative works, not direct copies of Anthropic's proprietary TypeScript source.

Is Claude Code open source?

No, Claude Code remains proprietary closed-source software owned by Anthropic. The March 31 leak was accidental and Anthropic has been actively issuing DMCA takedowns against repos hosting the original TypeScript source. Clean-room reimplementations in other languages exist but are not the official Claude Code.

What was exposed in the Claude Code source code leak?

The leak exposed approximately 1,900 TypeScript files and 512,000+ lines of code, including the full tool library, slash command implementations, agent orchestration system, memory architecture (KAIROS, MEMORY.md, autoDream), internal model codenames (Capybara = Claude 4.6, Fennec = Opus 4.6, Numbat unreleased), Undercover Mode, and a Tamagotchi companion called Buddy. No customer data, credentials, or model weights were exposed.

Is it safe to use Claude Code after the leak?

If you installed Claude Code via npm between 00:21 and 03:29 UTC on March 31, 2026, you should immediately check your lockfiles for axios versions 1.14.1 or 0.30.4, or the dependency plain-crypto-js. These indicate a potentially trojanized installation. Anthropic recommends switching to the native installer at https://claude.ai/install.sh.

What is KAIROS in Claude Code?

KAIROS is an unreleased autonomous agent mode referenced over 150 times in the leaked source code. It is named after the Ancient Greek word for 'the right time' and enables Claude Code to operate as an always-on background daemon. Key features include background session management and autoDream, a memory consolidation process that runs while the user is idle.

What is the 'instructkr claude code github' search trend about?

'instructkr' refers to the GitHub user Sigrid Jin, a South Korean developer who was featured in the Wall Street Journal for consuming 25 billion Claude Code tokens. After Anthropic's DMCA takedowns, Sigrid Jin built a Python reimplementation called claw-code in a single morning using an AI orchestration tool called oh-my-codex. The repo hit 30,000 stars faster than any repository in history.

Can Anthropic use DMCA to fully remove the leaked Claude Code source?

On centralized platforms like GitHub, yes. GitHub complied within hours. But decentralized infrastructure, including Gitlawb and torrents, is outside DMCA's practical reach. Additionally, if significant portions of Claude Code were written by Claude itself, Anthropic's copyright claim may be legally murky, since the DC Circuit upheld in March 2025 that AI-generated work does not carry automatic copyright.

References

1.      Claude Code's Source Code Appears to Have Leaked: Here's What We Know - VentureBeat

2.      Anthropic Accidentally Exposes Claude Code Source Code - The Register

3.      Anthropic Leaked Its Own Claude Source Code - Axios

4.      Anthropic Accidentally Leaked Claude Code's Source - The Internet Is Keeping It Forever - Decrypt

5.      Kuberwastaken/claude-code: Claude Code in Rust + Breakdown - GitHub

6.      The Great Claude Code Leak of 2026: Accident, Incompetence, or the Best PR Stunt in AI History? - DEV Community

7.      AINews: The Claude Code Source Leak - Latent Space

8.      Claude Code Source Code Leaked via npm Packaging Error, Anthropic Confirms - The Hacker News

9.      Claude Code Source Leak Reportedly Takes New Turn With Suspicious npm Packages - PiunikaWeb

10.   Source Code for Anthropic's Claude Code Leaks at the Exact Wrong Time - Gizmodo

Disclaimer: This article is for educational and informational purposes only.

We do not host, distribute, or encourage access to any leaked proprietary source code.

I woke up on March 31 to a very specific kind of chaos in my feed. Developers were sharing benchmarks, OpenRouter numbers were going wild, and one post kept appearing: Alibaba just dropped a 1-million-token model and made it completely free. That's not a typo.

Qwen 3.6 Plus Preview landed on OpenRouter on March 31, 2026, and the numbers are hard to ignore. Free access. 1M token context. Up to 65,536 output tokens. Built on a next-generation hybrid architecture that community users are clocking at roughly 3x the speed of Claude Opus 4.6 in early tests.

I've been following the Qwen series since Qwen 2.5, and each release has been faster, cheaper, and more capable than the last. But this one feels different. Not just because of the context window. Because of what it signals about where Alibaba is positioning itself against the US AI giants in 2026.

Here's my full breakdown of what Qwen 3.6 Plus Preview actually is, how it stacks up against Qwen 3.5 Omni and other major models, and whether you should build with it right now.

What Is Qwen 3.6 Plus Preview?

Qwen 3.6 Plus Preview is Alibaba's next-generation flagship language model, released on March 30-31, 2026, currently available for free via OpenRouter. It succeeds the Qwen 3.5 Plus series and is built on a new hybrid architecture designed for improved efficiency, stronger reasoning, and more reliable agentic behavior.

The "Preview" label means this is an early-access version. Alibaba is collecting prompt and completion data to improve the model. So skip sensitive or confidential information while testing — but for development, benchmarking, or learning what this thing can do, the free access is genuinely useful.

The headline feature is the 1-million-token context window. To put that in concrete terms: 1M tokens handles approximately 2,000 pages of text in a single request. Entire codebases. Long legal documents. Hours of transcribed meeting notes. All processed in one pass, with no need for chunking, retrieval, or workarounds.

I'll be honest: a year ago, I would have assumed a model with these specs would cost $15+ per million tokens. Instead it's free at the door. That changes a lot of calculations for indie developers and startups running on tight compute budgets.

Key Specs and Architecture

Here's what we know about Qwen 3.6 Plus Preview from official sources and early testing:

•        Context Window: 1,000,000 tokens (1M)

•        Max Output Length: 65,536 tokens per response

•        Architecture: Advanced hybrid (next-generation, not a standard MoE)

•        Reasoning: Built-in chain-of-thought, always active (no thinking mode toggle)

•        Tool Use: Native function calling supported

•        Modality: Text only (not multimodal in this release)

•        Model Size: Not publicly disclosed

•        License: Closed source (not open weights)

•        Availability: Free via OpenRouter (qwen/qwen3.6-plus-preview:free)

•        Release Date: March 30-31, 2026

The architecture upgrade from 3.5 is described as efficiency-focused. Inference energy consumption is lower, and the model reaches conclusions faster while maintaining stability. One of the most common complaints about Qwen 3.5 was overthinking on simple tasks. Qwen 3.6 Plus appears to fix that: it's more decisive, uses fewer tokens to reach answers, and shows better agent reliability in multi-step workflows.

The always-on chain-of-thought is an interesting design choice. No toggle. No thinking vs non-thinking mode. The model reasons through every prompt by default. I think this is actually the right call for an agentic coding model where you want consistent, auditable decision-making. For simple conversational tasks, you might pay a small latency premium. For complex multi-step tasks, you get more reliable outputs.

Qwen 3.6 Plus Preview vs Qwen 3.5 Omni: Head-to-Head

This is the comparison most people in my feed are asking about. Both dropped within 24 hours of each other on March 30-31, 2026. But they are very different models targeting different use cases.

Qwen 3.6 Plus Preview vs Qwen 3.5 Omni Comparison

My take: These are not competing releases. They serve different builders. Qwen 3.5 Omni is a multimodal powerhouse built for voice applications, audio-video analysis, and multilingual markets. If you're building a voice agent or processing video content, Qwen 3.5 Omni (read my full review at Qwen3.5-Omni Review: Does It Beat Gemini in 2026?) is the better pick.

Qwen 3.6 Plus Preview is for text-heavy workloads: large codebase analysis, long-document reasoning, and complex multi-step agents that need to reason carefully and consistently. The 1M context window combined with always-on CoT makes it the better fit for those scenarios.

Full Model Comparison: Qwen 3.6 Plus vs Claude Opus 4.6, GPT-5.4, Gemini 3.1 Pro

Let me put the numbers side by side. This is what I use to evaluate whether a model is worth building on:

On pricing alone, Qwen 3.6 Plus Preview wins by a country mile. Claude Opus 4.6 charges $5.00 per million input tokens and $25.00 per million output tokens. GPT-5.4 is paid. Qwen 3.6 Plus Preview is free during preview. That's not a small gap. That's a fundamentally different cost structure for developers who want to experiment or build MVPs.

Where does Claude Opus 4.6 still win? Production reliability, safety controls, and the depth of its enterprise integrations. If you're shipping to clients who care about compliance and output consistency at scale, Opus 4.6's track record matters. Qwen 3.6 Plus Preview is a week old. The production trust has to be earned over time.

Gemini 3.1 Pro is the benchmark leader right now, scoring 77.1% on ARC-AGI-2 and 94.3% on GPQA Diamond. For pure reasoning and scientific knowledge tasks, it's the strongest general-purpose model available. But it's not free, and the context window math differs by workload.

Speed and Performance: What Early Users Are Saying

Official benchmark numbers for Qwen 3.6 Plus Preview aren't fully public yet at the time of writing. But early community testing on OpenRouter is telling a clear story.

•        Speed: Users are reporting Qwen 3.6 Plus Preview running at up to 3x the output speed of Claude Opus 4.6 in token-per-second tests. This tracks with Alibaba's claim of significantly reduced inference energy consumption in the new hybrid architecture.

•        Agent Stability: Developers building multi-step agents are reporting fewer retries and more consistent tool-call behavior compared to Qwen 3.5. This is a big deal for production agent pipelines where flaky behavior costs real money.

•        Long-Context Performance: 1M context handling in benchmarks shows solid performance. Community tests processing large codebases are reporting accurate retrieval and reasoning across the full window.

•        Vision Tasks: Mixed feedback. This is a text-only model, so any vision comparisons are irrelevant. For multimodal tasks, look at Qwen 3.5 Omni instead.

•        Data Privacy Note: Prompts are collected during the free preview period for model training. Do not send confidential, proprietary, or client data through the free endpoint.

I want to be specific about what we don't know yet. Public benchmark scores on SWE-Bench Verified, HumanEval, and MMLU haven't been published by Alibaba for this specific preview release. The community speed reports are real but informal. Give it 2-3 weeks for third-party evaluators to run proper comparisons. The early signals are very good. But "very good early signals" is not the same as verified SOTA performance.

Who Should Use Qwen 3.6 Plus Preview Right Now?

Build with it if you are:

•        A developer building AI coding agents or code review tools who wants 1M context at zero API cost for testing and development

•        Building long-document workflows: legal contract analysis, financial report summarization, repository-scale code understanding

•        Running multi-step agentic tasks where the new stability improvements in 3.6 Plus matter more than raw benchmark scores

•        A startup or indie developer who cannot afford $5-25 per million tokens for a production-grade frontier model during early validation

•        Testing front-end component generation at scale, where the model's strength in agentic front-end development is directly useful

Wait or look elsewhere if you need:

•        Multimodal inputs (audio, video, images): use Qwen 3.5 Omni instead

•        Verified production stability: this is a preview model collecting training data; production deployments need more track record

•        Open-source weights: Qwen 3.6 Plus Preview is closed source; if on-device or private deployment matters, Qwen 3.5 variants on Hugging Face are a better option

•        The absolute highest reasoning benchmark scores: Gemini 3.1 Pro leads the field on ARC-AGI-2 and GPQA Diamond right now

The use case I'm most excited about personally: using the 1M context window to give an agent an entire codebase and ask it to audit every API endpoint for security issues in one pass. No chunking, no retrieval, no missed context. That workflow alone justifies testing this model seriously.

How to Access Qwen 3.6 Plus Preview for Free

Via OpenRouter (easiest): The model ID is qwen/qwen3.6-plus-preview:free. You need an OpenRouter API key. Free tier access is available during the preview period.

Via Puter.js (no API key needed): Puter.js supports the model with zero setup. Use the model string 'qwen/qwen3.6-plus-preview:free' in your puter.ai.chat() call. Useful for quick prototyping without any authentication setup.

Via OpenAI-compatible clients: Set the base URL to OpenRouter's endpoint and use the model string above. Works with any Python, JavaScript, or cURL setup that supports the OpenAI API format.

One practical note: during the free preview, Alibaba collects prompt and completion data. If you're working with client information, proprietary code, or anything sensitive, use a private instance or wait for the paid API. For benchmarking and personal development work, it's fine.

My Honest Take: What's Great and What's Missing

What's actually impressive:

•        The 1M context window at zero cost is a genuine unlock for developers who couldn't afford frontier-model API pricing at scale

•        The overthinking fix from 3.5 is real and meaningful. Faster, more decisive responses in agent workflows matters in production

•        Speed advantage over Opus 4.6 is significant if the community reports hold up under more systematic testing

•        Always-on chain-of-thought is the right default for agentic coding tasks

What I'm skeptical about:

•        No public benchmark scores yet. "Performs at or above leading SOTA models" is a marketing claim, not a benchmark result. I need to see HumanEval, SWE-Bench, and MMLU numbers before I'd call this definitively better than GPT-5.4 or Gemini 3.1 Pro on reasoning

•        Closed source and data collection during free preview creates legitimate privacy concerns for anyone with real production data

•        No multimodal capability. If Qwen 3.5 Omni taught us anything, it's that the future of these models is full modality. A text-only 3.6 Plus feels like one piece of a larger release strategy, not the whole picture

•        Preview status means this could change, improve, or get restricted at any time. Don't build a critical production system on a free preview model

The contrarian view worth considering: Alibaba releasing this for free isn't purely altruistic. They're training on your prompts. The cost structure only makes sense if the data you generate improves the model enough to justify the inference costs they're absorbing. That's not a reason to avoid it entirely, but it is a reason to be intentional about what you send through it.

Overall verdict: Qwen 3.6 Plus Preview is worth testing immediately if you're a developer building text-heavy agentic workflows. The cost-to-capability ratio during the free preview period is hard to argue with. Just don't confuse "free and fast" with "fully production-ready." Those are different things. Now go build something and see what it actually does.

Frequently Asked Questions

What is Qwen 3.6 Plus Preview?

Qwen 3.6 Plus Preview is Alibaba's next-generation large language model, released on March 30-31, 2026, on OpenRouter. It features a 1-million-token context window, up to 65,536 output tokens, always-on chain-of-thought reasoning, and native function calling. It is currently available free of charge during the preview period.

How does Qwen 3.6 Plus Preview compare to Qwen 3.5 Omni?

Qwen 3.6 Plus Preview is a text-only model focused on agentic coding, long-document reasoning, and multi-step agents. Qwen 3.5 Omni is a fully multimodal model supporting text, image, audio, and video. The 3.6 Plus has a larger 1M native context versus 3.5 Omni's 262K native (extendable to 1M), and addresses the overthinking issues present in the 3.5 series.

Is Qwen 3.6 Plus Preview free to use?

Yes. As of April 2026, Qwen 3.6 Plus Preview is available for free via OpenRouter using the model string qwen/qwen3.6-plus-preview:free. The model collects prompt and completion data during the preview period for model improvement. The paid pricing for the full release has not been announced.

What is the context window of Qwen 3.6 Plus Preview?

Qwen 3.6 Plus Preview supports a 1,000,000-token (1M) context window, equivalent to approximately 2,000 pages of text. This makes it suitable for repository-level code analysis, multi-hour document processing, and complex multi-turn agent workflows without chunking or retrieval.

How fast is Qwen 3.6 Plus Preview vs Claude Opus 4.6?

Early community testing on OpenRouter reports Qwen 3.6 Plus Preview running at approximately 2-3x the output speed of Claude Opus 4.6 in tokens-per-second comparisons. This aligns with Alibaba's claim of significantly reduced inference energy consumption through the new hybrid architecture. Official speed benchmarks have not been published.

Is Qwen 3.6 Plus Preview open source?

No. Qwen 3.6 Plus Preview is a closed-source model. The weights are not publicly available. Access is through the OpenRouter API only. For open-weight Qwen models, the Qwen 3.5 series (including the 9B and 27B variants) remains available on Hugging Face.

What is the difference between Qwen 3.5 Plus and Qwen 3.6 Plus Preview?

Qwen 3.6 Plus Preview upgrades the architecture with a more advanced hybrid design, expands the context window from 262K to 1M tokens, improves agent behavior reliability and reduces overthinking on simple tasks, and generates up to 65,536 output tokens per response. It does not add multimodal capabilities. Chain-of-thought reasoning is always active in 3.6 Plus, compared to optional thinking mode in 3.5.

Should I use Qwen 3.6 Plus Preview for production applications?

Not yet. This is a preview model that collects training data from prompts and completions. It has limited third-party benchmark verification and no long-term production track record. For development, testing, and building prototypes, it is excellent. For production applications handling sensitive data, use Claude Opus 4.6, GPT-5.4, or Gemini 3.1 Pro until Qwen 3.6 Plus reaches general availability with a paid API.

Recommended Blogs

If this breakdown was useful, these posts from Build Fast with AI go deeper on related topics:

1.    Qwen3.5-Omni Review: Does It Beat Gemini in 2026?

2.    GLM-5.1 Review: Can It Beat Claude Opus 4.6? (2026)

3.    Kimi 2.5 Review: Is It Better Than Claude for Coding? (2026)

4.    Claude Code vs Codex: Which Terminal AI Tool Wins in 2026?

5.    LLM Scaling Laws Explained: Will Bigger AI Models Always Win? (2026)

Want to stay ahead of every major AI release? Subscribe to Build Fast with AI for weekly breakdowns, model comparisons, and hands-on tutorials that actually help you ship.

References

1.    Qwen 3.6 Plus Preview on OpenRouter - OpenRouter model page with specs and pricing

2.     Qwen 3.6 Plus Preview Specs - Puter Developer - Technical specs and API integration guide

3.     Qwen 3.6 Plus Preview on OpenRouter - AIBase - Architecture upgrade details and free access announcement

4.     Qwen 3.6 Plus Early Benchmarks - Qubrid - Community benchmark comparisons vs Qwen 3.5 Plus and GLM 5 Turbo

5.     Qwen3.5-Omni Review: Does It Beat Gemini in 2026? - Build Fast with AI, March 31, 2026

I spent last week generating cinematic 4K videos from plain text prompts and paying less than a dollar per clip. That alone should tell you how fast this space is moving.

Google released Veo 3.1 in October 2025, and just expanded the family with Veo 3.1 Lite on March 31, 2026 - cutting developer costs in half.This immediately signals freshness to both readers and Google., and the conversation in every AI community immediately shifted. Not because video AI is new, but because Veo 3.1 is the . This was true in Oct 2025 but audio is now standard. Reframe as: 'Veo 3.1 remains the only model in the space that generates 48kHz synchronized dialogue, not just background sound. more precise, still differentiating. not an afterthought. You get synchronized dialogue, sound effects, and ambient soundscapes baked directly into the generation process. No separate audio track. No post-production band-aid.

If you've been watching the AI video space and wondering which model actually deserves your attention in 2026, this breakdown covers everything: features, real pricing, how it compares to Sora 2 and Kling 3.0, and how to get started with the API today.

What Is Google Veo 3.1?

Veo 3.1 is Google DeepMind's most advanced AI video generation model, released on October 14, 2025, capable of producing high-fidelity 8-second videos in 720p, 1080p, or 4K resolution, with natively generated audio.

It builds on Veo 3 (announced at Google I/O in May 2025) with substantial upgrades across audio quality, cinematic control, image-to-video capability, and resolution options. The model uses a latent diffusion transformer architecture, compressing video data into spatio-temporal patches instead of working with raw pixels. That's what makes it efficient enough to generate 4K output without the wait times you'd expect.

You can access Veo 3.1 via the Gemini app, Google Flow (the filmmaking tool), the Gemini API (developer access), Vertex AI (enterprise), and third-party platforms like Higgsfield and Freepik. It's also embedded in YouTube Shorts for short-form creators and in Google Vids for business teams. I covered how Google Vids integrates Veo 3.1 for Workspace users in the Gemini in Google Workspace guide.

One sentence that matters: Veo 3.1 is the first practical AI video model to generate synchronized audio at 48kHz directly from a text prompt, with lip-sync accuracy within 120ms.

Key Features That Set Veo 3.1 Apart

Here's what actually changed from Veo 3 to Veo 3.1, beyond the version number.

Native Audio Generation

Most AI video models either generate silent video or bolt on audio after the fact. Veo 3.1 generates three types of audio simultaneously: dialogue and speech (synced to character lip movements), sound effects (matched to on-screen action), and ambient audio (environmental soundscapes). The quality runs at 48kHz, which is professional-grade. You still might want post-production polish for broadcast work, but it's a solid production foundation out of the box.

Portrait Mode and Resolution Flexibility

Veo 3.1 now supports both landscape (16:9) and portrait (9:16) output. That second one matters a lot for creators focused on YouTube Shorts, TikTok, and Instagram Reels. You can generate natively vertical videos without cropping or reformatting. Resolution options are 720p, 1080p, and 4K, with higher resolutions adding to latency and cost.

Ingredients to Video: Character Consistency

This is the feature I've seen get the most attention from creators. You can upload up to three reference images of a character, product, or object. Veo 3.1 analyzes them and maintains consistent visual identity across scenes, angles, and settings. That's genuinely hard to do in AI video. Combine it with background and object reuse across scenes, and you can start telling a coherent narrative instead of generating isolated clips.

Scene Extension Up to 140 Seconds

The base clip is 8 seconds. But Veo 3.1's scene extension lets you chain up to 20 extensions, creating videos exceeding 140 seconds. Each extension analyzes the final second of your previous clip (all 24 frames), tracking character position, lighting, camera angle, and motion trajectories before generating the next segment. For professional workflows, this makes Veo 3.1 competitive on duration, where Sora 2 caps at 25 seconds per generation.

Frame-Specific Generation

You can now specify the first frame, last frame, or both when generating a video. This level of scene control is what separates a creative tool from a toy. It means you can define exactly where a shot starts and ends rather than hoping the model picks the right moment.

SynthID Watermarking:

All Veo 3.1 videos contain an invisible digital watermark verifiable at Google's SynthID platform — important for commercial and compliance use cases.

For more on how Veo feeds into Google's larger AI ecosystem, the NotebookLM Cinematic Video Overview guide walks through how Gemini and Veo work together in pipeline workflows.

Veo 3.1 Fast vs. Veo 3.1 Quality: Which Mode Should You Use?

Veo 3.1 comes in two variants: Fast (lower cost, quicker output) and Quality/Standard (higher fidelity, higher cost). The Fast mode cuts cost roughly in half while maintaining strong quality for most use cases.

Here's how I think about it practically:

•        Use

Veo 3.1 Fast when you're iterating on prompts, testing concepts, generating social media content, or working with tight budgets. At $0.10/second for 720p, it's the lowest official cost for any Google video generation.

•        Use

Veo 3.1 Quality when the output is for a client deliverable, a campaign hero video, or anything that needs to stand up to professional scrutiny. The 4K with audio option at $0.60/second is expensive, but for a 5-second clip that would have cost thousands in traditional production, the math still holds up.

My take: fast mode for 80% of work, quality mode for the final 20% that ships. That's the rational workflow, and most professional creators I've talked to have landed in the same place.

Veo 3.1 Lite — What It Is and Who It's For

Google's most cost-effective video model, released March 31, 2026. Less than 50% the cost of Veo 3.1 Fast, with similar generation speed.

Supports:

• 720p and 1080p

• 4s, 6s, 8s clips

• Text-to-video and image-to-video

Does NOT support:

• 4K

• Scene extension

Best for:

Developers building high-volume apps like social media automation, ads, and content pipelines.

Best Prompt Formulas for Veo 3.1

Sweeping drone shot of a lone hiker crossing a fog-covered mountain ridge at dawn, cinematic realism, shallow depth of field. Audio: wind, footsteps, ambient birdsong.

Close-up of a barista pouring latte art in a warm café, slow motion, golden hour lighting. Audio: coffee machine, soft jazz.

Product reveal shot, clean white background, smooth camera push-in, professional lighting. Audio: subtle unboxing sound.

Veo 3.1 Pricing: What It Actually Costs

Here is the actual pricing breakdown as of March 2026, across resolution and audio settings:Here is the updated pricing breakdown as of April 2026, including the new Veo 3.1 Lite tier and the Veo 3.1 Fast price reduction effective April 7:

Last updated: April 2026

The Gemini Advanced subscription gives you access through the app at around $20/month, with generation limits. For high-volume work, the API is the better route. Third-party platforms like fal.ai offer Veo 3.1 access at slightly different rates, which can work out cheaper for specific workflows.

A 5-second clip at Standard with audio costs exactly $2.00. For context: in traditional production, 5 seconds of professional video with synced audio could easily cost $500 or more. Even at the highest tier, AI video generation is orders of magnitude cheaper. The pricing isn't the barrier anymore. The creative skill of prompt writing is.

How to Use Veo 3.1: Access Options and API Quickstart

Veo 3.1 is available through six main channels as of 2026: the Gemini app (consumer), Flow (filmmaking tool), YouTube Shorts (short-form creators), Google Vids (enterprise), the Gemini API (developers), and Vertex AI (cloud enterprise).

For developers, the model string is veo-3.1-generate-preview, accessed via the Gemini API. Here's the basic Python setup:

from google
import genai from google.genai 
import types  client = genai.Client() 
 operation = client.models.generate_videos(  
   model="veo-3.1-generate-preview",   
  prompt="Your prompt here",    
config=types.GenerateVideosConfig( resolution="1080p",   ), )

For reference image usage (Ingredients to Video), you pass up to three images in the reference_images parameter. For scene extension, you pass the previously generated video in the video field.

In the Gemini app and Flow, no code is needed. You log in, craft your prompt, optionally upload reference images, and generate. New users on Flow get free credits to start. For most non-developers, that's the right entry point.

Want to understand how to write better AI prompts before diving into video generation? The Gemini URL Context guide covers prompt-grounding strategies that transfer directly to video generation work.

Veo 3.1 vs. Sora 2 vs. Kling 3.0 vs. Seedance 2.0

The AI video landscape in 2026 has five serious players — and the field shifted in late March when OpenAI paused consumer access to Sora, leaving Veo 3.1 as the most production-stable option for developers. Here's where they each actually stand, without the marketing language:

Veo 3.1 wins on: cinematic quality, native audio synchronization, official API stability, and Google ecosystem integration. It ranks first on both MovieGenBench and VBench for image-to-video quality as of early 2026.

Sora 2 wins on: physics simulation, human motion realism, and prompt adherence for narrative complexity. The caveat is access. As of March 2026, the official API opened to all developers, but third-party resellers still dominate the developer ecosystem for cost reasons.

Kling 3.0 wins on: cost efficiency (roughly $0.029/second through providers like fal.ai), a genuine free tier with daily credits, and 4K at 60fps for the smoothest motion. For high-volume ad production, Kling is hard to argue against on pure economics.

Seedance 2.0 wins on: creative input flexibility. Supporting up to 12 reference files (images, video clips, and audio) is unprecedented. If your workflow starts with rich reference material, Seedance 2.0 gives you the most fine-grained creative control.

My honest take: I don't think there's a single winner here. The professional workflow in 2026 is multi-model. Kling for social iterations, Veo 3.1 for hero content, Sora 2 when physics accuracy is non-negotiable. Paying loyalty to one model is a creative limitation, not a smart strategy.

What Veo 3.1 Gets Wrong (Honest Criticism)

No review is useful without honest criticism. Here's what Veo 3.1 still struggles with.

The 8-second base clip limit is real friction. Yes, you can extend to 140 seconds via chaining. But each extension requires a new API call, new prompt, and careful continuity management. For quick, non-extended content, 8 seconds isn't a lot to work with.

4K video extension isn't supported. Scene extension works only at 720p. If you need long-form 4K content, you're currently stuck stitching clips manually in post-production.

The official API pricing is genuinely expensive for high volumes. At $0.40/second for 1080p with audio, generating 100 videos per week would cost roughly $3,200/month. Kling at $0.029/second through fal.ai does the same volume for around $232/month. For budget-conscious teams, this gap is not trivial.

And I'll say the quiet part out loud: free access is limited. Gemini Advanced at $20/month gives you generation credits, but power users will hit limits fast. The free tier is essentially non-existent for serious video work, unlike Kling 3.0 which offers daily free credits without a credit card.

Who Should Be Using Veo 3.1 Right Now

Veo 3.1 is the right choice for creators and teams where audio-visual quality and Google ecosystem integration matter more than cost per clip.

Specifically:

•        Filmmakers and narrative creators who need character consistency across scenes and cinematic color science. Veo 3.1's output is closest to traditional film standards.

•        Marketing teams producing hero content, where a single brand video justifies the premium and needs to look polished without extensive post-production.

•        Developers building video-generation apps who need a reliable, officially supported API with Google Cloud's infrastructure guarantees behind it.

•        Google Workspace users already in the Gemini app, Flow, or Google Vids ecosystem, where Veo 3.1 is deeply integrated.

•        YouTube Shorts creators who want native portrait-mode video with synchronized audio without any format conversion.

If you're a solo creator on a tight budget running high-volume iterations, Kling 3.0 makes more financial sense. No shame in that. The right tool depends on the job, not brand loyalty.

For a broader picture of how Google's AI tools are being used in production workflows, I'd recommend reading the Nano Banana Pro use cases guide to see how image generation and video generation are increasingly used together in the same pipeline.

Want to build AI-powered video apps and workflows?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured program to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is Google Veo 3.1?

Veo 3.1 is Google DeepMind's most advanced AI video generation model, released in October 2025. It generates 8-second videos at up to 4K resolution with natively synchronized audio, including dialogue, sound effects, and ambient soundscapes. It is accessible via the Gemini API, Gemini app, Google Flow, YouTube Shorts, Google Vids, and Vertex AI.

What is Veo 3.1 Fast, and how does it differ from the standard model?

Veo 3.1 Fast is the lower-cost, faster-processing variant of the model. It costs $0.10/second for 720p output versus $0.40/second (with audio) for the standard version at 1080p. Fast mode is best for iterative prompt testing and social media content. The standard Quality mode delivers superior cinematic fidelity and is the right choice for hero or client-facing video production.

How much does Veo 3.1 cost?

Veo 3.1 pricing via the official Gemini API starts at $0.10/second for Fast mode at 720p. Standard mode ranges from $0.20/second (no audio, 720p-1080p) to $0.60/second (with audio, 4K). A 5-second 1080p clip with audio costs $2.00. Gemini Advanced subscribers get access through the app for around $20/month with generation limits.

Is Veo 3.1 available for free?

Veo 3.1 does not have a meaningful free tier for production use. Gemini Advanced ($20/month) includes some generation credits, but heavy users will exhaust them quickly. Google Flow offers free credits to new users for testing. For truly free AI video generation, Kling 3.0 offers daily free credits without requiring a credit card.

Is Veo 3 limited to 8 seconds?

The base generation is 8 seconds, but Veo 3.1's scene extension capability allows chaining up to 20 clips, creating videos that exceed 140 seconds total. Each extension analyzes the final second of the previous clip to maintain visual continuity. Note that 4K resolution is not available for scene extension, which is currently limited to 720p.

How does Veo 3.1 compare to Sora 2?

Veo 3.1 leads Sora 2 on official API access, native audio generation (synchronized at 48kHz), maximum video duration (140 seconds via extension vs. 25 seconds for Sora 2), and resolution (4K vs. 1080p). Sora 2 has an edge in physics simulation accuracy and human motion realism. Veo 3.1 is also the safer choice for developers who need a stable production API, as Sora 2 access has relied heavily on third-party resellers through early 2026.

What are the best prompt tips for Veo 3.1?

The most effective Veo 3.1 prompts follow a structure of [Cinematography] + [Subject] + [Action] + [Context] + [Style]. Example: 'Sweeping drone shot of a lone astronaut walking across a red desert at golden hour, cinematic realism, shallow depth of field.' Specify dialogue in quotation marks for the model to generate matching lip-synced speech. For scene extensions, prompt natural progressions rather than abrupt cuts to maintain continuity across clips.

How does Veo 3.1 handle character consistency across scenes?

Veo 3.1's Ingredients to Video feature lets you upload up to three reference images of a character, product, or object. The model uses these as a visual guide to maintain consistent appearance across different scenes, settings, and camera angles. This includes consistent facial features, clothing, and object identity, making coherent multi-scene narratives possible without manual compositing. 

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1.        Gemini in Google Workspace: Every Feature Explained (2026)

2.        NotebookLM Cinematic Video Overview: Full Guide (2026)

3.        20+ Top Nano Banana Pro Use Cases + Gemini 3 AI Prompts

4.        How to Use Gemini URL Context for Smarter AI Responses

5.        Google Releases Gemma 3: Here's What You Need to Know

References

1.     Generate Videos with Veo 3.1 in Gemini API - Google AI for Developers (March 2026)

2.     Introducing Veo 3.1 and New Creative Capabilities in the Gemini API - Google Developers Blog (October 2025)

3.     Veo 3.1 Ingredients to Video: New Video Generation Model Updates - Google Blog (January 2026)

4.     What Is Google Veo 3.1? The Flagship AI Video Model from Google - MindStudio (February 2026)

5.     Best AI Video Generators in 2026 - fal.ai (February 2026)

6.     Seedance 2.0 vs Kling 3.0 vs Sora 2 vs Veo 3.1: Complete 2026 AI Video Comparison - LaoZhang AI Blog (February 2026)

7.     Veo - Google DeepMind - Google DeepMind

8. Build with Veo 3.1 Lite — Google Developers Blog (March 31, 2026):

By Satvik Paramkusham, Founder of Build Fast with AI | Updated March 2026

The biggest AI models in the world no longer activate all their parameters for every token. DeepSeek-R1 has 671 billion parameters, but only 37 billion fire per token. Mixtral 8x7B holds 46.7 billion parameters but runs inference at the speed of a 13B model. The architecture making this possible is called Mixture of Experts, or MoE, and in 2026, it's practically the default choice for any serious frontier model.

I've spent a lot of time studying MoE architectures while building with DeepSeek and Mixtral, and I'll be honest: when I first heard "37 billion out of 671 billion parameters active," I thought someone was lying about the math. They weren't. MoE genuinely lets a model carry enormous knowledge while spending a fraction of the compute cost to use it. That trade-off is the entire reason the top 10 open-source models as of 2025 almost all use this design.

Whether you're fine-tuning models, building RAG pipelines, or just trying to understand why DeepSeek-R1 trained for $5.6 million while GPT-4 reportedly cost $50 to $100 million, this is the architecture you need to understand. Let's break it down properly.

What Is Mixture of Experts in AI?

Mixture of Experts is a neural network architecture that routes each input token to a small subset of specialized sub-networks, called experts, instead of activating the entire model for every token. The result is a sparse model: total parameter count stays large (good for knowledge capacity), but computation per token stays small (good for speed and cost).

The concept isn't new. In 1991, Robert Jacobs, Michael Jordan, Steven Nowlan, and Geoffrey Hinton published "Adaptive Mixtures of Local Experts" in Neural Computation. They proposed training a group of separate networks, each learning to handle a different subset of training cases, controlled by a gating network that decided which expert to activate. At the time, they demonstrated this on vowel discrimination tasks. Simple problem, massive idea.

For two decades, MoE stayed mostly academic. Then in 2017, Noam Shazeer (alongside Geoffrey Hinton and Jeff Dean at Google) scaled MoE to a 137 billion parameter LSTM model using sparse gating. By 2021, Google's Switch Transformer scaled it further to 1.6 trillion parameters. The architecture crossed a threshold from interesting to unavoidable.

Key stat: As of 2025, the top 10 most capable open-source AI models all use MoE architecture. This isn't a niche technique anymore.

Why Dense Models Hit a Wall

To understand why MoE matters, you need to understand the problem it solves. In a dense transformer (think GPT-2, original Llama, or Mistral 7B), every single parameter activates for every single token. When you prompt a dense 70B model, all 70 billion parameters fire for every token in your input and every token generated.

This creates a brutal scaling problem. Want a smarter model? You need more parameters. More parameters means more compute per token, more memory, more GPUs, and more cost per inference. Training GPT-4 reportedly cost between $50 million and $100 million. Dense scaling is a linear tax.

The deeper issue: not all parameters are useful for all inputs. A question about Python syntax probably doesn't need the same neural pathways as a question about Roman history. But in a dense model, every neuron fires regardless, wasting computation on parameters contributing nothing to the current task.

MoE breaks this link between parameter count and compute cost. You can double the knowledge capacity without doubling inference cost. That's the insight everything else follows from.

What Are Experts and Why Are They Called That?

In an MoE model, each "expert" is a standard feed-forward neural network (FFN) with its own independent set of parameters. In a transformer architecture, experts replace (or augment) the feed-forward layer inside each transformer block. The analogy to "experts" comes from the 1991 Jacobs et al. paper, which compared them to human specialists: a cardiologist for heart issues, a dermatologist for skin problems.

Here's the important counterintuitive part: experts don't specialize in topics the way people assume. A common misconception is that one expert handles math, another handles code, another handles creative writing. Research on Mixtral 8x7B shows that experts tend to specialize in syntactic and computational patterns, not semantic domains. One expert might handle certain token types or linguistic structures across many topics.

In Mixtral 8x7B, each transformer layer has 8 feed-forward expert networks. For every token, a router selects exactly 2 of those 8. Each expert has identical internal architecture (same FFN dimensions), but their weights diverge during training as they see different token distributions. Nobody manually assigns roles. The model learns specialization entirely on its own.

My take: This emergent specialization is fascinating and slightly humbling. We design the architecture, set up the training incentives, and the model figures out its own division of labor better than we could prescribe manually.

How the Router Decides Which Expert to Use

The router (gating network) is a small, trainable linear layer followed by a softmax function. It takes each token's representation as input and outputs a probability score for every expert. The top-k experts with the highest scores are selected, and only those experts process the token.

Here's the step-by-step process:

•        Token arrives at an MoE layer as a representation vector

•        Router multiplies that vector by its weight matrix to produce one score per expert

•        Softmax converts scores to probabilities across all experts

•        Top-k experts (typically 1 or 2) are selected based on highest probability

•        Selected experts process the token independently

•        Expert outputs are combined as a weighted sum, using the router's probability scores as weights

Different models choose different top-k values. The Switch Transformer uses top-1 (simplest, lowest overhead). Mixtral uses top-2. DeepSeek-V3 takes it to an extreme: 256 experts per layer with 8 active per token.

Load balancing is the critical engineering challenge here. If the router sends most tokens to a few popular experts while ignoring others, those experts get overloaded and the rest go undertrained. This is called routing collapse. The Switch Transformer solved this with auxiliary load-balancing losses during training. DeepSeek-V3 took a different approach entirely, eliminating auxiliary losses and instead using a bias term on gating values that adjusts dynamically when experts become imbalanced.

MoE vs Dense Models: Efficiency Comparison

The efficiency advantage is simple: massive increase in knowledge capacity, without proportionally increasing compute per token. Here's what that looks like in practice.

Consider Mixtral 8x7B. It has 46.7 billion total parameters but activates only roughly 13 billion per token during inference. The result: it outperforms Llama 2 70B on 9 out of 12 evaluated benchmarks, including mathematics, code generation, and multilingual understanding, while running approximately 6x faster at inference. Llama 2 70B is a dense model. It always activates all 70 billion. Mixtral routes smarter.

Google's research comparing MoE and dense models at 6.4B, 12.6B, and 29.6B scales found MoE models consistently outperformed dense baselines. At the 6.4B scale, an MoE model was 2.06x faster per training step while achieving better benchmark performance. A separate study found MoE models show approximately 16.37% better data utilization than dense models under similar computational budgets.

The trade-off nobody mentions enough: MoE saves compute, not memory. All experts must be loaded into GPU memory because the router needs access to all of them for dynamic decisions. DeepSeek-R1 still requires around 800 GB of GPU memory in FP8 format. If you're trying to run it locally, you need a server with 8 NVIDIA H200 GPUs minimum. This distinction trips up a lot of practitioners.

Real-World MoE Models You Should Know (2026)

The MoE landscape exploded in 2023-2025. Here are the models that define the current state of the art:

Mixtral 8x7B (Mistral AI, December 2023)

The model that brought MoE to the open-source mainstream. 46.7B total parameters, ~13B active per token. Matched or beat GPT-3.5 and Llama 2 70B across most benchmarks, released under Apache 2.0. It proved MoE could work brilliantly at consumer-accessible scales.

DeepSeek-V3 and DeepSeek-R1 (DeepSeek, Dec 2024/Jan 2025)

The current MoE benchmark. 671B total parameters, 37B active, 256 experts per layer with 8 active per token. R1 added reinforcement learning on top, achieving 79.8% on AIME and 2,029 Elo on Codeforces-style challenges, on par with OpenAI's o1. Trained for approximately $5.6 million in GPU hours.

Google Switch Transformer (2021)

The first 1.6 trillion parameter model. Used top-1 routing (single expert per token), demonstrating that one expert was sufficient for strong performance. It was 4x faster than T5-XXL at reaching equivalent quality benchmarks.

GPT-4 (OpenAI, March 2023)

Widely reported (though not officially confirmed by OpenAI) to use an MoE architecture. If accurate, it would explain strong performance across diverse tasks while maintaining manageable inference speeds. OpenAI has never officially confirmed the architecture details.

Gemini 1.5 (Google, February 2024)

Google's multimodal MoE model, notable for its 1 million token context window. Google's official technical report confirms an MoE architecture, though specific expert counts are not disclosed

Key Challenges and Trade-Offs

MoE isn't a free lunch. Here are the real challenges, ranked by how much they'll actually affect you as a practitioner:

1. Memory Requirements

All experts must reside in GPU memory simultaneously, even though only a subset fires per token. A model like DeepSeek-R1 requires around 800 GB of GPU memory in FP8 format. For local deployment, quantized versions or distilled dense variants like DeepSeek-R1-Distill-Qwen-32B are the practical option.

2. Training Stability

Hard routing decisions can cause instability, especially in lower precision formats like bfloat16. The Switch Transformer team solved this by selectively casting router computations to float32 precision while keeping everything else in bfloat16. Worth knowing if you're doing any custom training.

3. Fine-Tuning Behavior

MoE fine-tunes differently than dense models. Research from the ST-MoE project found that freezing only the MoE layer parameters (roughly 80% of the model) during fine-tuning preserves nearly all performance while significantly reducing training time. Sparse models also tend to benefit from smaller batch sizes and higher learning rates.

4. Expert Utilization Imbalance

Routing collapse, where a few experts handle most tokens while others are undertrained, remains an active research problem. The evolution from auxiliary losses (Switch Transformer) to bias-based routing (DeepSeek-V3) shows the field is still iterating on this.

How to Get Started with MoE Models

If you want to experiment today, here are the practical entry points:

•        Mixtral 8x7B locally: Fits on consumer GPUs with quantization (4-bit or 8-bit). Use Ollama or llama.cpp for the simplest setup. Best starting point if you're new to MoE.

•        DeepSeek-R1 distilled variants: The 32B distilled version retains most of R1's reasoning capability at a fraction of the cost. Runs on vLLM and SGLang. This is what I'd recommend for most production use cases today.

•        API access: Both Mixtral and DeepSeek-R1 are available via Together AI, Fireworks AI, and other inference providers if you want to skip the infrastructure entirely.

For application developers, MoE models are especially well-suited for RAG pipelines, multi-turn agents, and real-time assistants. The reduced per-token compute cost compounds significantly when your application makes many sequential model calls.

If you're on the research side, the active frontier questions include: optimal activation rates (recent work suggests around 20% activation is a sweet spot), better routing mechanisms beyond simple linear routers, and scaling expert counts into the hundreds while maintaining training stability.

People Also Ask (FAQ)

What is Mixture of Experts (MoE) in simple terms?

MoE is a model architecture that splits the model into multiple specialized sub-networks called experts, then uses a router to activate only a few of them for each input token. Instead of running all parameters every time, it routes each token to the most relevant experts. This lets a model have more total knowledge without proportionally more compute cost.

How is MoE different from a dense model?

A dense model activates 100% of its parameters for every token. An MoE model might have 671 billion total parameters but only activate 37 billion (about 5.5%) per token. Dense models scale compute linearly with parameter count. MoE breaks that relationship.

Why does MoE use less compute but not less memory?

Because the router needs access to all experts to make dynamic routing decisions per token. All expert weights must be loaded into GPU memory at inference time, even if only a few fire. This is the core trade-off: MoE saves FLOPs (compute), not memory footprint.

Which AI models use Mixture of Experts architecture?

Confirmed MoE models include Mixtral 8x7B and 8x22B (Mistral AI), DeepSeek-V3 and DeepSeek-R1, Google Switch Transformer, and Gemini 1.5. GPT-4 is widely reported to use MoE, but OpenAI has not officially confirmed this.

What is routing collapse in MoE models?

Routing collapse happens when the gating network learns to send most tokens to a small subset of popular experts while ignoring others. The overloaded experts become undertrained on diverse data, while the neglected ones waste capacity. Load balancing losses during training (or dynamic bias adjustments in DeepSeek-V3's approach) prevent this.

Can I fine-tune a Mixture of Experts model?

Yes. Research from the ST-MoE project recommends freezing the MoE layer parameters (about 80% of the model) and fine-tuning only the attention layers and other non-expert components. This preserves performance while dramatically reducing fine-tuning cost and improving stability.

Is Mixture of Experts better than dense models?

For most large-scale tasks, yes on compute efficiency. MoE models consistently match or outperform dense models of equivalent compute cost, and outperform dense models with similar total parameter counts. The catch is the memory requirement: MoE models still need large GPU memory to hold all experts, even if only a fraction activate per token.

What does "top-k routing" mean in MoE?

Top-k routing means the gating network selects the k experts with the highest probability scores for each token. Top-1 routing (one expert per token, used in Switch Transformer) minimizes overhead but loses some representational richness. Top-2 (used in Mixtral) is the most common balance. DeepSeek-V3 uses top-8 out of 256 experts.

Recommended Blogs

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1.     Claude Code vs GitHub Copilot: Which AI Coding Tool Is Actually Better in 2026?

2.     DeepSeek-R1 Deep Dive: Architecture, Benchmarks, and How to Run It

3.    How to Build a RAG Pipeline with Mixtral 8x7B (Step-by-Step)

4.     LLM Benchmarks Explained: What MMLU, HumanEval, and AIME Actually Test

5.      Fine-Tuning vs RAG: When to Use Each and How to Decide

Want to Build With Cutting-Edge AI Architectures Like MoE?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured bootcamp to go from 0 to 1 in Generative AI. Register at buildfastwithai.com/genai-course.

References

1.   Adaptive Mixtures of Local Experts (1991) - MIT Press / Neural Computation

2.    Switch Transformers: Scaling to Trillion Parameter Models - JMLR (2022)

3.     Mixtral of Experts - arXiv / Mistral AI (2024)

4.     Applying Mixture of Experts in LLM Architectures - NVIDIA Technical Blog (2024)

5.     Mixture of Experts Explained - Hugging Face Blog (2023)

6.    DeepSeek-R1 Architecture Deep Dive - Fireworks AI (2025)

7.      Revisiting MoE and Dense Speed-Accuracy Comparisons - arXiv (2024)

8.     Scaling Laws Across Model Architectures: Dense and MoE Models - arXiv (2024)

9.     A Visual Guide to Mixture of Experts - Maarten Grootendorst (2024)

Alibaba dropped Qwen3.5-Omni on March 30, 2026. And if you blinked, you missed something significant.

The Plus variant hit 215 SOTA results across audio, audio-video understanding, reasoning, and interaction benchmarks. It outperformed Google's Gemini-3.1 Pro on general audio understanding, reasoning, and translation tasks. A voice-first, fully multimodal open model from a Chinese lab just outperformed Google at Google's own game.

I've been tracking the Qwen family since Qwen2.5-Omni, and the pace of improvement here is genuinely hard to wrap your head around. The previous generation supported 19 languages for speech recognition. This one handles 113 languages and dialects. That's not iteration. That's a different category of model.

So let me break down what Qwen3.5-Omni actually does, how it compares against GPT-4o, Gemini, and ElevenLabs, and whether you should actually build with it.

What Is Qwen3.5-Omni?

Qwen3.5-Omni is Alibaba's latest generation full-modal AI model, released on March 30, 2026. It processes text, images, audio, and video natively in a single model pass, and generates both text and streaming speech output in real time.

The key word there is "natively." Most multimodal systems stitch separate models together. GPT-4o uses Whisper for audio transcription, a vision model for image processing, and its language model for reasoning. Three separate pipelines, stitched into one UX. Qwen3.5-Omni doesn't do that. Every modality goes through a single unified model.

The practical difference is speed and contextual coherence. When a model processes video and audio in a single pass, it can reason about what a speaker is saying in the context of what they're showing on screen simultaneously. That capability is genuinely hard to replicate with a pipeline approach.

This is Alibaba's second major AI release in under six weeks. In February 2026, they launched Qwen3.5, which matched frontier models on reasoning and coding. Qwen3.5-Omni extends that into full multimodal territory.

Qwen3.5-Omni Models: Plus, Flash, and Light Compared

The Qwen3.5-Omni family ships in three size tiers, each targeting a different deployment context.

All three variants share the same 256K token context window. To put that in concrete terms: 256K tokens handles over 10 hours of continuous audio or 400 seconds of 720p video with audio. For enterprise use cases like meeting transcription, long-form content moderation, or multi-hour podcast analysis, that context length is a practical requirement, not a luxury.

The Plus variant is the one hitting those 215 SOTA results and outperforming Gemini-3.1 Pro on audio benchmarks. Flash trades some of that capability for lower latency and cost. Light is for when you need on-device or edge deployment.

My take: the Flash variant is probably the most interesting one for most developers. Most real-world applications don't need max-capability Plus but absolutely need something faster and cheaper. I'll be watching to see what the latency numbers look like in production.

How the Thinker-Talker Architecture Works

Qwen3.5-Omni uses a split architecture called Thinker-Talker, first introduced in Qwen2.5-Omni and significantly upgraded here.

The Thinker handles all reasoning and text generation. It processes every input modality including text, images, audio, and video, then generates the internal reasoning representation.

The Talker converts those representations into streaming speech tokens. It runs autoregressively, predicting multi-codebook sequences and synthesizing audio frame-by-frame via the Code2Wav renderer.

The upgrade in version 3.5 is that both Thinker and Talker now use a Hybrid-Attention Mixture-of-Experts (MoE) architecture. This matches the broader Qwen3.5 family's move toward sparse models, meaning the model routes each input token to the most relevant subset of experts rather than activating everything on every pass. The result is lower compute cost at a given capability level.

Pre-training used more than 100 million hours of native multimodal audio-video data. The audio encoder was trained from scratch on 20 million hours of audio data. The vision encoder comes from Qwen3-VL, initialized from SigLIP2-So400m with roughly 543 million parameters.

One architectural detail I find genuinely smart: the Thinker-Talker split allows external systems like RAG pipelines, safety filters, and function calls to intervene between reasoning and speech synthesis. That's important for enterprise deployment, where you often need a layer between the model's raw output and what actually gets spoken to an end user.

Benchmark Comparison: Qwen3.5-Omni vs Gemini vs GPT-4o

Here's where things get interesting. These are benchmark results verified across the Qwen3 and Qwen3.5-Omni family:

On the Qwen3.5-Omni-Plus specifically, the headline results against Gemini-3.1 Pro:

•       General audio understanding, reasoning, recognition, and translation: Qwen3.5-Omni-Plus wins outright

•       Audio-video comprehension: Matches Gemini-3.1 Pro overall

•       Multilingual voice stability across 20 languages: Beats ElevenLabs, GPT-Audio, and Minimax

For document recognition, the broader Qwen3.5 family scores 90.8 on OmniDocBench v1.5, outperforming GPT-5.2 (85.7), Claude Opus 4.5 (87.7), and Gemini-3.1 Pro (88.5).

I want to be honest about one thing: the "215 SOTA results" number is a marketing claim, not a single unified benchmark. It's an aggregate across many audio, audio-video, and interaction-specific evals. What actually matters is performance on the specific benchmarks relevant to your use case. The audio numbers look strong. The broader model-level comparisons against GPT-5.2 and Claude Opus 4.5 are based on the Qwen3.5 base family, not specifically the Omni variant.

Audio-Visual Vibe Coding: What It Actually Does

Audio-Visual Vibe Coding is Qwen3.5-Omni's most distinctive new feature. The concept: you show the model a screen recording or video of a coding task, speak your intent out loud, and the model writes functional code based on what it sees and hears combined, with no text prompt required.

The idea is actually fairly profound. Instead of describing what you want in a text prompt, you demonstrate it. Point your camera at a UI bug, say "fix this," and the model processes both the visual evidence and your voice simultaneously.

In practice, this works because Qwen3.5-Omni processes audio and video in a single pass rather than transcribing speech first and then separately analyzing the video. The contextual link between what you're saying and what you're pointing at is maintained throughout the inference.

Whether this becomes a practical developer workflow or stays a cool demo depends on latency. The previous generation Qwen3-Omni Flash achieved voice response latency as low as 234 milliseconds, which is genuinely conversation-speed.

Other real-time interaction features added in this release:

•       Semantic interruption: The model distinguishes between "uh-huh" mid-conversation and an actual intent to cut in, so it doesn't stop mid-thought every time there's background noise.

•       Voice cloning: Generate custom voices from short reference clips.

•       Real-time web search: The model can answer questions about breaking news or live data without pretending it already knows.

That last one matters more than people are giving it credit for. Most omni models are static inference engines. Baking real-time web search into the omni model means voice-first applications can actually answer current questions without a separate RAG pipeline.

Who Should Use Qwen3.5-Omni?

Qwen3.5-Omni is worth serious evaluation if you're building in one of these areas.

Voice-first applications: 113 language support plus native voice cloning and semantic interruption makes this one of the strongest open-source foundations for multilingual voice agents. DeepSeek, Mistral, and Meta's Llama don't have comparable voice-native capabilities right now.

Meeting and audio intelligence: The 10-hour context window combined with strong multilingual speech recognition (1.7% WER on LibriSpeech, matching Gemini 2.5 Pro) makes it a serious option for long-form transcription and analysis.

Video understanding: 400 seconds of 720p video at 1 FPS in a single context pass. For content moderation, video summarization, or educational content processing, that's a meaningful capability.

Multilingual markets: 113 recognition languages is unusually broad coverage. If you're building for markets where major US models have weak language support, this is a realistic alternative.

Where I'd be more cautious: complex software engineering tasks. Claude Opus 4.5 maintains an edge on SWE-bench at 80%+ compared to the Qwen3.5 family. For pure coding agent workflows, the Qwen models are strong but not definitively ahead on the hardest engineering benchmarks.

How to Access Qwen3.5-Omni Today

Demos are available now on Hugging Face and through Alibaba Cloud. Community fine-tunes have already appeared on Hugging Face following the March 30 release.

For API access, Qwen3.5-Omni-Plus and Flash are available via Alibaba Cloud's DashScope API. The Light variant can be run locally via Hugging Face.

If you're a developer who has already worked with Qwen via the OpenAI-compatible API interface, integration should be familiar. The model supports function calling and native web search baked in, which changes what's possible without external orchestration.

My Honest Take: What's Missing

I think Qwen3.5-Omni is a genuinely impressive release and the audio benchmark numbers look real. But there are things worth being skeptical about.

The "215 SOTA results" headline is a number I'd take with some skepticism. Benchmarks self-selected by the releasing lab tend to favor the releasing lab. More neutral third-party evaluations will tell a clearer story over the next few weeks.

Also, the speech recognition language count. Alibaba lists 113 languages and dialects. That last word matters. Regional dialect variants often get counted separately, which makes the number look bigger than the practical coverage. I'd want to see independent evaluations on lower-resource languages before claiming Qwen3.5-Omni as the definitive multilingual voice option.

That said, for open-source omni models specifically, the competitive gap is real. DeepSeek doesn't have this. Mistral doesn't have this. Meta doesn't have this. If you need a voice-native open model and you don't want to be locked into Google or OpenAI's API, Qwen3.5-Omni is your most serious option right now.

Want to learn how to build AI agents and apps using models like Qwen3.5-Omni?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured program to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is Qwen3.5-Omni?

Qwen3.5-Omni is Alibaba's latest omnimodal AI model, released on March 30, 2026. It processes text, images, audio, and video natively in a single model pass and generates streaming speech output in real time. The Plus variant achieved 215 SOTA benchmark results across audio and audio-video tasks.

How does Qwen3.5-Omni compare to Gemini?

Qwen3.5-Omni-Plus outperforms Google's Gemini-3.1 Pro on general audio understanding, reasoning, recognition, and translation tasks, and matches Gemini-3.1 Pro on audio-video comprehension overall. On multilingual voice stability across 20 languages, it also beats ElevenLabs, GPT-Audio, and Minimax.

What languages does Qwen3.5-Omni support?

Qwen3.5-Omni supports speech recognition for 113 languages and dialects, up from 19 in the previous Qwen3-Omni generation. Speech generation covers 36 languages. The previous Flash variant achieved voice response latency as low as 234 milliseconds.

What is Audio-Visual Vibe Coding in Qwen3.5-Omni?

Audio-Visual Vibe Coding allows the model to watch a screen recording or video of a coding task and generate functional code based on both the visual content and spoken instructions simultaneously, without a text prompt. It works because Qwen3.5-Omni processes audio and video in a single model pass rather than through separate pipelines.

How long can Qwen3.5-Omni process audio or video?

All three Qwen3.5-Omni variants (Plus, Flash, Light) support a 256K token context window. In practical terms, this handles over 10 hours of continuous audio input or up to 400 seconds of 720p video at 1 frame per second with audio.

Is Qwen3.5-Omni open source?

The Light variant is available as open weights on Hugging Face. The Plus and Flash variants are accessible via Alibaba Cloud's DashScope API. The model was pre-trained on over 100 million hours of native multimodal audio-video data using the Thinker-Talker architecture with Hybrid-Attention MoE design.

What is the Thinker-Talker architecture?

Thinker-Talker is Qwen's split model architecture where the Thinker component handles multimodal reasoning and text generation, and the Talker converts those representations into streaming speech. The split allows external systems like RAG pipelines or safety filters to intervene between reasoning and speech output before it reaches the end user.

How does Qwen3.5-Omni compare to GPT-4o?

On Qwen3-Omni generation benchmarks, the model scores 82.0% on MMMU vs GPT-4o's 79.5%, 92.6% on HumanEval vs GPT-4o's 89.2%, and 1.7% word error rate on LibriSpeech vs GPT-4o's 2.2%. The Qwen3.5-Omni-Plus additionally beats GPT-Audio on multilingual voice stability across 20 languages.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1.   GLM-5.1 Review: Can It Beat Claude Opus 4.6? (2026)

2.   Seedance 2.0 Review: ByteDance Tops AI Video in 2026

3.   LLM Scaling Laws Explained: Will Bigger AI Models Always Win? (2026)

4.   Kimi 2.5 Review: Is It Better Than Claude for Coding? (2026)

5.   Claude Code vs Codex: Which Terminal AI Tool Wins in 2026?

References

1.    Qwen3.5-Omni Official Announcement - Alibaba Qwen, March 30 2026

2. Qwen3-Omni Technical Report - arXiv

3.   Qwen3.5-Omni: Alibaba's AI Model Can Now Hear, Watch, and Clone Your Voice - Decrypt

4.    Qwen3-Omni Review: Multimodal Powerhouse or Overhyped Promise? - Analytics Vidhya

5.    Qwen3.5 Features, Access, and Benchmarks - DataCamp

6.    Qwen3.5 Model Card and Deployment Guide - Hugging Face

7.    Qwen3.5-Omni Launch Coverage - Aihola

88% of companies are already using AI in at least one business function. That number is from McKinsey. And yet, when I look at how developers actually build and ship software, most of them are still doing it the old way.

The gap between knowing AI exists and actually deploying production apps with it has never been more expensive. AWS closed a big chunk of that gap in 2025 and 2026 with three tools that genuinely change the workflow: Bedrock, Kiro, and Amplify Gen 2.

In a recent Build Fast with AI live workshop, Avinash Karthik (Software Manager, AWS Amplify) and Salih Guler (Senior Developer Advocate, AWS) walked 350+ developers through the entire stack live, from prompt to deployed production app in under an hour. I'm going to break down everything they covered, with the technical details you actually need.

This is not a summary. It's a working guide.

Watch the Full Workshop (Recommended)

If you want to see everything in action — from idea → code → deployed app in under 60 minutes — watch the full workshop recording below.

👉 Recorded Here

In this session, AWS experts walk through:

- Building an AI app using Bedrock

- Using Kiro for spec-driven development

- Deploying with Amplify Gen 2

- Real-world debugging and deployment flow

⚡ This is the fastest way to understand the full workflow end-to-end.

1. Why AWS AI Adoption Is Accelerating in 2026

AI adoption is no longer optional for enterprises. 88% of organizations globally are using AI in at least one business function, and 40% are already seeing measurable productivity and efficiency returns, according to Deloitte. The strategy question is not whether to adopt, it's how fast you can move.

Three data points from the workshop stood out:

•        60% of companies have appointed a Chief AI Officer, making AI a C-suite priority rather than an IT initiative

•        45% of companies now list generative AI tools as their primary budget item, above infrastructure and traditional software

•        Agentic AI and multi-agent systems are receiving the majority of enterprise GenAI spending in 2026

The companies that are moving fastest are not the ones with the biggest teams. They're the ones using the right tools. That's what this guide covers.

2. AWS's Three-Pillar AI Strategy Explained

AWS did not stumble into AI. They've been building toward a specific strategy: from custom silicon chips (Trainium, Inferentia) all the way up to application-layer tools like Kiro and Amazon Q. Avinash broke it down into three pillars:

Pillar 1: Freedom to Invent

AWS gives you genuine choice. Bedrock alone offers 100+ foundation models from providers including Anthropic (Claude), Amazon (Nova), Meta (Llama), Mistral, and several open-source models. You are not locked into one vendor or one model.

AWS also supports open protocols: MCP (Model Context Protocol) and A2A (Agent-to-Agent). Agents you build on AWS can connect to any external service, not just AWS services. That interoperability is a real differentiator.

Pillar 2: AI You Can Trust

Security and governance are built in from day one. Models in Bedrock run inside your own AWS account and VPC. IAM policies control access at a granular level. Compliance certifications cover the major enterprise standards.

This matters enormously for regulated industries like finance, healthcare, and government. Many AWS enterprise customers chose Bedrock specifically because they can run models without sending data to a third-party API endpoint.

Pillar 3: Maximizing Value

Most companies can build an AI demo in a week. Getting that demo to production takes months. AWS is specifically investing in collapsing that timeline to weeks or days. Kiro and Amplify Gen 2 are the main tools in that effort.

3. Amazon Bedrock: What's New and What Matters

Bedrock has had a massive update cycle since the start of 2025. Here are the three launches that matter most right now:

Bedrock Agent Core (GA October 2025)

Agent Core is the platform for building, deploying, and operating AI agents at scale. Key specs:

•        Agents can execute tasks for up to 8 hours continuously

•        Full session isolation between agent runs

•        Built-in gateways for MCP and A2A protocol connections

•        Native observability: you can monitor what your agents are doing in production

•        Agent memory: agents can learn and store data while executing long tasks

The 8-hour execution window is significant. Most AI agent frameworks time out at minutes. Agent Core is designed for real-world enterprise workflows that span hours, not seconds.

Multi-Agent Orchestration

Bedrock's multi-agent system lets you create networks of specialized agents, coordinated by a supervisor agent. Think of it as a software team: one supervisor (manager) coordinating multiple specialized agents (frontend dev, security, QA, etc.).

The supervisor handles routing, coordination, and workflow execution. Specialized agents focus on one domain each. This architecture produces significantly better results than single-agent systems for complex tasks.

Model Catalog: 100+ Foundation Models

Bedrock added 30+ models in the last 3 months alone. The current lineup includes Claude Opus 4.6, Claude Sonnet 4.5, Amazon Nova, Meta Llama, Mistral, and a growing selection of open-source models. If you need a custom model that is not in the catalog, SageMaker and NovaForge let you bring your own model and host it on AWS infrastructure.

4. AWS Kiro: The AI IDE That Changes How You Develop

Kiro launched in 2025 and is AWS's answer to Cursor, with a fundamentally different development philosophy. Where most AI IDEs focus on fast code generation, Kiro focuses on structured, production-ready development.

The core difference: Kiro uses spec-driven development. You don't just ask it to write code. You describe your requirements, Kiro creates a structured design doc, breaks it into tasks, and executes them systematically. The output is documented, consistent, and production-ready by default.

Kiro's Core Features

Spec-Driven Development

Spec mode works in three phases: first, it defines the technology and architecture; second, it creates a detailed project definition; third, it generates and executes tasks. Because the planning phase is structured and explicit, the output has a higher determinism level than vibe-only approaches. The confidence in what gets built is measurably higher.

Steering Files

Steering files are markdown files that encode your organization's coding conventions, security rules, and architectural decisions. Kiro reads them and generates code that follows your standards automatically. Salih showed his steering file during the demo: it had 8 rules covering TypeScript strictness (no 'any' type), commit conventions, testing commands, and file creation preferences.

If your team has spent years defining best practices, put them in a steering file. Your AI assistant will follow them without being reminded every session. Steering files are the equivalent of your Confluence knowledge base, but actually read by the agent.

Agent Hooks

Agent hooks run automated workflows at specific points in your development cycle. For example: every time you update an OpenAPI spec, a hook can automatically regenerate client libraries. Or every time you commit code in a multilingual app, a hook can trigger translation updates. These repeatable operations save real time at scale.

Native MCP Support

You can add MCP server configurations directly in Kiro. Once configured, Kiro can query those servers during development without burning unnecessary context on multiple roundtrip calls. The AWS MCP Power (more on this below) is a great example of using this efficiently.

Kiro Powers (Context-Efficient Tool Access)

Kiro's context window fills up fast if you're not careful. MCP servers can consume a lot of context if used naively. Kiro Powers solve this by packaging pre-built knowledge, SOPs, and tool routing into compact, on-demand context. The AWS Amplify Power, for example, tells Kiro exactly which tool to call and which SOP to follow, without burning context on multiple documentation lookups.

LSP Integration

Kiro uses Language Server Protocol to understand your project structurally, not just as raw text. It doesn't process your entire codebase as context. It actually understands what's going on: types, imports, call graphs. This is faster and more accurate than the naive approach of dumping all your code into a prompt.

Kiro vs Cursor vs Claude Code

5. AWS MCP Server: One Unified Gateway to 200+ AWS Services

Before AWS MCP Server, connecting an AI agent to AWS required separate tools for each service: one for S3, one for Lambda, one for CDK. Each had limited functionality and required separate configuration. AWS MCP Server consolidates all of that into a single interface.

What's inside AWS MCP Server:

•        15,000+ AWS APIs covered across 200+ AWS services

•        10+ embedded knowledge sources: documentation, best practices, framework guidance, domain-specific knowledge

•        30+ pre-built Agent SOPs (Standard Operating Procedures) for complex multi-step tasks

•        Natural language access: your agent calls any AWS API using plain English

•        Remote server: always up-to-date, no local installation, no maintenance required

•        Free to use

Agent SOPs are the standout feature. For complex multi-step tasks where LLMs tend to produce inconsistent results, SOPs provide a structured playbook the agent follows. AWS has published 30+ specialized SOPs covering common deployment, configuration, and infrastructure tasks.

The practical result: your agent doesn't just access AWS, it understands AWS. It can answer questions about services, look up documentation, and follow proven procedures, all through one MCP connection.

Want to see this entire workflow live?

Watch the full Build Fast with AI workshop here:

6. Live Demo: From Idea to Production in Under 60 Minutes

Avinash walked through the complete flow live during the workshop. Here's the exact process, step by step.

Step 1: Generate the App with Lovable

Avinash used Lovable (a vibe coding tool) to generate a community website for Build Fast with AI. The prompt specified: activity feed, meetup page with RSVP functionality, a community forum, a point system based on activity, and specific technical choices (Vite, React, shadcn/ui, Radix).

Prompt quality matters here. A vague prompt forces the LLM to make architectural decisions, which burns token capacity that should go toward code quality. A specific prompt removes ambiguity and produces better output. Lovable built the full app in under 5 minutes.

Important caveat: the app used mock data at this stage. No backend, no database. Just a front-end running in the browser.

Step 2: Push to GitHub

From Lovable, Avinash connected GitHub directly and pushed the project. This took seconds and gave Kiro a clean starting point to pull from.

Step 3: Open the Project in Kiro

Kiro cloned the repository, analyzed the project using LSP, and identified it as a React TypeScript app using Vite with shadcn components and mock data. No manual configuration needed.

Step 4: Ask Kiro What to Do

Avinash typed a natural language question into Kiro: what does AWS recommend for deploying this website? Kiro queried the AWS MCP Server, which returned the top 5 relevant documentation hits. The recommendation: AWS Amplify Hosting as the simplest path, or S3 plus CloudFront for more infrastructure control.

Step 5: Deploy to AWS Amplify via Kiro

Kiro handled the full deployment:

1.     Built the React app and created a production ZIP file

2.     Called the AWS MCP Server using natural language: deploy this to AWS Amplify

3.     The MCP server translated this into the correct AWS API calls

4.     Created an Amplify app, obtained a pre-signed upload URL, and uploaded the ZIP

5.     Triggered the deployment and polled for status

6.     Returned a live production URL

Total time from Kiro opening the project to a live URL: under 5 minutes. The URL is production-ready, hosted on AWS infrastructure that scales to millions of users automatically.

7. AWS Amplify Gen 2: Migrating from Mock Data to Real Backend

Salih took the same app concept (with the same prompt) and demonstrated a more advanced workflow: migrating the mock data to a real cloud backend using Amplify Gen 2, then adding authentication.

What is AWS Amplify?

AWS Amplify is a full-stack development platform for building mobile and web applications with cloud backends. Amplify Gen 2 (the current version) lets you define your backend using TypeScript, which is then automatically provisioned on AWS. It handles authentication, data models, storage, and API generation.

The Migration Workflow

Salih's prompt to Kiro was: this app uses mock data, migrate everything to Amplify Gen 2, add authentication using Amplify UI libraries, and make all feed/forum/meetup data available to every authenticated user.

Kiro's execution had three phases:

7.     Backend phase: installed Amplify Gen 2 libraries, defined the authentication and data schema in TypeScript, configured user pool settings

8.     Deployment phase: ran the Amplify sandbox deployment command, which provisions the actual AWS backend resources (Cognito user pool, DynamoDB tables, AppSync API)

9.     Frontend connection phase: updated the React components to use Amplify data clients instead of mock data, integrated the Amplify UI auth components

The deployment hit a snag during the live demo: the Cognito user pool was created with self-signup disabled. Kiro caught this automatically (because Salih had set a rule requiring npm run build to succeed before committing), searched the AWS documentation, identified the issue, and redeployed with the correct configuration. No manual debugging required.

Amplify UI Authentication

Rather than writing a custom auth flow from scratch, Kiro used Amplify's pre-built UI components. These handle the entire authentication experience: sign-up, sign-in, email verification, MFA configuration. The components are built for Cognito and connect automatically once the backend is configured.

By the end of the demo, Salih had a running app with real user accounts, real cloud data, and working authentication, all from a vibe-coded starting point.

One honest note from the demo: the AI chat feature they tried to add at the end (an AI assistant that queries the app's meetup data) didn't complete cleanly in the time available. That's a real-world reminder that complex features still take iteration, even with AI tooling.

8. Spec-Driven Development: The New Software Lifecycle

Salih spent time explaining how AI has changed the software development lifecycle (SDLC). The old cycle: plan, analyze, design, develop, test, deploy, maintain. The new cycle looks similar but operates very differently.

How the AI-Augmented SDLC Works

•        Plan: write a proper spec in markdown, define goals AND non-goals, specify tech stack, set acceptance criteria

•        Analyze: use AI tools for research and problem definition, review outputs before proceeding

•        Design and architecture: you make the architecture decisions, AI builds to your spec

•        Build: AI executes the implementation under your direction

•        Verify: run tests, check outputs against acceptance criteria

•        Deploy and monitor: AI-assisted deployment, human monitoring and iteration

The most important shift: you are in the driver's seat. Salih made this point bluntly: if you let the agent run unsupervised and go get lunch, you may come back to a circular debugging loop. AI tools are powerful because humans direct them well, not because they run autonomously.

Writing Effective Specs

A spec for AI-assisted development should include:

•        Clear goals (what you want to build) and explicit non-goals (what the agent should NOT do)

•        Technology choices: specify frameworks, libraries, and constraints

•        Executable test commands: tell the agent how to verify its own work

•        Acceptance criteria: what does success look like?

•        Phased tasks: break complex work into sequential, verifiable phases

Negative prompting matters as much as positive prompting. The more specific you are about what not to do, the less token capacity the agent wastes on bad decisions.

SkillMD and AgentMD Files

These are context management tools. AgentMD (equivalent to CLAUDE.md in Claude Code, or .cursorrules in Cursor) is a project-level readme for your agent. It tells the agent the key facts about the project, conventions, and constraints.

SkillMD is different: it's an entry point to a collection of detailed guides. Rather than loading all knowledge upfront, SkillMD uses progressive disclosure to load only the relevant context for the current task. This keeps your context window healthy on long sessions.

9. Prompting Tips That Actually Matter for AI Development

Avinash made a point about prompting that I think every developer should internalize: the LLMs running your agents typically have 100K to 200K token context windows. Every token spent on a decision is a token taken away from code quality.

When you give a vague prompt, the model has to decide what features to build, what architecture to use, how many components to create, and what the design should look like. Every one of those decisions burns context. The output suffers.

Practical Prompting Guidelines

•        Be explicit about technology choices: don't make the agent pick between React and Vue, tell it which one

•        Specify what NOT to build: negative prompting prevents scope creep

•        Break large requests into phases: let the agent complete and commit one phase before starting the next

•        Set verifiable exit criteria: 'do not commit until npm run build passes' is a rule that prevents partial, broken work

•        Cancel and reiterate: if you see the agent spiraling, cancel the current task and rephrase rather than letting it continue

•        Check context usage: Kiro shows a context percentage indicator; if you're at 70%+, start a new session for the next major task

Avinash also mentioned prompts.dev and the AWS Marketplace for pre-built prompts. Both are worth checking before building a new prompt from scratch. There is no reason to solve a problem that has already been solved.

 Want to build AI agents and deploy full-stack apps like these?
 
 Join Build Fast with AI's Gen AI Launchpad: an 8-week structured program to take
 you from zero to production-ready AI builder.
 
 Register Here

Frequently Asked Questions

What is AWS Kiro and how is it different from Cursor?

AWS Kiro is an AI-powered IDE that uses spec-driven development to produce structured, production-ready code. Unlike Cursor, which is primarily chat-driven and flexible, Kiro creates formal design documents and task breakdowns before writing code. Kiro also has native AWS MCP Server support, built-in agent hooks for automated workflows, and LSP integration for deeper project understanding.

What is Amazon Bedrock and what models does it support?

Amazon Bedrock is AWS's managed AI platform for accessing foundation models without managing infrastructure. It offers 100+ models from providers including Anthropic (Claude Opus 4.6, Sonnet 4.5), Amazon (Nova), Meta (Llama), and Mistral. Models run inside your AWS account and VPC, not on shared third-party infrastructure. Bedrock added 30+ new models in Q1 2026 alone.

What is AWS MCP Server and how does it work?

AWS MCP Server is a unified remote server that gives AI agents natural language access to all 200+ AWS services and 15,000+ AWS APIs. It includes 10+ embedded knowledge sources (documentation, best practices, domain guides) and 30+ pre-built Agent SOPs for complex tasks. It requires no local installation, is always up-to-date, and is free to use.

What is spec-driven development in Kiro?

Spec-driven development is Kiro's approach to building software: instead of writing code immediately from a chat prompt, Kiro first creates a structured design document that defines goals, architecture, and tasks. It then executes those tasks sequentially with built-in verification. This produces more consistent, documented, and production-ready output compared to vibe coding alone.

What is AWS Amplify Gen 2 used for?

AWS Amplify Gen 2 is a full-stack development platform for building web and mobile applications with cloud backends. It lets developers define authentication (Cognito), data models (DynamoDB via AppSync), and storage (S3) using TypeScript, which Amplify then automatically provisions on AWS. It includes pre-built UI components for auth flows and connects to the frontend through generated client libraries.

Can Kiro deploy apps to AWS automatically?

Yes. When connected to AWS MCP Server, Kiro can analyze your project, determine the appropriate AWS deployment strategy, build your application, and deploy it to services like AWS Amplify, all through natural language instructions. In the Build Fast with AI demo, Avinash went from a Kiro prompt to a live production URL in under 5 minutes.

What is the difference between Bedrock and Kiro?

Amazon Bedrock is infrastructure: it hosts foundation models and provides APIs for building AI agents and applications. Kiro is an IDE: a development environment that uses AI to help you write, test, and deploy code. Kiro can use Bedrock models internally, and can deploy applications that call Bedrock APIs, but they operate at different layers of the stack.

How do steering files work in Kiro?

Steering files are markdown files stored in your Kiro project that define coding conventions, security requirements, testing commands, and architectural constraints. Kiro reads them automatically and generates code that follows your rules without needing reminders each session. They are equivalent to .cursorrules in Cursor or CLAUDE.md in Claude Code, but Kiro treats them as first-class configuration.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•        Claude Code vs Codex: Which Terminal AI Tool Wins in 2026?

•        7 AI Tools That Changed Developer Workflow (March 2026)

•        Claude Code Auto Mode: Unlock Safer, Faster AI Coding (2026 Guide)

•        Every AI Model Compared: Best One Per Task (2026)

•        What Is Perplexity Computer? The 2026 AI Agent Explained

References

1.   AWS Kiro AI IDE Official Page

2.   Amazon Bedrock Documentation

3. https://docs.amplify.aws

4.   AWS MCP Server (GitHub)

5. McKinsey: The State of AI 2025

6.   Deloitte AI Survey 2025

7.   AWS Bedrock Agent Core Announcement

8. Build Fast with AI Workshop Recording

Pick a side. That's what Tyler posted on X last week, dropping logos of Anthropic's Claude Code and OpenAI's Codex side by side. The replies blew up. Developers picked teams, shared workflows, debated benchmarks, and posted advanced tips that most people had never seen. I spent the week going through every thread, running both tools, and digging into the actual numbers. Here's what I found.

This isn't another surface-level comparison. Both tools have matured significantly in 2026. Claude Code hit a $2.5 billion annualized run rate with 135,000 GitHub commits per day flowing through it. OpenAI's Codex launched its macOS desktop app in February 2026 and now runs on GPT-5.3-Codex. The gap that existed six months ago has closed considerably, and the debate has gotten genuinely interesting.

I'll cover benchmarks, pricing, power-user workflows, and the honest truth about when each tool actually wins. No marketing. No hype. Just what developers are actually saying.

What Are Claude Code and Codex, Really?

Both tools are agentic coding agents, not autocomplete tools. You describe a task in plain language, the agent plans an approach, writes code across multiple files, runs your tests, and iterates until the task passes. That's where the similarity ends.

Claude Code is Anthropic's terminal-first coding agent, launched in May 2025 and powered by Claude Opus 4.6 and Sonnet 4.6. It runs locally by default, integrates deeply with your terminal and IDE, and ships with a rich configuration system built around CLAUDE.md files, custom slash commands, sub-agents, and hooks. Anthropic has since expanded it to VS Code, JetBrains, the Claude desktop app, Slack, and a web interface. As of early 2026, it runs across more surfaces than most developers realize.

OpenAI's Codex in 2026 is completely different from the original 2021 version that was deprecated in March 2023. The new Codex is a full autonomous software engineering agent powered by GPT-5.3-Codex. It runs across a cloud web agent at chatgpt.com/codex, an open-source CLI built in Rust and TypeScript, IDE extensions for VS Code and Cursor, and a macOS desktop app. The CLI has over 59,000 GitHub stars and hundreds of releases as of early 2026. Codex is cloud-first by default and leans into async, delegated workflows.

The framing most developers inherited is wrong: Claude Code is the local tool, Codex is the cloud tool. That was already incomplete before 2026. Both now operate across multiple surfaces. The real difference is the workflow philosophy. Claude Code keeps you in the loop while the task runs. Codex is designed for you to define a task, hand it off, and review the branch later.

Benchmark Reality Check: The Numbers That Actually Matter

OpenAI warned developers in early 2026 that SWE-bench Verified is becoming unreliable due to contamination concerns and recommended SWE-bench Pro instead. With that caveat in mind, here's where things actually stand:

The 23-point gap on SWE-bench Verified is significant. It reflects Claude's superior ability to understand complex codebases and make changes that solve problems without introducing new bugs. On real-world bug-fixing tasks across large repositories, that gap matters.

But Codex leads on Terminal-Bench 2.0 at 77.3% versus Claude's 65.4%. Terminal-Bench measures terminal-based debugging specifically, and GPT-5.3-Codex was optimized for exactly that kind of structured, multi-step reasoning. Developers on Reddit and Hacker News describe Codex as catching logical errors, race conditions, and edge cases that Claude misses on those specific task types.

My take: Claude wins on codebase understanding and complex refactoring. Codex wins on terminal debugging tasks and token cost. If your work is mostly fixing bugs in well-scoped issues, Codex is legitimately competitive. If you're doing architectural work across a large repo, Claude is the better choice right now.

Pricing Breakdown: What You Actually Pay

Pricing in this space changes fast, but here's the state of things as of March 2026:

The listed prices look similar, but the practical cost difference is wider than they suggest. Because Claude Code's reasoning is token-intensive, heavy daily users frequently hit limits on the $20 Pro plan and find the Max tier at $100-200/month is what they actually need for sustained work. Codex tends to use roughly 3x fewer tokens for equivalent tasks, which means the Plus tier stretches further.

For API users building products on top of these tools, the token efficiency gap translates directly to infrastructure costs. Codex is meaningfully cheaper at scale. That math changes what's buildable for startups watching LLM API spend.

That said, Claude Code's Max plan at $200/month includes access to Opus 4.6 with high effort settings, which is where you get that 80.8% SWE-bench performance. You're paying for quality. The question is whether your workflow justifies it.

Claude Code's Secret Weapons: CLAUDE.md and Parallel Agents

This is where Claude Code genuinely pulls ahead for developers who invest in the setup. The configuration system is unlike anything Codex offers.

CLAUDE.md: Persistent Project Intelligence

CLAUDE.md is a Markdown file in your project root that Claude reads at the start of every session. It acts as a persistent project brief: your coding conventions, architecture decisions, key commands, patterns to follow, and anti-patterns to avoid. Claude reads it before acting, which means it writes new code that matches your style rather than imposing its own.

The files can be hierarchical. You can have one project-level CLAUDE.md and individual ones in subdirectories, and Claude prioritizes the most specific one when working in that context. You can also save personal preferences to global memory that applies across all projects, or local memory that's project-specific and git-ignored.

Best practice: keep CLAUDE.md under 200 lines. Move detailed instructions into skills, which only load when invoked. Use @file imports for large reference docs instead of pasting content. The goal is a tight, fast-loading context that gives Claude what it needs without bloating every message.

Slash Commands and Sub-Agents

Custom slash commands let you define reusable workflows as Markdown files. Create a .claude/commands/deploy.md and /deploy becomes a command that runs your entire deployment procedure. Use $ARGUMENTS to pass parameters. Teams share these via the .claude/ directory committed to git.

Sub-agents are specialized AI instances Claude can delegate to. You define them at .claude/agents/ with their own system prompts, tool restrictions, and model choices. A code-reviewer agent that runs automatically after changes. A security-audit agent with read-only permissions. A test-writer that specializes in your testing framework. These run in parallel and their verbose output stays in their own context, keeping the main session clean.

The /batch command runs changes across many files in parallel. The --worktree flag creates an isolated git worktree for each task, so parallel sessions don't interfere. This is where Claude Code starts feeling like AI-native development rather than AI-assisted development.

Codex's Strengths: Speed, Cost, and Open Source

Codex wins on three things developers care about: raw speed, token cost, and transparency. If Claude Code is the meticulous senior developer who understands your whole codebase, Codex is the fast contractor who ships working code quickly and lets you review the diff.

The open-source CLI is a genuine differentiator. Codex CLI is fully published on GitHub under an open license. Developers can inspect exactly what it does, modify it, and build on top of it. Claude Code is closed source. For teams with security or compliance requirements who want full transparency into their tooling, this matters.

Codex's GitHub integration is considered best-in-class. Several developers on X described the pull request workflow as their favorite feature: define a task, Codex runs in an isolated cloud container with your repository preloaded, produces a branch with a clean diff, and you review it as a PR. For teams running parallel workstreams across a backlog of discrete tasks, this async model is genuinely faster than Claude's interactive approach.

Ben Holmes, whose workflow breakdown got significant traction on X, described Codex as doing rigorous self-checking code while praising Claude for clearer plans and better conversations. That framing stuck because it's accurate: Codex is stronger at structured, well-scoped tasks. Claude is stronger at the exploratory, architectural work where you don't fully know what you want until you're doing it.

Advanced Developer Workflows Shared on X

The X thread that kicked off this debate surfaced power-user tips that aren't in any documentation. Here are the ones that showed up repeatedly from verified developers:

Parallel sessions via --worktree: Run claude --worktree feature-auth to create an isolated git worktree and start a session in it. Run multiple Claude Code instances in parallel on different features without branch-switching conflicts. Some developers run 4-6 parallel sessions simultaneously on a single codebase. Each worktree is automatically cleaned up if no changes are made.

/init for new projects: Running /init in a new repository generates a CLAUDE.md file that describes your project structure and confirms your current configuration. This is the fastest way to onboard Claude to an existing codebase. Several developers noted that /init on a repo with poor documentation produced better project descriptions than the team's actual README.

Custom sub-agents as a code review layer: The emerging workflow that got the most discussion: use Claude Code to generate features, then define a Codex-style reviewer sub-agent that runs before any PR merge. Some developers are literally calling the Codex API from within a Claude Code sub-agent. There's even a community-built 'Codex Skill' for Claude Code that lets you prompt Codex directly from a Claude session.

/compact and /clear discipline: Heavy users are obsessive about context hygiene. /compact replaces conversation history with a compressed summary when context usage exceeds 80%. /clear wipes it entirely when switching to a completely different task. The practical difference: /compact when you want Claude to remember the thread, /clear when you want a fresh start. Running out of context mid-task without compacting is the most common reason for degraded output quality.

HANDOFF.md for complex multi-session tasks: For tasks that take longer than a single context window, power users create a HANDOFF.md file that captures current state: what's been tried, what worked, what didn't, and what the next agent needs to pick up. A fresh Claude session with nothing but the HANDOFF.md path produces better results than trying to compress an entire long session.

Hooks for automated workflows: Hooks fire before and after specific Claude Code events. Developers use them to automatically run Prettier after file modifications, validate inputs before allowing edits, send Slack notifications when Claude needs input, and trigger CI checks after commits. One developer described a hook setup that runs a full type-check after every file edit, meaning Claude only accepts changes that pass TypeScript compilation.

The Hybrid Workflow: Why Power Users Use Both

The binary framing of the X debate is somewhat misleading. The developers with the most sophisticated setups are using both tools. The split that emerged from the thread discussions:

Claude Code for architecture, planning, and complex multi-file changes. Codex for debugging, code review, and long autonomous runs on well-scoped tickets. The two tools complement each other rather than substitute. Claude's deep codebase understanding and interactive collaboration is best for work where you need to steer the task mid-flight. Codex's async cloud execution and lower token burn is best for defined tasks you can hand off and review later.

An increasingly common pattern: write features with Claude Code, submit to Codex for review before merging. One developer described Codex as catching race conditions and edge cases that Claude missed on 3 out of 5 complex TypeScript tasks. That's not a condemnation of Claude; it's a recognition that having a second specialized pass catches different classes of errors.

The AI code tools market is projected to reach $91 billion by 2035, growing at 27.6% annually from $7.9 billion in 2025. That's large enough for multiple winners. The ecosystem is already treating these as complementary rather than competing, and the tooling is following: community-built Claude Code skills that call Codex directly, shared agent configurations that use both APIs, and team workflows that formalize which tool handles which task type.

Which Tool Should You Choose?

Based on actual benchmark data, pricing, and developer feedback from the X thread, here's the honest answer:

For most web development and complex engineering work, Claude Code is the stronger default in 2026. The 80.8% SWE-bench Verified score isn't just a marketing number; it reflects real capability on the kinds of tasks that slow teams down. But Codex has earned its place for specific workflows, and the token cost advantage is real money at scale.

My recommendation: start with Claude Code on the Max plan for a month. Build your CLAUDE.md files and custom commands. If you find yourself running lots of parallel isolated tasks where you just want to review diffs, add Codex to your workflow for those cases. The two-tool setup adds overhead, but for active teams shipping multiple features in parallel, it pays for itself quickly

Want to build AI-powered apps and autonomous coding agents like these?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured program to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is the difference between Claude Code and OpenAI Codex?

Claude Code is Anthropic's terminal-first coding agent powered by Claude Opus 4.6, focused on interactive deep-reasoning development with persistent project context via CLAUDE.md files. OpenAI Codex is a cloud-first autonomous agent powered by GPT-5.3-Codex, designed for async task delegation with a multi-surface interface including a CLI, web agent, and macOS desktop app. Claude Code scores 80.8% on SWE-bench Verified; Codex scores 64.7%.

Which is better for complex coding tasks, Claude Code or Codex?

Claude Code outperforms Codex on complex multi-file refactoring and codebase understanding tasks. It scores 80.8% on SWE-bench Verified compared to Codex's 64.7%. Codex leads on Terminal-Bench 2.0 at 77.3% versus Claude's 65.4%, making it the stronger choice for structured terminal debugging and well-scoped ticket-based work.

Is Claude Code or Codex cheaper to use?

Both start at approximately $20/month. In practice, Codex uses roughly 3x fewer tokens per task, making it meaningfully cheaper at scale. Claude Code's reasoning is token-intensive, and heavy users often find the $100-200/month Max plan is needed for sustained daily work. For API users building products on these tools, Codex's token efficiency translates to significantly lower infrastructure costs.

What is CLAUDE.md and why do developers use it?

CLAUDE.md is a Markdown file placed in your project root that Claude Code reads at the start of every session. It functions as a persistent project brief: coding conventions, architectural patterns, key commands, and rules Claude should follow. This prevents Claude from scanning the codebase to figure out your stack and style on every session. Developers keep it under 200 lines and use it alongside custom slash commands and sub-agents to create repeatable, consistent coding workflows.

Can you use Claude Code and Codex together?

Yes, and many power users do. The emerging hybrid workflow uses Claude Code for feature generation and complex architectural work, then runs Codex as a reviewer before PR merges. There is even a community-built Claude Code skill (Codex Skill by klaudworks) that lets you call Codex directly from a Claude Code session. Several developers on X described Codex catching race conditions and edge cases that Claude missed on complex TypeScript tasks.

Does Claude Code or Codex have better GitHub integration?

Both tools integrate with GitHub. Claude Code's /install-github-app command sets up the Claude GitHub App for pull request workflows. Codex is widely praised for its GitHub integration, with cloud-based tasks running in isolated containers with your repository preloaded, producing clean branches and reviewable diffs. Developers frequently cite Codex's PR workflow as its strongest feature for team-based async development.

What are the best slash commands to learn in Claude Code?

The most impactful Claude Code slash commands are /init (generates CLAUDE.md for a new project), /compact (compresses conversation history when context usage exceeds 80%), /clear (resets context entirely between unrelated tasks), /plan (enables plan mode before executing changes), /cost (shows token spend for the current session), and /batch (runs parallel changes across many files). Custom slash commands created in .claude/commands/ let teams build repeatable workflows like /deploy and /security-review.

Is Codex CLI open source?

Yes. The Codex CLI is fully open source, published on GitHub, and has over 59,000 stars as of early 2026. It is built in Rust and TypeScript. This transparency lets developers inspect exactly how it works, modify it for their needs, and build tooling on top of it. Claude Code is closed source, though Anthropic maintains detailed documentation and has been responsive to feature requests from the developer community.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1. Is Claude Code Review Worth $15-25 Per PR? (2026 Verdict)

2. 7 AI Tools That Changed Developer Workflow (March 2026)

3. Kimi K2.5 Review: Is It Better Than Claude for Coding? (2026)

4. What Is Claude Cowork? The 2026 Guide You Need

References

1. Claude Code vs Codex CLI 2026 Comparison - NxCode (March 2026) - nxcode.io

2. Codex vs Claude Code: AI Coding Assistants Compared - DataCamp (Feb 2026) - datacamp.com

3. Claude Code vs OpenAI Codex - PinkLime (Feb 2026) - pinklime.io

4. Claude vs Codex: Comparison of AI Coding Agents - WaveSpeedAI (Jan 2026) - wavespeed.ai

5. OpenAI Codex Plugins Target Enterprises, Not Developers - Implicator AI (Mar 2026) - implicator.ai

6. Claude Code vs Codex in 2026: Steer Live or Delegate Async - LaoZhang AI (Mar 2026) - blog.laozhang.ai

7. Codex vs Claude Code: 2026 Comparison for Developers - Leanware (Feb 2026) - leanware.co

8. How to Use Claude Code: Skills, Agents, Slash Commands - ProductTalk (Feb 2026) - producttalk.org

9. Extend Claude with Skills - Claude Code Official Documentation - code.claude.com

Comments Section

In 2023, Chinese AI labs were dismissed as fast followers. In 2024, they were called credible. In 2025, they started winning benchmarks. In March 2026, ByteDance just took the number one spot on the world's most-watched AI video leaderboard and Z.ai (formerly Zhipu AI) released a coding model that sits at 94.6% of Claude Opus 4.6's score. Both dropped within 48 hours of each other.

I've been tracking AI video generation closely for the past year, and what happened this week is not a gradual trend. It's a step change. Seedance 2.0 from ByteDance hit Elo 1,269 on Artificial Analysis, beating Google Veo 3, OpenAI Sora 2, and Runway Gen-4.5. GLM-5.1 from Z.ai scored 45.3 on coding evals versus Claude Opus 4.6's 47.9. These numbers are not from labs you can dismiss.

This post breaks down what Seedance 2.0 actually does, why the benchmark numbers matter (and where to be skeptical), how it compares to the best globally available alternatives, and what the GLM-5.1 coding leap means for developers who are watching China's AI progress with one eye.

What Is Seedance 2.0?

Seedance 2.0 is ByteDance's latest AI video generation model, officially launched in March 2026. It uses a unified multimodal audio-video architecture, supporting text, images, audio, and video as inputs simultaneously, and generates clips up to 15 seconds at up to 1080p resolution.

The architecture is the part I find genuinely interesting. Most video generators work like this: you write a prompt, the model generates a clip, you decide if you like it. Seedance 2.0 is designed more like a director's workspace. You can feed up to 9 reference images, 3 video clips, and 3 audio clips alongside your text prompt in a single generation pass. That multi-reference control is unique at this level of quality.

ByteDance describes its core advancement as 'director-level control.' That means you're not just describing a scene, you're specifying camera movement, lighting, shadow behavior, character motion, and audio cues. The model reasons across all of those inputs at once rather than treating them as post-generation corrections.

The other meaningful upgrade over Seedance 1.0 is native audio-video joint generation. Audio is not layered in after the fact. It's synthesized alongside the video in the same pass, which is why users are reporting naturally synced dialogue, ambient sound, and music in generated clips without any additional editing.

Seedance 2.0 Benchmark Numbers: What the Elo Score Actually Means

Seedance 2.0 currently leads the Artificial Analysis video leaderboard with an Elo score of 1,269 for text-to-video and 1,351 for image-to-video (without audio). These are not self-reported numbers. Artificial Analysis uses blind user voting, where people compare two video outputs side by side without knowing which model made which, then pick their preference. The Elo system updates based on the win-loss record.

That methodology matters because it captures real human preference, not just checklist scoring. A model can ace a controlled benchmark but lose blind human preference tests because it looks sterile or lifeless. Seedance 2.0 winning here suggests real perceptual quality, not just technical metric performance.

The honest caveat: Seedance 2.0's Elo lead may not hold once more votes come in. New models always start with smaller sample sizes, so their Elo scores are more volatile. Kling 3.0 at Elo 1,248 is more stable because it has been ranked for longer. I'd treat the current Seedance lead as 'likely best' rather than 'definitively best' until rankings stabilize in April.

Seedance 2.0 vs Competitors: Kling 3.0, Veo 3, Sora 2, Runway Gen-4.5

Benchmarks tell part of the story. Here is where each model actually stands in real-world use.

Seedance 2.0 vs Kling 3.0

Seedance 2.0 scores higher on the Artificial Analysis leaderboard right now, but Kling 3.0 from Kuaishou has something Seedance doesn't: a globally available API today. Kling 3.0 generates native 4K at 60fps, priced at $0.075/second, with stable production access. If you're building something now, Kling 3.0 is the practical choice. If you're evaluating what to migrate to in Q3 2026, Seedance 2.0 is worth tracking.

Seedance 2.0 vs Google Veo 3

Veo 3 has the best native audio-video synchronization among all publicly available models. Its Elo 1,226 in text-to-video puts it solidly in the top five, but Seedance 2.0 beats it on both T2V and I2V in the no-audio category. Where Veo 3 still wins: it's available now through Vertex AI and Google's consumer products, while Seedance 2.0's global API launch is months away.

Seedance 2.0 vs Runway Gen-4.5

Runway Gen-4.5 held the Elo top spot when it launched in December 2025, then got surpassed by Kling 3.0 and Seedance 2.0 in March 2026. That is not a knock on Runway. The field advanced around it. Runway's advantage remains its ecosystem: motion brush controls, multi-shot workflow tools, scene consistency features, and API maturity that no competitor matches for professional post-production. Seedance 2.0 scores higher on raw generation quality. Runway remains the better choice if you need editing capabilities alongside generation.

Seedance 2.0 vs Sora 2

Sora 2 is not yet part of the Artificial Analysis arena ranking dataset as of March 2026. I cannot give you a direct Elo comparison. From community demos, Sora 2 excels at cinematic long-form coherence but remains expensive and access-restricted. The honest answer is: wait for Sora 2 to enter the arena rankings before drawing conclusions.

Key Features That Set Seedance 2.0 Apart

Three specific capabilities matter here, and I want to be precise about each one rather than listing marketing points.

•       Multi-reference input stack: 9 images, 3 videos, 3 audio clips simultaneously. No other production model supports this range of reference inputs in a single generation pass. This is the feature that makes Seedance 2.0 useful for narrative content, not just isolated clips.

•       Video editing and extension: Seedance 2.0 lets you make targeted changes to specific scenes, characters, or actions in a generated clip, and extend it with follow-on shots. This reduces the 'start over from scratch' problem that plagues most video generation workflows.

•       Native audio synthesis: Music, dialogue, and sound effects are generated in the same pass as the video. Lip-sync accuracy is strong on single subjects, though ByteDance acknowledges multi-person lip-sync still needs improvement.

One thing I want to flag that the marketing materials underplay: detail stability in fast-motion scenes is still a known weakness. ByteDance's own documentation notes this. If your use case involves high-speed action, falling objects, or rapid camera movement, test carefully before committing.

Seedance 2.0 Access: CapCut, Dreamina, and What Is Still Missing

Seedance 2.0 is available now through two ByteDance platforms: Dreamina (dreamina.capcut.com) for web-based generation and CapCut on desktop and mobile. ByteDance rolled out access starting March 24, 2026, initially to paid users in Indonesia and Brazil, then expanded globally as a free limited-time perk in CapCut.

The global API launch is expected in Q2 2026, according to multiple sources tracking the rollout. Until then, developers cannot integrate Seedance 2.0 into production pipelines. CapCut has over 800 million users globally, so the consumer distribution is enormous, but the developer access gap is a real limitation right now.

My honest take: if you're a creator, try it now in CapCut or Dreamina. The free trial access is a genuine opportunity to form your own opinion about quality before everyone else catches up. If you're a developer building video features, continue with Kling 3.0 or Runway Gen-4.5 until the Seedance 2.0 API drops.

GLM-5.1 vs GLM-5: The Coding Leap You Should Not Ignore

While Seedance 2.0 dominated the visual AI news cycle, Z.ai (formerly Zhipu AI) quietly dropped GLM-5.1 on March 27, 2026, and the benchmark numbers are worth taking seriously.

GLM-5.1 scored 45.3 on Z.ai's coding evaluation, compared to Claude Opus 4.6's score of 47.9 on the same benchmark harness. That's a gap of 2.6 points. The predecessor, GLM-5, scored 35.4. In other words, a single-point update delivered a 28% improvement in coding performance in just over one month from GLM-5's February 11 release.

There's a caveat I need to flag clearly: the GLM-5.1 coding scores use Claude Code as the evaluation harness, which naturally advantages Anthropic models. For GLM-5.1 to reach 94.6% of Claude Opus 4.6 in an environment tuned for Claude is a meaningful result. But these are Z.ai's own numbers, not independently verified as of this writing. GLM-5's 77.8% on SWE-bench Verified was externally confirmed, so Z.ai has a track record, but wait for independent replication before fully committing your workflow.

The pricing contrast is the other half of this story. GLM Coding Plan starts at $3/month for 120 prompts (promotional), with the API at $1.00/M input tokens and $3.20/M output tokens. Compare that to Claude's pricing and the cost gap is substantial. GLM-5.1 is also built entirely on Huawei Ascend 910B chips, with zero Nvidia hardware, making it the most prominent example of China building frontier-class AI outside the CUDA ecosystem.

One practical weakness: GLM-5.1 runs at 44.3 tokens per second, which is slower than competing frontier models. For long agentic tasks where you're not waiting at your screen, that's fine. For interactive coding loops where you want fast iteration, it's noticeable.

What This Week's Releases Mean for AI Developers

Two things happened this week that I think are underreacted to in Western AI coverage.

First, the video generation market now has a clear best-in-class benchmark leader that runs on a platform with 800 million existing users. That is a distribution advantage no Western AI video startup can match. TikTok and Douyin alone give ByteDance a feedback loop for Seedance 2.0 that other video AI labs cannot replicate. More usage means more human preference data, which means faster Elo-informed iteration. The compounding effect here is real.

Second, GLM-5.1 scoring 94.6% of Claude Opus 4.6 in coding while being priced at a fraction of the cost and built on non-Nvidia hardware is the clearest data point yet that the assumption 'frontier AI requires Western infrastructure and Western labs' is no longer solid. It may still be true at the absolute frontier. But 94.6% of frontier performance at 6% of the price is a different calculus for most production workloads.

What I would actually do with this information: test Seedance 2.0 in CapCut this week while access is free. Try GLM-5.1 via the Coding Plan if you're a developer spending more than $30/month on coding AI. Form your own benchmarks on your own tasks before making workflow decisions based on anyone else's numbers, including mine.

Frequently Asked Questions

What is Seedance 2.0 and who made it?

Seedance 2.0 is ByteDance's AI video generation model, officially launched in March 2026. It uses a unified multimodal architecture that accepts text, image, audio, and video inputs, and generates videos up to 15 seconds long at 1080p resolution. It is available through ByteDance's Dreamina and CapCut platforms.

What is Seedance 2.0's Elo score on Artificial Analysis?

As of March 2026, Seedance 2.0 holds an Elo score of 1,269 for text-to-video (no audio) and 1,351 for image-to-video (no audio) on the Artificial Analysis Video Arena leaderboard. Both scores place it first in their respective categories, ahead of Kling 3.0, Google Veo 3, and Runway Gen-4.5.

How does Seedance 2.0 compare to Kling 3.0?

Seedance 2.0 scores higher on the Artificial Analysis leaderboard (Elo 1,269 vs 1,248), but Kling 3.0 from Kuaishou is currently the better choice for developers who need a globally available API today. Kling 3.0 supports native 4K at 60fps, priced at $0.075/second, while Seedance 2.0's global API is not expected until Q2 2026.

Is Seedance 2.0 free to use?

Seedance 2.0 is available as a free limited-time perk in CapCut apps globally as of March 2026. Web access is available through Dreamina (dreamina.capcut.com). Paid plans with higher usage limits are available. A developer API is not yet publicly available and is expected in Q2 2026.

What is GLM-5.1 and how does it compare to Claude Opus 4.6 for coding?

GLM-5.1 is Z.ai's (formerly Zhipu AI's) latest coding-focused model, released March 27, 2026. It scored 45.3 on Z.ai's internal coding evaluation, compared to Claude Opus 4.6's score of 47.9 on the same benchmark harness, representing 94.6% of Claude Opus performance. These figures are self-reported by Z.ai and have not been independently verified as of March 2026.

How much does GLM-5.1 cost compared to Claude?

The GLM Coding Plan starts at $3/month (promotional price) for 120 prompts, with a standard price beginning at $10/month. The GLM-5 API is priced at $1.00 per million input tokens and $3.20 per million output tokens. This positions GLM-5.1 significantly below Claude Opus 4.6 pricing, which starts at $15 per million input tokens.

Is GLM-5.1 open source?

GLM-5.1 is not yet open source as of its March 27, 2026 release, but Z.ai has signaled an open-source release is coming. The predecessor GLM-5 is available on Hugging Face under the MIT License. The GLM-4.7 model is also publicly available on Hugging Face and ModelScope, so Z.ai has a consistent track record of open-sourcing its models.

What AI hardware does GLM-5.1 run on?

GLM-5.1 inherits the GLM-5 architecture, which was trained entirely on 100,000 Huawei Ascend 910B chips with zero Nvidia hardware. This makes GLM-5 and GLM-5.1 the most prominent demonstration of frontier-class AI development outside the Nvidia CUDA ecosystem.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

- GLM-5.1 Review: Can It Beat Claude Opus 4.6? (2026)

- GLM OCR vs GLM-5-Turbo: Which AI Model Should You Use? (2026)

- Every AI Model Compared: Best One Per Task (2026)

- Kimi 2.5 Review: Is It Better Than Claude for Coding? (2026)

- 7 AI Tools That Changed Developer Workflow (March 2026)

References

1. Seedance 2.0 Official Page - ByteDance Seed

2. Artificial Analysis Image-to-Video Leaderboard (March 2026)

3. GLM-5: From Vibe Coding to Agentic Engineering - arXiv:2602.15763

4. GLM-5.1 Review: Can It Beat Claude Opus 4.6? - Build Fast with AI

5. Seedance 2.0: A Comprehensive Analysis - Viblo Asia

6. GLM-5.1 Coding Plan: Claude Opus Alternative - Apiyi.com

7. ByteDance's Gemini 3.0 Moment: Seedance 2.0 and Seed2.0 - Recode China AI

8. Best AI Models for Video Generation - March 2026 - Awesome Agents

9. Zhipu GLM-5.1: 94% of Claude Opus 4.6 Coding Performance - Digital Applied

Comments Section

In 2023, open-source AI was two years behind frontier models. In 2024, one year. In 2025, six months. And on March 27, 2026, Z.ai dropped GLM-5.1 with a coding score of 45.3 on their internal eval - while Claude Opus 4.6 sits at 47.9. That gap is 2.6 points. I am not cherry-picking optimistic numbers. That's the headline.

GLM-5.1 is now live for all GLM Coding Plan users, trained entirely on Huawei Ascend 910B chips (zero Nvidia involvement), and Z.ai is already teasing an open-source release. If those benchmark numbers survive independent scrutiny, this is the most serious challenge any open model has posed to Anthropic's flagship coding model.

But here is what the benchmark tables won't tell you: GLM-5.1 is the slowest model in this comparison at 44.3 tokens per second, it shines hardest on long agentic tasks rather than quick code generation, and the open-source release is still just a tease. I want to walk you through exactly what this model does, where it leads, where it lags, and whether you should switch your coding workflow to it today.

What Is GLM-5.1?

GLM-5.1 is an incremental post-training upgrade to Z.ai's GLM-5 foundation model, released on March 27, 2026, specifically targeting coding performance. It does not change the base architecture - it is the same 744 billion total parameter Mixture-of-Experts model with 40 billion active parameters per inference token, a 200K context window, and DeepSeek Sparse Attention under the hood.

Z.ai (the international brand for Zhipu AI, China's third-largest AI lab by IDC's count) has been moving fast. The release cadence in 2026 alone reads like this: GLM-5 on February 11, GLM-5-Turbo on March 15, and GLM-5.1 on March 27. That's three significant releases in six weeks. The Chinese AI market is brutally competitive, and Zhipu is not letting up.

What makes .1 different from .0? Refined post-training. The base architecture is unchanged, but the reinforcement learning pipeline was retargeted specifically at coding task distributions. The result: GLM-5.1 scores 45.3 on Z.ai's coding eval versus the GLM-5 baseline of 35.4. That is a 28% improvement. In one point release. For context, Claude Opus 4.6 scores 47.9 on the same benchmark.

I think the 'point release delivers 28% uplift' story is actually more interesting than the 'we're close to Claude' story. It tells you that post-training quality, not parameter count, is the lever Z.ai is pulling right now.

How GLM-5.1 Performs on Coding Benchmarks

GLM-5.1 scores 45.3 on Z.ai's proprietary coding evaluation benchmark, placing it 94.6% of the way to Claude Opus 4.6's score of 47.9 on the same harness. The eval uses Claude Code as the harness, which introduces a notable caveat: these benchmarks are self-reported by Z.ai and have not yet been independently verified as of March 28, 2026.

That caveat matters. A lot. I have seen several Chinese labs report impressive self-benchmarked numbers that look less exciting once independent testing happens. That said, GLM-5 (the base model) already demonstrated 77.8% on SWE-bench Verified when measured externally - the highest score among all open-source models on that benchmark. So Z.ai has a track record of backing up their internal numbers.

Here is a quick look at where GLM-5 (the base for GLM-5.1) sits on established external benchmarks:

(Note: GLM-5.1 coding benchmark score is internal/self-reported. External benchmark data above reflects GLM-5 base model per Artificial Analysis and arXiv technical report.)

The BrowseComp number is the one I keep coming back to. GLM-5 scores 62.0 versus Claude Opus 4.5's 37.0 on that benchmark. That's not a gap you can explain away. Something real is happening with Z.ai's web-browsing and research capabilities.

Agent Leaderboard: Where GLM-5.1 Shines

GLM-5.1 achieves an 85.0 average score across agent leaderboards, making it among the top open-source models for long-horizon agentic tasks. Its standout capability is synthesizing long research reports - the example Z.ai highlights is autonomous synthesis of dexterous hands research documentation, a task that requires sustained multi-step reasoning over hours of compute time.

GLM-5 was already ranked #1 among open-source models on Vending Bench 2 - a benchmark that simulates running a vending machine business over a one-year horizon. The model finished with a final account balance of $4,432, approaching Claude Opus 4.5's performance. GLM-5.1 builds on this agentic foundation.

The architecture is genuinely built for this. The 'slime' asynchronous RL infrastructure means GLM-5.1 can handle long-trajectory tasks without the synchronization bottlenecks that hamper other large models. It was also trained on long-horizon agentic data specifically during mid-training, not just fine-tuned at the end.

My honest take: if your use case is short, quick code completions in a Cursor-style autocomplete setup, GLM-5.1 may not be your best option. Where it gets interesting is multi-file refactoring, backend architecture tasks, or anything that requires a model to hold context and plan across dozens of steps. That's where the 85.0 agent score actually means something in practice.

Speed, Pricing, and the Practical Tradeoffs

GLM-5.1 is the slowest model in its competitive tier at 44.3 tokens per second - which is a real limitation if you're doing real-time coding in an IDE. For context, GLM-5 Reasoning mode on Artificial Analysis generates at 69.4 tokens per second. The 5.1 variant with its additional post-training is slower.

Pricing for the GLM Coding Plan starts at $27 per quarter (roughly $9/month), with a promotional entry point of $3/month for 120 prompts. The standalone GLM-5 API costs $1.00 per million input tokens and $3.20 per million output tokens - which is approximately 6x cheaper on input and 10x cheaper on output than Claude Opus 4.6's pricing of $5/$25 per million tokens.

Here is the tradeoff summary you actually need:

•       Speed: 44.3 tokens/sec (slowest in class). Not ideal for autocomplete.

•       Price: $27/quarter for plan access. Dramatically cheaper than Opus 4.6 API pricing.

•       Context: 200K tokens, 131,072 max output. Excellent for long tasks.

•       Open-source: Teased but not yet released as of March 28, 2026.

•       Compatibility: Works with Claude Code, Cursor, Cline, Kilo Code, OpenCode, and more.

The speed issue is the one I'd push Z.ai on. 44.3 tokens per second on a model positioned as a coding assistant is a friction point. Developers will notice it. That said, for batch tasks or agentic workflows where you're not watching tokens stream in real time, it matters far less.

GLM-5.1 vs Claude Opus 4.6: Side-by-Side Comparison

Coding eval scores are only one slice of this comparison. Let me put the practical differences side by side.

The pricing gap is extraordinary. For teams running high-volume coding workflows through the API, $3.20 versus $25 per million output tokens is not a rounding error. It's the difference between a $3,000 monthly AI budget and a $30,000 one.

The text-only limitation is real though. Claude Opus 4.6 can accept image inputs, which matters for UI tasks, diagram analysis, and debugging visual output. GLM-5.1 cannot. That's a genuine capability gap, not just a benchmark number.

The Huawei Hardware Story Behind GLM-5.1

GLM-5.1 was trained entirely on 100,000 Huawei Ascend 910B chips using the MindSpore framework, with zero Nvidia GPU involvement. Zhipu AI has been on the US Entity List since January 2025, which means they cannot access US-manufactured semiconductor hardware for AI training.

This context changes how you read the benchmark numbers. Z.ai built a model within 2.6 eval points of Anthropic's best coding model, using hardware that the US government classified as less capable than Nvidia's offerings. Whether you think the Entity List is good policy or not, the technical achievement is real.

Zhipu AI also completed a Hong Kong IPO on January 8, 2026, raising approximately HKD 4.35 billion (roughly USD $558 million). That capital has directly accelerated the GLM-5 family's development pace. The one-release-per-month cadence in 2026 is not a coincidence.

I think the deeper story here is that the assumption 'you need Nvidia to build frontier AI' is increasingly wrong. GLM-5 scored 50 on the Artificial Analysis Intelligence Index - the first open-weight model to hit that threshold. It was done on Huawei chips. That's a geopolitically significant data point.

Should You Use GLM-5.1 Right Now?

GLM-5.1 is worth using if you run long-horizon coding tasks, want 10x cheaper API costs than Claude Opus 4.6, and can tolerate 44.3 tokens per second. It's not the right choice if you need fast autocomplete, multimodal input, or fully verified independent benchmark scores.

Here's how I'd break down who should actually switch:

•       Use GLM-5.1 if: You're running backend refactoring, multi-file architecture tasks, or long research synthesis. The 85.0 agent average and 200K context window are genuinely useful here.

•       Use GLM-5.1 if: You're cost-sensitive. At $27/quarter for the coding plan, this is dramatically cheaper than comparable Claude API access.

•       Wait on GLM-5.1 if: You need independent benchmark verification before committing workflow changes. Self-reported scores are a starting point, not a guarantee.

•       Wait on GLM-5.1 if: Speed matters for your use case. 44.3 tokens per second will feel slow in an interactive coding context.

The open-source release is the thing I'm most interested in. Z.ai has a consistent track record of open-sourcing GLM models (GLM-4.7 is already on Hugging Face under MIT). When GLM-5.1 weights drop, the conversation about running frontier-adjacent coding AI locally changes significantly. I'll be watching for that announcement.

Want to build AI agents and coding tools like these from scratch?  Join Build Fast with AI's Gen AI Launchpad, an 8-week structured program to go from 0 to 1 in Generative AI.  Register here:

buildfastwithai.com/genai-course

Frequently Asked Questions

What is GLM-5.1?

GLM-5.1 is Z.ai's (Zhipu AI's) latest coding-focused AI model, released on March 27, 2026. It is a post-training upgrade to GLM-5, built on the same 744 billion parameter Mixture-of-Experts architecture with 40 billion active parameters per token and a 200K context window. The upgrade targets coding benchmark performance specifically.

How does GLM-5.1 compare to Claude Opus 4.6 in coding benchmarks?

GLM-5.1 scores 45.3 on Z.ai's internal coding evaluation benchmark, compared to Claude Opus 4.6's score of 47.9 on the same harness. That puts GLM-5.1 at 94.6% of Claude Opus 4.6's performance. These benchmarks are self-reported by Z.ai and had not been independently verified as of March 28, 2026.

What is the GLM Coding Plan pricing?

The GLM Coding Plan starts at a promotional price of $3/month for 120 prompts, with the full plan at $27 per quarter. The standalone GLM-5 API is priced at $1.00 per million input tokens and $3.20 per million output tokens, which is roughly 6x cheaper on input and 10x cheaper on output versus Claude Opus 4.6.

How fast is GLM-5.1 in tokens per second?

GLM-5.1 generates at approximately 44.3 tokens per second, making it the slowest model in its competitive tier. For context, GLM-5 in reasoning mode generates at 69.4 tokens per second. The speed limitation is worth considering for interactive coding and autocomplete use cases.

Is GLM-5.1 open source?

As of March 28, 2026, GLM-5.1 is not yet open-source, but Z.ai has teased an open-source release. Z.ai has a consistent track record of open-sourcing its models: GLM-4.7 is available on Hugging Face under the MIT License. The GLM-5 family is expected to follow the same precedent.

What hardware was GLM-5.1 trained on?

GLM-5.1 was trained on approximately 100,000 Huawei Ascend 910B chips using the MindSpore framework, with no Nvidia GPU involvement. Zhipu AI has been on the US Entity List since January 2025, making this an independent Chinese AI compute stack.

What agent benchmarks does GLM-5.1 score on?

GLM-5.1 achieves an 85.0 average score across agent leaderboards. The GLM-5 base model scored #1 among open-source models on Vending Bench 2 (a one-year business simulation) with a final account balance of $4,432, and recorded 62.0 on BrowseComp versus Claude Opus 4.5's 37.0.

Which coding tools support GLM-5.1?

GLM-5.1 is compatible with Claude Code, Cursor, Kilo Code, Cline, OpenCode, Droid, and OpenClaw via the GLM Coding Plan. It can be accessed through the Z.ai API using an OpenAI-compatible endpoint, making integration straightforward for most developer tooling.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

Kimi 2.5 Review: Is It Better Than Claude for Coding? (2026)

GLM OCR vs GLM-5-Turbo: Which AI Model Should You Use? (2026)

Claude Code Auto Mode: Unlock Safer, Faster AI Coding (2026 Guide)

LLM Scaling Laws Explained: Will Bigger AI Models Always Win? (2026)

7 AI Tools That Changed Developer Workflow (March 2026)

References

1. GLM-5 Technical Report (arXiv:2602.15763) - Zhipu AI / Z.ai

2. GLM-5 Official Hugging Face Model Card - Z.ai

3. GLM-5.1 Benchmark Analysis - Digital Applied

4. GLM Coding Plan Pricing - Z.ai

5. GLM-5 Overview - Z.AI Developer Documentation

6. z.ai's GLM-5 Achieves Record Low Hallucination Rate - VentureBeat

7. GLM-5 Intelligence Index Analysis - Artificial Analysis

8. GLM-5 GitHub Repository - Z.ai Org

Comments section

GPT-3 was released in 2020. It could write essays, generate code, and complete almost any text prompt you gave it. But it was also wildly unpredictable. Ask it a question and it might give you a brilliant answer, a completely fabricated one, or just continue your prompt as if it were a Wikipedia article. It was powerful but not useful in the way a product needs to be.

Then in late 2022, OpenAI released ChatGPT. Same underlying architecture. Same fundamental capabilities. But ChatGPT could follow instructions, hold a conversation, refuse harmful requests, and stay on topic. It became the fastest-growing consumer application in history, reaching 100 million users in two months. The difference between GPT-3 and ChatGPT wasn't more parameters or more training data. It was RLHF, Reinforcement Learning from Human Feedback.

RLHF is the technique that transformed raw language models from impressive text predictors into the conversational AI systems that hundreds of millions of people use daily. It's the reason ChatGPT, Claude, and Gemini feel helpful rather than chaotic. And running it at the scale of frontier models is one of the most logistically complex operations in AI. Let's break down exactly how it works and what it takes to do it for real.

Why Pretraining Alone Isn't Enough

A pretrained LLM is fundamentally a next-token prediction machine. It's been trained on trillions of tokens of internet text to predict what word comes next in a sequence. This gives it vast knowledge and fluent language generation, but it creates a critical gap: the model has no concept of what a "good" response is.

Ask a pretrained model "What is the capital of France?" and it might respond with "Paris" or it might continue the sentence as if it's writing a geography quiz: "What is the capital of France? A) Paris B) Lyon C) Marseille." Both are valid text completions, but only one is what a user actually wants.

The problem gets worse with complex tasks. A pretrained model doesn't know when to be concise versus detailed. It doesn't understand that fabricating a medical diagnosis is dangerous. It doesn't grasp that a coding question expects executable code, not a discussion about programming philosophy. These are all subjective qualities that are easy for humans to judge but nearly impossible to define mathematically as a loss function.

Traditional supervised fine-tuning (SFT) helps by training the model on examples of ideal prompt-response pairs written by humans. But SFT has limits. You can only show the model what good looks like, never what bad looks like. And for many tasks, there's no single "correct" answer. A response can be helpful in many different ways, and SFT struggles to capture that nuance.

This is where RLHF enters the picture. Instead of trying to define "good" mathematically, RLHF lets humans judge model outputs directly and trains the model to produce more of what humans prefer.

How RLHF Works Step by Step

The RLHF pipeline has three distinct stages, each building on the previous one. Understanding each stage is essential for grasping both the power and the complexity of the technique.

Stage 1: Supervised Fine-Tuning (SFT). Before applying RL, the model needs a starting point that can follow instructions at a basic level. A team of human annotators writes high-quality responses to a curated set of prompts. These prompt-response pairs are used to fine-tune the pretrained model using standard supervised learning. For InstructGPT, OpenAI used roughly 13,000 human-written demonstrations for this stage. Anthropic used transformer models from 10 million to 52 billion parameters. This SFT model becomes the foundation for everything that follows.

Stage 2: Reward Model Training. This is the most distinctive part of RLHF. Instead of defining a mathematical reward function (which would be impractical for something as subjective as "helpfulness"), you train a separate neural network to predict what humans would prefer.

Here's how it works: the SFT model generates multiple responses to the same prompt. Human annotators then rank these responses from best to worst. These rankings are converted into pairwise comparisons (Response A is better than Response B) and used to train a reward model. The reward model learns to assign a scalar score to any given prompt-response pair that reflects how much humans would like it.

For InstructGPT, OpenAI used roughly 50,000 labeled preference comparisons. Each prompt had 4 to 9 candidate responses, forming between 6 and 36 pairwise comparisons per prompt, yielding 300K to 1.8M training examples. Anthropic's Constitutional AI process used 318K comparisons in total, with 135K generated by humans and 183K generated by AI.

The reward model is typically initialized from the SFT model itself. The intuition is that the reward model needs to understand language at least as well as the model it's evaluating. If the reward model is weaker than the policy model, it can't reliably score the outputs.

Stage 3: RL Fine-Tuning with PPO. This is where the actual reinforcement learning happens. The SFT model (now called the "policy") generates responses to prompts. The reward model scores each response. Then Proximal Policy Optimization (PPO), an RL algorithm, adjusts the policy to produce responses that receive higher reward scores.

There's a critical constraint: you don't want the model to change too much from its SFT starting point. Without this constraint, the model might learn to "game" the reward model by producing outputs that score high but are actually degenerate. To prevent this, RLHF adds a KL divergence penalty that penalizes the model for deviating too far from the original SFT distribution. This keeps the model from losing the general capabilities it learned during pretraining and SFT.

The PPO training loop is iterative: generate responses, score them, compute the policy gradient, update the model, repeat. Each iteration improves the model's alignment with human preferences as captured by the reward model.

The Logistics of RLHF at Scale

Running RLHF on a research model is one thing. Running it on a frontier model with hundreds of billions of parameters is a completely different engineering challenge. The logistics are staggering, and this is where most of the cost and complexity actually lives.

The four-model problem. PPO-based RLHF requires keeping four separate large models in GPU memory simultaneously: the policy model (the LLM being trained), the reference model (a frozen copy of the SFT model for computing the KL penalty), the reward model, and the critic/value model (used by PPO to estimate advantages). For a 70B parameter model, each copy requires roughly 140 GB in FP16. That's 560 GB just for model weights, before accounting for activations, optimizer states, or KV caches. This means you need distributed training across dozens or hundreds of GPUs even for a single RLHF training run.

Human annotation is the bottleneck. Every RLHF iteration requires high-quality human preference data. Generating well-written demonstration responses for SFT requires hiring skilled writers, not crowdworkers. OpenAI employed a team of about 40 contractors for InstructGPT's annotation work. At production scale, companies like Scale AI and Surge AI provide thousands of trained annotators. The cost is substantial: high-quality human annotation for RLHF runs approximately $100 per expert comparison for complex tasks, and expert annotation rates can exceed $40 per hour. For frontier models requiring hundreds of thousands of comparisons, the annotation budget alone can reach millions of dollars.

Annotator consistency is a real problem. Different humans have different preferences. One annotator might value brevity while another values detail. One might prioritize factual accuracy while another values engaging tone. This inter-annotator disagreement introduces noise into the reward model training. Production RLHF systems use multiple annotators per comparison, carefully designed annotation guidelines, and statistical aggregation methods (like Elo ratings) to manage this variance. But it remains a fundamental limitation: human judgment is noisy, and the reward model can only be as good as the data it's trained on.

Reward hacking is a constant risk. The policy model can learn to exploit weaknesses in the reward model rather than genuinely improving. For example, models might learn that longer responses score higher (because annotators sometimes equate length with thoroughness) and start padding responses with unnecessary text. Or models might learn that confident-sounding language scores well, even when the content is wrong. John Schulman (co-creator of PPO) has noted that while RLHF was supposed to help with hallucination, the InstructGPT paper showed it actually made hallucination slightly worse, because the model learned to sound more confident. Mitigating reward hacking requires careful reward model design, regularization, and iterative evaluation.

Training instability at scale. PPO is notoriously sensitive to hyperparameters, and this sensitivity amplifies at large scale. Learning rates, KL penalty coefficients, batch sizes, and clip ratios all need careful tuning. The "Secrets of RLHF in Large Language Models" paper documented advanced techniques needed to stabilize PPO training: normalizing and clipping rewards based on historical statistics, initializing the critic model from the reward model, using global gradient clipping, and adding pretrain language model loss to reduce "alignment tax" (the degradation of general capabilities during RLHF). Without these tricks, PPO training at scale frequently diverges or produces degenerate outputs.

Distributed orchestration is complex. RLHF training isn't just running one forward pass and one backward pass. Each iteration requires: generating responses from the policy (inference), scoring them with the reward model (inference), computing advantages with the critic (inference), and updating the policy and critic (training). These four operations have different compute profiles and need to be orchestrated across a GPU cluster. Frameworks like OpenRLHF (built on Ray + vLLM) and TRL (from Hugging Face) have been developed specifically to handle this orchestration, distributing the actor, critic, reward model, and reference model across separate GPU groups.

Beyond RLHF: DPO, GRPO, and RLVR

The complexity and cost of PPO-based RLHF motivated the development of simpler alternatives. The field has evolved rapidly, and the standard RLHF recipe from 2022 looks very different from what frontier labs use in 2026.

Direct Preference Optimization (DPO), introduced by Stanford researchers in 2023, eliminates the reward model entirely. Instead of training a separate reward model and then running RL, DPO reformulates the problem as a supervised classification task. It trains the model directly on preference pairs using a contrastive loss that increases the probability margin between preferred and rejected responses. DPO is simpler to implement, requires less GPU memory (no reward model or critic), and is more stable to train. SimPO, an extension, outperforms DPO by 6.4 points on AlpacaEval 2 and 7.5 points on Arena-Hard.

Group Relative Policy Optimization (GRPO), introduced by DeepSeek, has become the dominant RL algorithm for training reasoning models. GRPO's key innovation is eliminating the separate critic model that PPO requires. For each prompt, GRPO generates a group of multiple responses (typically 8-64), scores them all with a reward model, and computes advantages by comparing each response's reward against the group mean and standard deviation. This reduces memory requirements by roughly 50% compared to PPO since you no longer need a full critic model. A recent theoretical analysis showed that GRPO's policy gradient is provably optimal within a broad class of policy gradient methods, not just a practical hack. GRPO is now used in DeepSeek R1, Nemotron 3 Super, and numerous other production models.

Reinforcement Learning with Verifiable Rewards (RLVR) represents the biggest paradigm shift. Instead of relying on human preference labels or learned reward models, RLVR trains models on tasks where correctness can be automatically verified, like math problems (check the answer) and code (run unit tests). The reward signal is binary and perfect: the answer is correct or it isn't. DeepSeek R1 demonstrated that pure RLVR with GRPO, applied directly to a base model without any supervised fine-tuning, could produce emergent reasoning capabilities including self-verification and extended chain-of-thought reasoning. Because verifiable rewards are less prone to reward hacking, RLVR training can run much longer than traditional RLHF without collapsing. This is how reasoning models achieve their impressive math and coding capabilities.

The modern post-training stack in 2026 is modular. SFT teaches instruction-following format. Preference optimization (DPO/SimPO/KTO) handles alignment with human preferences. RL with verifiable rewards (GRPO/DAPO) builds reasoning capabilities. Each stage addresses a different aspect of model behavior, and the combination produces models that are helpful, safe, and capable of complex reasoning. As Sebastian Raschka summarized: LLM development in 2025-2026 was "essentially dominated by reasoning models using RLVR and GRPO."

Why RLHF Still Matters

Despite the evolution toward DPO, GRPO, and RLVR, classical RLHF hasn't disappeared. It remains essential for aligning models on open-ended tasks where there's no verifiable ground truth, things like tone, helpfulness, cultural sensitivity, and creative quality. You can't write a unit test for "was this response empathetic?"

DeepSeek R1's final training stage used both RLVR (for reasoning tasks) and traditional RLHF with neural reward models (for general helpfulness and harmlessness). They used separate reward models for each criterion: helpfulness was scored based only on the final answer, while harmlessness was evaluated on the entire reasoning chain. This hybrid approach is likely what most frontier labs use today.

The OpenAI GPT-4 technical report showed that RLHF doubled accuracy on adversarial questions. Even more striking, OpenAI noted that labelers preferred outputs from the 1.3B parameter InstructGPT model over the 175B parameter GPT-3. A smaller model with RLHF beat a model 135x its size without it. That result alone justified the technique's central role in modern AI.

RLHF also has a practical advantage that's often overlooked: it's more data-efficient than pretraining. You don't need trillions of tokens. InstructGPT used around 50,000 preference comparisons. Anthropic's dataset contained roughly 318K comparisons. Compared to the trillions of tokens and hundreds of millions of dollars required for pretraining, RLHF delivers outsized improvements for a relatively modest investment in human annotation.

Want to understand LLM training end-to-end and build AI systems yourself?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured bootcamp to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is RLHF in simple terms?

RLHF (Reinforcement Learning from Human Feedback) is a training technique that teaches LLMs to generate responses that humans prefer. Instead of defining "good" mathematically, humans rank model outputs, a reward model learns to predict those rankings, and then reinforcement learning optimizes the LLM to produce higher-scoring responses. It's what transformed GPT-3 into ChatGPT.

Why can't you just use supervised fine-tuning instead of RLHF?

Supervised fine-tuning (SFT) only shows the model examples of good responses, never bad ones. It also struggles with tasks where there's no single "correct" answer. RLHF captures nuanced preferences by letting humans compare different responses, providing both positive and negative signals. OpenAI showed that a 1.3B model with RLHF outperformed a 175B model with only SFT, demonstrating that alignment matters more than raw size for usability.

What is the difference between PPO, DPO, and GRPO?

PPO (Proximal Policy Optimization) is the original RL algorithm used in RLHF, requiring four models in memory simultaneously. DPO (Direct Preference Optimization) eliminates the reward model entirely, training directly on preference pairs as a classification task. GRPO (Group Relative Policy Optimization) removes the critic model from PPO by comparing multiple responses within a group, reducing memory by roughly 50%. GRPO is now the dominant algorithm for training reasoning models.

How much does RLHF cost for a frontier model?

The total cost includes human annotation (potentially millions of dollars for hundreds of thousands of expert comparisons at ~$100 per complex comparison), compute for running PPO across four model copies (requiring hundreds of GPUs for 70B+ models), and iterative evaluation. The annotation alone for a production RLHF pipeline can cost $1-5 million depending on scale and task complexity.

What is RLVR and how is it different from RLHF?

RLVR (Reinforcement Learning with Verifiable Rewards) uses automatically verifiable rewards instead of human preference labels. For math problems, the reward is whether the answer is correct. For code, it's whether the code passes tests. DeepSeek R1 showed that RLVR with GRPO can produce emergent reasoning abilities without any human feedback, making it cheaper and more scalable than traditional RLHF for reasoning tasks.

References

1. Training Language Models to Follow Instructions with Human Feedback (InstructGPT) - arXiv (Ouyang et al., OpenAI)

2. Illustrating Reinforcement Learning from Human Feedback (RLHF) - Hugging Face Blog

3. RLHF: Reinforcement Learning from Human Feedback - Huyenchip

4. Secrets of RLHF in Large Language Models Part I: PPO - arXiv

5. RLHF 101: A Technical Tutorial - CMU Machine Learning Blog

6. Group Relative Policy Optimization (GRPO) - Cameron R. Wolfe

7. Post-Training in 2026: GRPO, DAPO, RLVR and Beyond - LLM Stats

8. The State of LLMs 2025 - Sebastian Raschka

9. InstructGPT and RLHF: Aligning Language Models with Human Preferences - Michael Brenndoerfer

10. Reinforcement Learning from Human Feedback - Wikipedia

The entire trajectory of modern AI has been guided by one deceptively simple question: what happens when you make models bigger, train them on more data, and throw more compute at them?

The answer, discovered through years of empirical research, is that performance improves predictably. Not randomly. Not chaotically. It follows clean mathematical curves called scaling laws. These laws are the reason OpenAI built GPT-4, the reason Google trained Gemini Ultra, and the reason companies are collectively spending nearly $700 billion on AI infrastructure in 2026. Every major decision about model size, training budget, and data collection at frontier AI labs is informed by these equations.

But here's the thing most people don't talk about: scaling laws also tell you exactly when bigger stops being better. And we may be approaching that point faster than the hype suggests. Let's break down what scaling laws actually say, how they evolved, whether they're hitting a wall, and why training LLMs from scratch remains one of the most expensive things humans have ever done.

What Are Scaling Laws in AI?

Scaling laws are empirical relationships that describe how a neural network's performance changes as you increase three key variables: model size (number of parameters), training data (number of tokens), and compute (total floating-point operations used during training).

The core discovery is that the model's loss (a measure of how wrong its predictions are) decreases as a power law when any of these variables increases. A power law means the relationship follows the form: Loss = constant / variable^exponent. On a log-log plot, this shows up as a straight line, which makes the relationship both predictable and useful for planning.

There are two landmark papers that defined this field, and they reached notably different conclusions about how to allocate resources. Understanding both is essential because the tension between them has shaped every major AI model released in the last five years.

The Kaplan Scaling Laws (OpenAI, 2020)

In January 2020, a team at OpenAI led by Jared Kaplan (with co-authors including Dario Amodei, who later founded Anthropic, and Sam McCandlish) published "Scaling Laws for Neural Language Models." This paper ran systematic experiments varying model size, data, and compute, and found three power-law relationships.

Performance improves predictably with model size, dataset size, and compute, with trends spanning more than seven orders of magnitude. The paper also found that architectural details like network width or depth had minimal effects within a wide range. What mattered most was the total parameter count and the amount of training data.

The critical conclusion from Kaplan's work was that model size matters more than data. Given a fixed compute budget, the optimal strategy was to train a very large model on a relatively modest amount of data and stop early. The allocation split roughly 73% toward parameters and 27% toward data.

This finding directly influenced the design of GPT-3. OpenAI trained a 175 billion parameter model on "only" 300 billion tokens, a ratio of roughly 1.7 tokens per parameter. At the time, this was considered the right approach: build the biggest model you can afford and don't worry too much about data volume.

GPT-3 was a sensation. It could write essays, code, and poetry. And the lesson the industry took from it was simple: bigger is better. The parameter race was on.

The Chinchilla Scaling Laws (DeepMind, 2022)

Two years later, a team at DeepMind led by Jordan Hoffmann flipped the script entirely.

Their paper, "Training Compute-Optimal Large Language Models," showed that Kaplan's conclusions were biased by experimental choices. Specifically, Kaplan's team used smaller models (up to 1B parameters), didn't count embedding parameters, and used learning rate schedules that were suboptimal for longer training runs. When DeepMind ran more carefully controlled experiments with models up to 16B parameters and properly tuned cosine learning rate schedules, they found something different.

The Chinchilla conclusion: model size and data are equally important. For a given compute budget, you should scale both parameters and training tokens in roughly equal proportion. The optimal ratio is approximately 20 tokens per parameter.

To prove this, DeepMind trained a model called Chinchilla with 70 billion parameters on 1.4 trillion tokens (exactly 20:1). Despite being 4x smaller than Gopher (280B parameters), Chinchilla outperformed it on nearly every benchmark. It also beat GPT-3 (175B), Jurassic-1 (178B), and Megatron-Turing NLG (530B).

The implication was devastating for the parameter-maximization approach: most existing LLMs were massively undertrained. They had too many parameters relative to their training data. GPT-3, by Chinchilla's math, should have either been trained on 3.5 trillion tokens (at 175B parameters) or been a 15B parameter model (at 300B tokens). It was neither.

This single insight reshaped the entire industry. Meta trained Llama 2 70B on 2 trillion tokens. Llama 3 8B was trained on a staggering 15 trillion tokens, roughly 1,875 tokens per parameter, far beyond even Chinchilla's recommendations. The era of "train smaller models on way more data" had begun.

Beyond Chinchilla: The Inference-Aware Scaling Laws

The Chinchilla scaling law optimized for one thing: minimizing training compute. But in the real world, training is a one-time cost. Inference, serving the model to millions of users every day, is the recurring expense that dominates total cost of ownership.

Researchers at MosaicML (now Databricks) identified what they called the "Chinchilla Trap." If you follow Chinchilla's recommendations exactly, you end up with a model that's optimally trained but potentially too large to serve cheaply at scale. A 70B model costs much more to run per request than a 7B model, even if the 70B model is slightly better.

Their analysis showed that if you expect high inference demand (say, billions of API requests over a model's lifetime), you should train a smaller model on significantly more data than Chinchilla recommends. The inference-optimal ratio could be 100-200 tokens per parameter, not 20.

This is exactly what we've seen in practice. Llama 3 8B was trained on 15 trillion tokens (1,875:1 ratio). Microsoft's Phi series of small language models was trained on "textbook-quality" synthetic data specifically to squeeze maximum capability into tiny models. DeepSeek pushed efficiency even further, training their V3 model (671B total parameters, but a Mixture of Experts with only 37B active per token) on 14.8 trillion tokens for a reported compute cost of just $5.6 million.

The lesson: scaling laws aren't just about making the best model. They're about making the best model that you can afford to serve.

Will Scaling Laws Always Work?

This is the billion-dollar question, and the honest answer in 2026 is: probably not in their current form.

Scaling laws predict that loss decreases as a power law with more compute. But there's a catch that's easy to miss. On a log-log plot, power-law improvements look like a straight line, which feels exciting. On a linear plot, however, the same curve looks like exponential decay, with massive initial gains that flatten out quickly. Each doubling of compute gives you less improvement than the last one. This is diminishing returns baked into the math itself.

Several concrete signs suggest that brute-force scaling is reaching practical limits.

The data wall. Chinchilla-optimal training for a 1 trillion parameter model would require roughly 20 trillion tokens of training data. High-quality text data on the internet is estimated at somewhere between 10-50 trillion tokens depending on how you count. We are approaching a point where the largest models may need more unique training data than exists. Synthetic data generation is one solution, but research shows that over-reliance on synthetic data can introduce diversity issues and "model collapse" where models trained on their own outputs gradually degrade.

GPT-5's reception. The launch of GPT-5 was met with what many described as a muted response compared to GPT-4's debut. While technically more capable, the gap between GPT-4 and GPT-5 felt smaller to users than the gap between GPT-3.5 and GPT-4. This aligns with what scaling laws predict: the closer you get to the performance ceiling, the harder each incremental improvement becomes.

Different capabilities plateau at different points. Research on model size versus performance shows that knowledge tasks (like MMLU) show diminishing returns beyond 30B parameters. Reasoning tasks (like GSM8K) plateau around 70B+ parameters. Code generation diminishes after 34B+. Language understanding flattens at 13B+. Only creative tasks continue benefiting significantly from larger scales.

Industry leaders are signaling a shift. Ilya Sutskever stated at NeurIPS 2024 that "pretraining as we know it will end" and that "the 2010s were the age of scaling, now we're back in the age of wonder and discovery." Sara Hooker's 2026 essay "On the Slow Death of Scaling" documented how smaller models are rapidly closing the gap with larger ones through better training techniques. Falcon 180B (2023) was outperformed by Llama 3 8B (2024) just one year later.

The sub-scaling phenomenon. Recent research studying over 400 models found that as datasets grow very large, performance improvements decelerate faster than standard scaling laws predict. The culprit is data density: as you consume more data, the marginal uniqueness of each new sample decreases, leading to redundancy and diminishing returns that compound.

None of this means scaling is dead. It means that pure parameter scaling, training bigger dense models on more data with more compute, is no longer the only path forward. The frontier is moving toward smarter scaling: test-time compute (letting models "think" longer during inference, as in OpenAI's o1 and o3), Mixture of Experts architectures (activating only a fraction of parameters per token), better data curation, and distillation (smaller models learning from larger ones).

Why Training LLMs From Scratch Is So Expensive

Even with all the scaling law research telling you exactly how much data and compute you need, actually training a frontier LLM from scratch remains one of the most expensive engineering endeavors in human history.

Let's look at the numbers. The original Transformer paper (2017) cost roughly $900 to train. GPT-3 (2020) cost between $500,000 and $4.6 million in compute. GPT-4 (2023) reportedly cost over $100 million, with Stanford's AI Index calculating $78 million in compute alone. Google's Gemini Ultra was estimated at $191 million. Meta's Llama 3.1 405B came in around $170 million.

On average, companies spent 28x more training their most recent flagship model compared to its predecessor. Training costs for frontier models have been growing 2-3x per year for the past eight years.

Anthropic's CEO Dario Amodei has publicly stated that current frontier model training costs span $100 million to $1 billion, with projections reaching $5-10 billion by 2025-2026 and potentially $10-100 billion within three years.

These costs break down across several categories.

Compute infrastructure is the largest line item. Training GPT-4 consumed an estimated 21 billion petaFLOPs of computation. At current prices, an NVIDIA H100 costs roughly $25,000 per unit, with additional infrastructure costs of $5,000-$50,000 per GPU for power, cooling, and networking. A single frontier training run might occupy thousands of GPUs for months. Meta's Llama 3 training cluster used 16,000 H100 GPUs.

Data acquisition and management has become surprisingly costly. The global data annotation market is projected to grow from $2.32 billion in 2025 to $9.78 billion by 2030. Human-in-the-loop annotation for RLHF (reinforcement learning from human feedback) costs approximately $100 per high-quality annotation, and expert annotation rates can exceed $40 per hour.

Energy consumption is substantial and growing. A single modern AI data center campus can consume 500 megawatts to 1 gigawatt of power. OpenAI's Texas data center alone consumes roughly 300 megawatts, enough to power a mid-sized city, and is set to hit 1 gigawatt by mid-2026.

Failed experiments are rarely discussed but add significantly to total costs. The $5.6 million figure DeepSeek reported for training their V3 model excluded infrastructure, experimentation, and failed training runs. Real-world training involves multiple attempts, hyperparameter sweeps, and debugging sessions that can double or triple the final compute bill.

This is precisely why the industry has shifted heavily toward fine-tuning, distillation, and open-source models. Fine-tuning a pre-trained model like Llama 3 on domain-specific data can cost as little as $500-$5,000 with LoRA adapters, a fraction of the millions required for training from scratch. For most organizations, training a frontier model is not feasible, not necessary, and not the right approach. The smart play is to leverage existing open-source models and customize them for your specific use case.

Want to master LLM training, fine-tuning, and deployment?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured bootcamp to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What are scaling laws in large language models?

Scaling laws are empirical power-law relationships that describe how LLM performance improves as you increase model size (parameters), training data (tokens), and compute (FLOPs). The two most important scaling laws are the Kaplan laws (OpenAI, 2020) which favored larger models, and the Chinchilla laws (DeepMind, 2022) which showed that model size and data should be scaled equally, with an optimal ratio of roughly 20 tokens per parameter.

What is the Chinchilla scaling law?

The Chinchilla scaling law, published by DeepMind in 2022, states that for a given compute budget, the optimal training strategy allocates resources equally between model parameters and training data. The recommended ratio is approximately 20 tokens per parameter. DeepMind proved this by training Chinchilla (70B parameters, 1.4T tokens), which outperformed models 4x its size including Gopher (280B) and GPT-3 (175B).

Are LLM scaling laws hitting a wall?

Frontier labs are seeing diminishing returns from pure parameter scaling. Different capabilities plateau at different model sizes, high-quality training data is becoming scarce, and smaller models trained with better techniques are rapidly closing the gap with larger ones. However, new scaling dimensions like test-time compute, Mixture of Experts, and synthetic data are opening alternative paths to improvement.

How much does it cost to train a large language model?

Costs vary enormously. The original Transformer (2017) cost about $900. GPT-3 cost $500K-$4.6M. GPT-4 exceeded $100 million. Gemini Ultra was estimated at $191 million. Frontier model costs are projected to reach $5-10 billion by 2026. Fine-tuning existing models is far cheaper, often $500-$5,000 with LoRA adapters, making it the practical choice for most organizations.

Why are companies still investing in bigger models if scaling has diminishing returns?

Because even diminishing returns at the frontier can be valuable. A small improvement in reasoning capability can unlock entirely new use cases. Labs are also exploring new scaling dimensions beyond raw parameters, including inference-time compute (o1/o3 reasoning models), Mixture of Experts architectures, and higher-quality training data. The shift is from "bigger models" to "smarter scaling."

References

1. Scaling Laws for Neural Language Models - arXiv (Kaplan et al., OpenAI)

2. Training Compute-Optimal Large Language Models (Chinchilla) - arXiv (Hoffmann et al., DeepMind)

3. LLM Scaling Laws: Analysis from AI Researchers - AI Multiple

4. Scaling Laws for LLMs: From GPT-3 to o3 - Cameron R. Wolfe

5. Chinchilla Data-Optimal Scaling Laws: In Plain English - Alan D. Thompson

6. AI Model Scaling Isn't Over: It's Entering a New Era - AI Business

7. Machine Learning Model Training Cost Statistics 2026 - About Chromebooks / Stanford AI Index

8. How Much Does LLM Training Cost? - Galileo AI

9. AI Beyond the Scaling Laws - HEC Paris

10. A Riff on "The Slow Death of Scaling" - BlackHC Blog

I spent the past week generating music with Google's Lyria 3 inside the Gemini app. Some tracks were genuinely impressive. Others sounded like stock music you'd hear in a dentist's waiting room. But here's what surprised me most: almost nobody using it knows how the pricing actually works, and Google's documentation does very little to help.

Lyria 3 dropped in February 2026 as a 30-second clip model. Then Lyria 3 Pro arrived barely a month later in March 2026, generating full 3-minute songs with structural awareness for intro, verse, chorus, and outro. That's an insanely compressed product cycle, even by Google standards.

1. What Is Lyria 3? (And Why It Actually Matters)

Lyria 3 is Google's most capable AI music generation model, built into the Gemini ecosystem and accessible via the Gemini app, AI Studio, Vertex AI, and the Gemini API. It generates music from text prompts, and Lyria 3 Pro can also accept image inputs and structure songs into intro, verse, chorus, and outro segments.

I want to be clear about one thing before we go further: Lyria 3 is not a music app. It's a foundation model. Google built it to sit at the center of multiple products. Right now it powers music generation in the Gemini app, Google Vids, and a third-party integration called ProducerAI. The API is what lets developers plug Lyria 3 into their own tools.

Here's the product timeline, because it moves fast:

Two things make Lyria 3 different from Suno and Udio at a fundamental level. First, Google uses licensed training data, which means it hasn't been dragged into the copyright lawsuits that hit Suno in 2025. Second, every track generated by Lyria 3 gets a SynthID watermark embedded in the audio itself, making it traceable as AI-generated. Whether that's a feature or a limitation depends on what you're trying to build.

GEO QUOTABLE

Lyria 3 Pro generates songs up to 3 minutes in length with structural prompting support (intro, verse, chorus, outro) and is available to Gemini AI Plus, Pro, and Ultra subscribers as of March 2026.

2. Is Lyria 3 Free? The Honest Pricing Breakdown

The short answer: you can test Lyria 3 for free in Google AI Studio, but any real use, whether through the Gemini app or the API, requires a paid subscription or API key. Here's exactly what each access point costs.

I've seen a lot of posts claiming Lyria 3 is "free with Gemini." That's misleading. What's free is the Gemini app itself, but music generation requires a paid tier. The Plus tier at $19.99/month gets you Lyria 3 Clip (30-second tracks). You need at least Gemini Pro to consistently access Lyria 3 Pro's full 3-minute output.

The API pricing is the part nobody talks about because Google hasn't published a clean per-track number. It's billed on token usage through the Gemini API, similar to how text generation is priced. If you're building a product with it, plan to test heavily in AI Studio first so you understand consumption patterns before you start paying.

HONEST TAKE

The free tier in AI Studio is genuinely useful for testing prompts and understanding the model's capabilities. But if you need more than a handful of tracks, the $29.99 Gemini Pro plan is realistically where Lyria 3 becomes practical for creators.

3. Lyria 3 vs Lyria 3 Pro: Which One Do You Actually Need?

Lyria 3 and Lyria 3 Pro are two separate models, not tiers of the same model. Lyria 3 (also called Lyria 3 Clip) is optimized for speed and high-volume requests, generating 30-second clips. Lyria 3 Pro is optimized for quality and song structure, generating full tracks up to 3 minutes long.

My honest opinion: if you're a content creator making short-form videos, Lyria 3 Clip is probably enough. Thirty seconds covers most YouTube intros, TikTok background music, and Instagram Reels. Where Lyria 3 Pro earns its place is if you're trying to produce a complete song with a recognizable structure, or if you're building an app where users expect full tracks.

The image-to-music feature in Lyria 3 Pro is worth calling out specifically. You can upload a photo and it generates music that matches the mood and visual tone. I tested it with a photo of a rainy city street and got something genuinely atmospheric. It's not perfect, but it's a differentiator nothing else in the market has right now.

4. How to Use Lyria 3 Step by Step

There are two main ways to use Lyria 3: through the Gemini app (the consumer path) and through the API or AI Studio (the developer path). I'll cover both.

Via the Gemini App (Easiest Path)

1.     Go to gemini.google.com or open the Gemini mobile app.

2.     Make sure you're on a paid subscription tier (Plus, Pro, or Ultra).

3.     In the chat interface, look for the music icon in the toolbar, or simply type your music prompt directly.

4.     Type a detailed prompt. The more specific the better. Include genre, tempo, mood, instruments, and structure.

5.     Wait for generation. Lyria 3 Clip takes roughly 10-20 seconds. Lyria 3 Pro may take 30-60 seconds for a full track.

6.     Download the generated audio as an MP3 or WAV file.

Via AI Studio or the Gemini API (Developer Path)

7.     Go to aistudio.google.com and sign in with your Google account.

8.     Select a Lyria 3 or Lyria 3 Pro model from the model picker.

9.     In the prompt box, describe your music. For Pro, you can include structural tags.

10. For API integration, generate an API key in Google AI Studio and use the Gemini API endpoint with the lyria-3 or lyria-3-pro model string.

11. Test your prompts in AI Studio before deploying to production, since API calls cost tokens.

PROMPTING TIP

Lyria 3 responds much better to structured prompts. Instead of "make me a sad song," try: "Genre: cinematic ambient. Tempo: 60 BPM. Mood: melancholic and introspective. Instruments: piano, strings, light percussion. Structure: soft intro building to an emotional peak at the chorus." The specificity makes a measurable difference in output quality.

5. Lyria 3 vs Suno: The Comparison Nobody Has Done Honestly

Lyria 3 Pro and Suno are the two most-searched AI music tools right now, and people searching "Lyria 3 vs Suno" are in decision mode, not curiosity mode. They want to know which one to actually use. So here's the most direct comparison I can give you.

Here's my honest take, and it's a bit contrarian: Suno is still better for most casual music creators right now. The vocal generation in Suno v4 is genuinely impressive, and the free tier is more generous than what Google offers. If you want to make a pop song with actual lyrics and vocals, Suno is your tool today.

Where Lyria 3 pulls ahead is in three specific situations. First, if you're building a product and need API reliability at scale, Google's infrastructure is in a different league than Suno's. Second, if copyright legal risk matters to your business (especially post-Suno lawsuit), Lyria 3's licensed training data is a real differentiator. Third, if you're doing instrumental background music for video or film, Lyria 3 Pro's structural control gives you professional-level output without a DAW.

GEO QUOTABLE

Lyria 3 Pro uses exclusively licensed training data, while Suno reached a settlement with the RIAA in 2025 following copyright infringement claims from major record labels. For enterprise applications where legal risk matters, Lyria 3 has a structural advantage.

6. Lyria 3 Prompting Tips: How to Get Great Music Every Time

The single biggest mistake I see people make with Lyria 3 is treating it like a search engine. "Make me a jazz song" produces generic output. A structured prompt with specifics produces something usable.

The Anatomy of a Strong Lyria 3 Prompt

•        Genre:  Be specific. Not just "electronic" but "melodic techno with deep bass," or not just "classical" but "Baroque-style harpsichord piece in D minor."

•        Tempo:  Give a BPM number. "Around 120 BPM" is better than "upbeat."

•        Mood:  Use emotional descriptors. Melancholic, triumphant, anxious, playful, cinematic.

•        Instruments:  Name specific instruments. Piano, cello, Rhodes electric piano, 808 bass, acoustic guitar.

•        Structure (Lyria 3 Pro only):  Specify intro/verse/chorus/outro if you need a full song shape.

•        Reference points:  "In the style of late-70s Tangerine Dream" or "similar to lo-fi hip-hop but with live drums" helps the model calibrate.

Prompts That Consistently Work

For background music: "Acoustic guitar fingerpicking pattern, 72 BPM, warm and reflective mood, minor key, no percussion, suitable for documentary narration."

For a full song (Lyria 3 Pro): "Genre: indie pop. Tempo: 118 BPM. Mood: hopeful and nostalgic. Instruments: electric guitar, synth pads, bass guitar, drum kit. Structure: quiet intro 8 bars, verse builds energy, chorus full band, bridge strips back to guitar and synth, final chorus with added strings."

For cinematic score: "Orchestral, 84 BPM, tension building to resolution, strings leading with brass accent, suitable for a chase scene that ends in victory, no vocals."

One thing I've noticed: Lyria 3 handles minor keys and complex emotional tones much better than it handles humor or novelty. If you're trying to generate something comedic or deliberately cheesy, results are inconsistent. For serious or cinematic output, it's quite reliable.

7. Lyria 3 Not Working? Here Are the Fixes

The most common reasons Lyria 3 stops working are subscription tier mismatches, regional availability issues, and age verification gaps. Here's how to fix the main ones.

Music option not showing in Gemini app

•        This usually means you're on the free Gemini tier. Music generation requires a paid subscription. Check your subscription status at myaccount.google.com.

•        If you're on a paid tier and it's still missing, try signing out and signing back in. The feature sometimes takes a few hours to appear after a subscription upgrade.

•        Make sure your Gemini app is fully updated. Lyria 3 features roll out in app updates.

API returning errors

•        Verify your API key is active and has billing enabled in Google Cloud Console.

•        Check that you're using the correct model string: use lyria-3-clip for short clips and lyria-3-pro for the full model.

•        Check the API rate limits. Lyria 3 Clip is built for high-volume requests, but there are still per-minute limits during the current preview period.

Generated music is poor quality

•        Specificity in your prompt is the most reliable fix. Vague prompts produce generic output.

•        Try adding a BPM value and naming specific instruments.

•        For Lyria 3 Pro, use structural tags to give the model a song shape to work within.

Lyria 3 not available in your country

•        As of March 2026, full Lyria 3 access in the Gemini app is available in the US, UK, EU, and select Asia-Pacific markets. Check the Google AI Studio availability page for your specific region.

•        The API through Vertex AI has broader regional availability than the consumer Gemini app.

Frequently Asked Questions

Is Lyria 3 free to use?

Lyria 3 is free to test in Google AI Studio with limited generations. For regular use through the Gemini app, you need a paid subscription starting at $19.99/month (Gemini AI Plus). The API requires a paid API key with token-based billing. There is no fully free unlimited access tier for Lyria 3.

What is the Lyria 3 release date?

Lyria 3 (the 30-second clip model) was released in February 2026. Lyria 3 Pro, which generates songs up to 3 minutes long with structural prompting, was released in March 2026, approximately one month after the base model.

How much does Google Lyria cost?

Google Lyria 3 costs $19.99/month on Gemini AI Plus (10 tracks/day), $29.99/month on Gemini Pro (20 tracks/day), or $99.99/month on Gemini Ultra (50 tracks/day). API pricing through the Gemini API is token-based, and Vertex AI pricing is enterprise-negotiated. AI Studio allows free testing with limited generations.

Lyria 3 vs Suno: which is better?

Suno v4 currently produces stronger vocal synthesis and is better for creators who want songs with lyrics. Lyria 3 Pro is better for instrumental music, developer API integration, enterprise applications, and use cases where copyright legal risk matters, since Lyria 3 uses exclusively licensed training data. Suno settled an RIAA copyright lawsuit in 2025 before reaching this resolution.

What is the difference between Lyria 3 and Lyria 3 Pro?

Lyria 3 (also called Lyria 3 Clip) generates 30-second audio clips with high speed and is optimized for volume. Lyria 3 Pro generates full songs up to 3 minutes, supports structural prompting (intro, verse, chorus, outro), and accepts image inputs to generate mood-matched music. Lyria 3 Pro requires a Gemini Pro or Ultra subscription.

What is Lyria 3 Pro release date?

Lyria 3 Pro was released in March 2026, approximately four to six weeks after the base Lyria 3 model launched in February 2026.

How to use Lyria 3 for free?

The only free access to Lyria 3 is through Google AI Studio (aistudio.google.com), which allows limited test generations without a paid subscription. You cannot generate music with Lyria 3 through the Gemini app without a paid tier. For developers, AI Studio is the recommended starting point before activating a paid API key.

What is Lyria 3 API pricing?

Lyria 3 API pricing is token-based through the Gemini API and varies by model and usage volume. As of March 2026, Google has not published a flat per-track price for Lyria 3. Developers should use AI Studio to estimate token consumption before deploying to production. Enterprise pricing via Vertex AI is negotiated separately.

Is AI-generated music illegal?

AI-generated music is not illegal in most jurisdictions, but copyright ownership of AI-generated works is still legally unresolved in many countries. In the US, the Copyright Office has ruled that purely AI-generated content without human creative input is not eligible for copyright protection. Using AI music trained on copyrighted works without licenses (as Suno was alleged to have done) can create legal liability. Google's Lyria 3 uses licensed training data, which reduces this risk.

Can Google AI make a song?

Yes. Lyria 3 Pro can generate complete songs up to 3 minutes long from a text prompt. You can specify genre, tempo, mood, instruments, and song structure (intro, verse, chorus, outro). Lyria 3 Pro also accepts image inputs and generates music matching the visual mood of the photo.

Is Lyria 3 available in the Gemini AI music generator?

Yes. Lyria 3 and Lyria 3 Pro are the underlying models powering the music generation feature in the Gemini app. Gemini AI Plus subscribers access Lyria 3 Clip; Gemini Pro and Ultra subscribers access both Lyria 3 Clip and Lyria 3 Pro.

Which AI music generator is better than Suno?

For instrumental music and developer API use cases, Lyria 3 Pro from Google is currently the strongest alternative to Suno. For enterprise applications requiring copyright clarity, Lyria 3's licensed training data gives it a structural advantage. Udio is another competitor but has less API maturity than either Suno or Lyria 3 as of early 2026.

Recommended Blogs

These are related posts from Build Fast with AI that give more context on the AI tools landscape:

•        Google Gemini 2.5 Pro: What Changed and Why It Matters for Developers

•        How to Use Google AI Studio: A Complete Beginner Guide

•        Suno AI Music Generator: Full Review and Pricing (2026)

•        The Best AI Tools for Content Creators in 2026

•        Google Vertex AI vs OpenAI API: Which Should You Build On?

STAY AHEAD OF AI RELEASES

I publish deep-dives on new AI tool launches every week. If you found this useful, subscribe at buildfastwithai.com for the analysis that goes beyond the press release.

References

1.     Google DeepMind — Lyria 3 Official Announcement

2.     Google AI Studio — Lyria Model Access and Documentation

3.     Google Gemini Pricing Page — Subscription Tiers

4.     Google Cloud Vertex AI — Lyria 3 API Documentation

5.     The Verge — Google Launches Lyria 3 Pro AI Music Generator (March 2026)

6.     9to5Google — Lyria 3 Pro: Everything You Need to Know

7.     Google SynthID — AI Content Identification Technology

8. US Copyright Office — AI and Copyright Policy Statement

By Satvik Paramkusham, Founder of Build Fast with AI

Every time you chat with ChatGPT, Claude, or Gemini, the model generates your response one token at a time. Each new token requires the model to look back at every previous token in the conversation to decide what comes next. Without any optimization, this means the model would redo the same calculations over and over again for tokens it has already processed. For a 4,000-token conversation, generating token #4,001 would require recomputing attention across all 4,000 previous tokens from scratch.

This is wildly inefficient. And it's exactly the problem that the KV cache solves.

The KV cache (key-value cache) is one of the most important optimization techniques in LLM inference. It stores intermediate computations from previous tokens so the model can reuse them instead of recomputing them at every step. The result is dramatically faster text generation. It's also one of the biggest memory bottlenecks in production AI systems today, consuming anywhere from hundreds of megabytes to hundreds of gigabytes of GPU memory depending on the model and context length.

If you're building, deploying, or even just using LLMs, understanding the KV cache is essential. Let's break it down.

How LLMs Generate Text Token by Token

Large language models like GPT-4, Llama, and Gemini are autoregressive. This means they generate text one token at a time, where each new token depends on all the tokens that came before it.

Here's the process: you give the model a prompt like "The weather today is". The model processes this entire prompt, computes attention across all tokens, and predicts the next token, say "sunny". Now the input becomes "The weather today is sunny", and the model processes the full sequence again to predict the next token. This repeats until the response is complete.

The critical operation here is the attention mechanism, introduced in the original "Attention Is All You Need" paper by Vaswani et al. in 2017. During attention, each token is transformed into three vectors: a query (Q), a key (K), and a value (V). The model computes attention scores by multiplying the query of the current token against the keys of all previous tokens. These scores determine how much each previous token should influence the current prediction. The values are then weighted by these scores to produce the final output.

The key insight is this: when generating token #4,001, the query vector changes (it's for the new token), but the key and value vectors for tokens #1 through #4,000 are exactly the same as they were in the previous step. Recomputing them is pure waste.

What Is the KV Cache?

The KV cache is a memory buffer that stores the key and value vectors from all previously processed tokens across every attention layer in the model. Instead of recomputing K and V for the entire sequence at every generation step, the model computes them once, stores them in the cache, and reuses them for all future steps.

Here's what happens step by step during text generation with a KV cache:

Prefill phase: The model processes your entire input prompt in parallel. It computes Q, K, and V for every token, generates the first output token, and stores all the K and V vectors in the cache. This is why you sometimes notice a small pause before the first token appears in ChatGPT or Claude.

Decode phase: For each subsequent token, the model only needs to compute Q, K, and V for the single new token. It retrieves all previous K and V vectors from the cache, computes attention between the new query and all cached keys, and produces the output. The new K and V vectors are then appended to the cache for the next step.

Without the KV cache, attention computation scales quadratically with sequence length, because every token must attend to every other token from scratch. With the KV cache, it scales linearly, because only the new token's interactions need to be computed. This is the fundamental trade-off: you trade GPU memory (to store the cache) for GPU compute (to avoid redundant calculations). In production, this trade-off is almost always worth it.

How Much Memory Does the KV Cache Use?

The KV cache can consume a surprising amount of GPU memory, and understanding the math is crucial for anyone deploying LLMs.

The formula for KV cache memory per token is:

Memory per token = 2 x num_layers x num_kv_heads x head_dim x precision_bytes

The "2" accounts for both the key and value tensors. Let's plug in real numbers for some popular models.

For Llama 3 8B with Grouped Query Attention (GQA), which uses 8 KV heads instead of the full 32, each token occupies about 0.1 MB in the cache at FP16 precision. That sounds small, but fill up the full 8,192-token context window and you're looking at roughly 1.1 GB just for the KV cache of a single request.

For Llama 2 7B without GQA, each token consumes about 0.5 MB in the cache. At the same 8K context, that's around 4 GB per request.

For larger models, the numbers get serious fast. A 70B parameter model serving a 32,000-token context can consume 80+ GB of KV cache memory for a single request. That's more than the entire capacity of an NVIDIA A100 80GB GPU, and it's just the cache, not the model weights.

When you factor in batching (serving multiple users simultaneously), the picture gets even more demanding. A 70B model serving a batch of 32 requests at 8K context needs roughly 640 GB of KV cache alone. At this scale, the KV cache often exceeds the model weights in total memory consumption.

This is why KV cache optimization has become one of the most active research areas in AI infrastructure.

Why the KV Cache Is a Bottleneck

The KV cache creates three major challenges for production LLM systems.

Memory pressure. As context windows grow (GPT-4 supports 128K tokens, Gemini supports up to 1M tokens), the KV cache grows linearly with sequence length. This directly limits how many concurrent users you can serve and how long your context windows can be. Every additional token in every active request costs memory.

Memory fragmentation and waste. Traditional KV cache implementations pre-allocate memory for the maximum possible sequence length for every request. If you allocate space for 4,096 tokens but a user only generates 200, the remaining 3,896 slots sit empty but reserved. Research from the vLLM team showed that naive memory management could lead to 60-80% of allocated KV cache memory being wasted.

Scaling constraints. For long-context applications like retrieval-augmented generation (RAG), coding assistants, and multi-turn agentic workflows, the KV cache becomes the dominant cost driver. Infrastructure teams have to decide between shorter context windows, fewer concurrent users, or more expensive GPU hardware.

This is not a theoretical problem. It directly affects the cost and performance of every AI product you use today.

KV Cache Optimization Techniques

The AI industry has developed several techniques to address the KV cache bottleneck. These operate at different levels of the stack, from model architecture to memory management to compression.

Grouped Query Attention (GQA) reduces the KV cache at the architecture level. In standard multi-head attention, every attention head maintains its own set of key and value vectors. GQA groups multiple query heads to share a single set of keys and values. Llama 2 70B and Llama 3 use GQA with an 8:1 ratio, meaning 8 query heads share 1 KV head. This reduces the KV cache size by 8x compared to standard multi-head attention with minimal quality loss (less than 0.2% in most benchmarks). GQA is now the default in nearly all modern open-source LLMs.

Multi-Query Attention (MQA) takes this further by having all heads share a single KV pair. It offers the most aggressive cache reduction but can sacrifice more model quality. It's less common in recent models than GQA.

Sliding Window Attention (SWA) limits the cache to only the most recent W tokens. Mistral 7B uses this with a window size of 4,096. Older tokens are evicted from the cache entirely. This caps memory usage regardless of sequence length, but means the model can't attend to information beyond the window. It's effectively trading long-range context for memory efficiency.

PagedAttention, introduced by the vLLM framework, revolutionized KV cache memory management. Instead of pre-allocating contiguous memory for the maximum sequence length, PagedAttention divides the cache into fixed-size blocks (typically 16 tokens per block) and allocates them on demand as sequences grow. A block table maps logical positions to physical GPU memory locations, similar to how operating systems manage virtual memory. This reduced memory waste from 60-80% to under 4%, enabling 2-4x throughput improvements. PagedAttention is now supported by all major inference frameworks including vLLM, HuggingFace TGI, NVIDIA TensorRT-LLM, and LMDeploy.

KV cache quantization compresses the cached tensors to lower precision formats. Instead of storing keys and values in FP16 (2 bytes per parameter), you can quantize to FP8 (1 byte) or INT4 (0.5 bytes), cutting memory by 2-4x. vLLM supports FP8 KV cache quantization natively on NVIDIA Hopper and Blackwell GPUs. More advanced methods like Google's TurboQuant (ICLR 2026) compress KV caches down to 3 bits with zero accuracy loss, achieving 6x memory reduction, while Nvidia's KVTC achieves up to 20x compression using PCA-based techniques.

KV cache offloading moves inactive cache data from GPU memory to CPU RAM or even SSD storage. When a user pauses mid-conversation, their cache can be offloaded to free GPU memory for active requests and reloaded when they return. NVIDIA reports up to 14x faster time-to-first-token compared to recomputing the cache from scratch. Frameworks like LMCache implement multi-tiered caching hierarchies (GPU, CPU DRAM, local disk) to extend effective memory capacity by 10-50x.

Prefix caching identifies when multiple requests share common prefixes (like identical system prompts) and shares the cached KV data across requests instead of duplicating it. This is particularly valuable for RAG applications and chat systems with consistent system prompts. vLLM's Automatic Prefix Caching feature can achieve 87%+ cache hit rates for prefix-heavy workloads.

How to Calculate KV Cache Size for Your Model

If you're deploying an LLM, you need to estimate your KV cache memory requirements before provisioning hardware. Here's the practical formula:

Total KV cache memory = 2 x num_layers x num_kv_heads x head_dim x precision_bytes x max_seq_len x batch_size

For a concrete example, let's calculate for Llama 3.1 70B with GQA (8 KV heads), 80 layers, head dimension of 128, FP16 precision, 8,192-token context, and a batch size of 32:

→ Per token: 2 x 80 x 8 x 128 x 2 bytes = 327,680 bytes (~0.3 MB) → Per request (8K context): 0.3 MB x 8,192 = ~2.6 GB → Full batch (32 requests): 2.6 GB x 32 = ~83 GB

That's 83 GB just for the KV cache. The model weights for Llama 3.1 70B in FP16 are about 140 GB. So the KV cache for a modest batch of 32 users at 8K context is already more than half the size of the model itself.

A practical rule of thumb: reserve 40-60% of your GPU memory for the KV cache, with the remainder split between model weights and activations. For an 80GB H100 running a model with tensor parallelism across 2 GPUs, you'd have roughly 30-35 GB per GPU available for cache after loading weights.

What's Next for KV Cache Technology

KV cache optimization is one of the fastest-moving areas in AI research right now. Two major compression methods are being presented at ICLR 2026 in April: Google's TurboQuant (6x compression, zero accuracy loss, no calibration needed) and Nvidia's KVTC (up to 20x compression using transform coding). Both represent generational improvements over KIVI, which was the standard baseline since ICML 2024 with its 2.6x compression ceiling.

On the infrastructure side, Nvidia's Dynamo inference engine is building cluster-scale KV cache management with its KV Block Manager, enabling cache coordination across multiple machines. Projects like llm-d (a collaboration between IBM, Google, and Red Hat) are bringing KV cache-aware routing to Kubernetes, directing requests to pods that already hold relevant cached context.

The direction is clear: KV cache management is maturing from a single-node optimization into a full production infrastructure layer, complete with tiered storage, intelligent routing, and aggressive compression. For anyone building AI systems at scale, understanding and optimizing the KV cache isn't optional. It's the single biggest lever you have for cost, latency, and throughput.

Want to master LLM inference optimization and build production AI systems?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured bootcamp to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is KV cache in large language models?

The KV cache (key-value cache) is a memory buffer that stores previously computed key and value tensors from the attention mechanism during LLM inference. Instead of recomputing these tensors for all tokens at every generation step, the model stores them once and reuses them, reducing attention computation from quadratic to linear complexity.

How much memory does the KV cache use?

KV cache memory depends on the model size, context length, precision, and batch size. For Llama 3 8B with GQA at FP16, each token uses about 0.1 MB. For a 70B model serving 32 requests at 8K context, the cache alone requires roughly 83 GB, often exceeding the model weights themselves.

What is PagedAttention and how does it help?

PagedAttention is a memory management technique introduced by the vLLM framework that divides the KV cache into fixed-size blocks allocated on demand, similar to OS virtual memory. It reduces memory waste from 60-80% to under 4%, enabling 2-4x throughput improvements. It's now supported by vLLM, TGI, TensorRT-LLM, and other major inference frameworks.

What is the difference between GQA and MQA for KV cache optimization?

Grouped Query Attention (GQA) groups multiple query heads to share a single set of key-value pairs, reducing the KV cache by the grouping ratio (typically 4-8x). Multi-Query Attention (MQA) has all heads share one KV pair for maximum reduction. GQA is more common in modern models like Llama 3 because it better balances cache savings with model quality.

How do TurboQuant and KVTC compress the KV cache?

Google's TurboQuant (ICLR 2026) uses polar coordinate transformation and 1-bit error correction to compress KV caches to 3 bits with zero accuracy loss and 6x memory reduction. Nvidia's KVTC uses PCA-based decorrelation and entropy coding to achieve up to 20x compression with less than 1% accuracy drop. TurboQuant requires no calibration while KVTC needs a one-time per-model calibration step.

Recommended Blogs

If you found this useful, these related articles from Build Fast with AI cover topics worth reading next:

1.   How to Build AI Agents

2.   Claude Opus 4.6 vs GPT-5: Which AI Model Wins in 2026?

3. what is claude cowork

4. How Google's TurboQuant Compresses LLM Memory by 6x

References

1. Mastering LLM Techniques: Inference Optimization - NVIDIA Technical Blog

2. Understanding and Coding the KV Cache in LLMs from Scratch - Sebastian Raschka

3. Efficient Memory Management for Large Language Model Serving with PagedAttention - arXiv (vLLM)

4. Techniques for KV Cache Optimization in Large Language Models - Omri Mallis

5. KV Caching Explained: Optimizing Transformer Inference Efficiency - Hugging Face Blog

6. LLM Inference Series: KV Caching, a Deeper Look - Pierre Lienhart

7. KV Cache Optimization: Memory Efficiency for Production LLMs - Introl Blog

8. KV Cache Offloading - LLM Inference Handbook - BentoML

By Satvik Paramkusham, Founder of Build Fast with AI

Every time you have a long conversation with ChatGPT, Claude, or Gemini, your LLM is quietly burning through GPU memory to keep track of everything you've said. For a 70-billion parameter model serving 512 concurrent users, that temporary memory alone can consume 512 GB, nearly four times the memory needed for the model weights themselves. This is the key-value cache problem, and it is one of the biggest bottlenecks in AI inference today.

Google Research just published a new compression algorithm called TurboQuant that attacks this problem head-on. It compresses the KV cache down to just 3 bits per value, reducing memory by at least 6x, while delivering up to 8x faster attention computation on NVIDIA H100 GPUs. The wildest part? Zero accuracy loss. No retraining. No fine-tuning. No calibration data required.

The paper will be formally presented at ICLR 2026 in late April, and independent developers are already building working implementations from the math alone. Let's break down what TurboQuant is, how it works, and why it matters for anyone building or deploying AI systems.

What Is the KV Cache and Why Does It Matter?

The key-value (KV) cache is the working memory that LLMs use during inference. Every time a model processes a token, it generates a key vector and a value vector for that token. These vectors are stored so the model doesn't have to recompute them when generating the next token. Think of it as the model's short-term memory for your conversation.

The problem is that KV cache size scales linearly with context length. As models support longer conversations and bigger context windows (32K, 128K, even 1 million tokens), the memory footprint of the KV cache grows proportionally. For a model like Llama 3 at 70B parameters with a 32,000-token context, the KV cache alone can eat up roughly 80 GB of GPU memory.

Traditional vector quantization methods can compress these caches, but they come with a hidden cost. They need to store quantization constants (normalization values) alongside the compressed data, adding 1 to 2 extra bits per value. That sounds small, but it compounds rapidly as context windows get larger. This overhead is exactly what TurboQuant eliminates.

How TurboQuant Works

TurboQuant is a two-stage compression algorithm that combines two companion techniques: PolarQuant and Quantized Johnson-Lindenstrauss (QJL). Together, they achieve near-theoretical-limit compression with zero overhead from stored quantization constants.

Stage 1: PolarQuant (the heavy lifter). PolarQuant starts by applying a random orthogonal rotation to the data vectors. This rotation transforms the data so that each coordinate follows a predictable, concentrated distribution, regardless of the original data. Then it converts the vectors from standard Cartesian coordinates into polar coordinates, separating each vector into a magnitude (radius) and a set of angles (direction). Because the angular distributions are predictable after rotation, PolarQuant can apply optimal scalar quantization without the expensive per-block normalization step that conventional methods require. This single design choice eliminates the overhead bits entirely.

Stage 2: QJL (the error corrector). Even after PolarQuant's compression, a small residual error remains. QJL handles this by projecting the leftover error into a lower-dimensional space and reducing each value to a single sign bit (+1 or -1). Using a technique based on the Johnson-Lindenstrauss transform, QJL creates an unbiased estimator that ensures the critical relationships between vectors (the attention scores) remain statistically accurate. This costs just 1 bit per dimension.

The result is a system where PolarQuant captures the vast majority of the information using most of the bit budget, and QJL cleans up the remaining error at negligible cost. The combined output uses as few as 3 bits per value while preserving the precision you'd get from 32-bit representations.

One critical design feature: TurboQuant is data-oblivious. It works the same way regardless of which model or dataset you apply it to. No calibration step. No training data. No model-specific tuning. This makes it a potential drop-in solution for any transformer-based model.

Benchmark Results and Performance

Google tested TurboQuant across five standard long-context benchmarks: LongBench, Needle In A Haystack, ZeroSCROLLS, RULER, and L-Eval, using open-source models including Gemma, Mistral, and Llama-3.1-8B-Instruct.

The results are strong across the board:

→ Perfect scores on Needle-in-a-Haystack retrieval tasks while compressing KV memory by at least 6x. The model found the buried information just as reliably as the uncompressed baseline.

→ Matched or outperformed the KIVI baseline across all tasks on LongBench, which covers question answering, code generation, and summarization.

→ Up to 8x speedup in computing attention logits with 4-bit TurboQuant on H100 GPUs, compared to 32-bit unquantized keys.

→ Superior recall ratios on vector search tasks evaluated on the GloVe dataset (d=200), outperforming Product Quantization and RabbiQ baselines despite those methods using larger codebooks and dataset-specific tuning.

An important nuance: that 8x speedup applies specifically to attention logit computation, not end-to-end inference throughput. Attention is a significant bottleneck, but not the only one, so real-world wall-clock improvements will be lower than 8x. Still, for long-context workloads where KV cache is the dominant cost, this is a massive improvement.

Independent validation is also emerging. A PyTorch implementation tested on Qwen2.5-3B-Instruct reported 99.5% attention score similarity after compression to 3 bits. Another developer built a custom Triton kernel, tested it on Gemma 3 4B on an RTX 4090, and reported character-identical output to the uncompressed baseline at 2-bit precision.

TurboQuant vs. KIVI vs. Nvidia's KVTC

TurboQuant isn't the only KV cache compression method making waves at ICLR 2026. Nvidia's KVTC (KV Cache Transform Coding) is also being presented at the same conference, and it takes a fundamentally different approach. Here's how they compare.

KIVI has been the standard baseline since ICML 2024 and ships with HuggingFace Transformers integration. It uses asymmetric 2-bit quantization and achieves roughly 2.6x compression with minimal quality loss. Solid, but limited headroom.

TurboQuant jumps to 6x compression with zero accuracy loss, requires no calibration, and works out of the box on any model. Its mathematical foundation provides provable distortion bounds, giving you confidence that the guarantees hold. The trade-off: it has only been tested on models up to roughly 8B parameters, and there is no official code release yet (expected Q2 2026).

Nvidia's KVTC takes the most aggressive approach, achieving up to 20x compression (and 40x+ for specific use cases) with less than 1 percentage point accuracy drop. It borrows from JPEG-style media compression, combining PCA-based decorrelation, adaptive quantization, and entropy coding. The catch: it requires a one-time calibration step per model using about 200K tokens on an H100. KVTC has been tested on a wider range of models (1.5B to 70B parameters) and is already integrating with Nvidia's Dynamo inference engine.

For production deployments, the choice depends on your constraints. TurboQuant offers simplicity and zero-calibration deployment. KVTC delivers higher raw compression but needs model-specific setup. Both represent a generational leap over KIVI's 2.6x ceiling.

Why This Matters for AI Deployment

The KV cache bottleneck is not an academic problem. It directly determines how many concurrent users you can serve, how long your context windows can be, and how much your GPU infrastructure costs.

A 6x reduction in KV cache memory means a model that previously needed 8 H100s for 1-million-token context could potentially serve the same context on 2 H100s. Inference providers could handle 6x more concurrent long-context requests on the same hardware. For a 32,000-token context, the KV cache drops from roughly 12 GB to about 2 GB.

This has immediate implications for several areas:

→ Long-context inference on consumer hardware. At 3-bit compression, a model's KV cache for 8K tokens drops from 289 MB to about 58 MB. On a 12GB GPU, that's the difference between fitting 8K context and fitting 40K context. This brings serious long-context capability to RTX-class GPUs.

→ Mobile and edge AI. 3-bit KV cache compression could make 32K+ context feasible on phones with software-only implementations. That changes what local AI assistants can do.

→ Vector search and RAG pipelines. TurboQuant's indexing time is nearly zero (0.0013 seconds for 1,536-dimensional vectors) compared to 239.75 seconds for Product Quantization. For retrieval-augmented generation systems, this is transformative.

→ Cost reduction for cloud providers. Memory is one of the largest line items in AI infrastructure. The market reacted immediately to TurboQuant's announcement, with memory supplier stocks dipping on the day of release.

The research team, led by Amir Zandieh and Vahab Mirrokni (VP and Google Fellow), collaborated with researchers from Google DeepMind, KAIST, and NYU. Google highlights the potential for TurboQuant to address KV cache bottlenecks in models like Gemini, though there's no confirmation that it's running in any production system yet.

How to Get Started

Google has not released official TurboQuant code yet. However, the community is moving fast:

→ A PyTorch implementation with custom Triton kernels is available on GitHub (tonbistudio/turboquant-pytorch), validated on real model KV caches.

→ MLX implementations for Apple Silicon are reporting roughly 5x compression with 99.5% quality retention.

→ llama.cpp integration is being tracked actively, with one fork (TheTom/turboquant_plus) already passing 18/18 tests with compression ratios matching the paper's claims.

→ Official open-source code from Google is widely expected around Q2 2026.

If you want to prepare now, start by benchmarking your current KV cache memory usage. Understanding your baseline footprint will help you measure impact when production-ready implementations arrive. You can also explore existing 4-bit quantization tools like AutoGPTQ, AWQ, or GGUF to get partial benefits while waiting.

Want to master LLM optimization and AI infrastructure?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured bootcamp to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is TurboQuant and how does it compress LLM memory?

TurboQuant is a compression algorithm from Google Research that reduces the key-value cache in large language models to as few as 3 bits per value. It combines PolarQuant (polar coordinate transformation) and QJL (1-bit error correction) to achieve at least 6x memory reduction with zero accuracy loss and no retraining required.

Does TurboQuant require model fine-tuning or calibration?

No. TurboQuant is completely data-oblivious, meaning it works out of the box on any transformer-based model without training, fine-tuning, or dataset-specific calibration. This is a key differentiator from competing methods like Nvidia's KVTC, which requires a one-time calibration step per model.

How does TurboQuant compare to Nvidia's KVTC?

Both are being presented at ICLR 2026. TurboQuant achieves 6x compression with zero accuracy loss and no calibration. KVTC achieves up to 20x compression with less than 1 percentage point accuracy drop but requires per-model calibration. TurboQuant has been tested on models up to 8B parameters, while KVTC covers 1.5B to 70B.

Can I use TurboQuant today?

Google has not released official code, but independent developers have built working implementations in PyTorch, MLX, and llama.cpp. Official open-source release is expected around Q2 2026. Community implementations are available on GitHub for experimentation.

What is the KV cache and why does compressing it matter?

The KV cache is the temporary memory LLMs use to store key-value pairs from previously processed tokens during inference. It scales linearly with context length and can consume more memory than the model weights themselves. Compressing it directly reduces GPU memory costs, enables longer context windows, and allows more concurrent users on the same hardware.

References

1. TurboQuant: Redefining AI Efficiency with Extreme Compression - Google Research Blog

2. Google's TurboQuant Reduces AI LLM Cache Memory by at Least 6x - Tom's Hardware

3. Google's TurboQuant Algorithm Slashes LLM Memory Use by 6x - Winbuzzer

4. Google's New TurboQuant Algorithm Speeds Up AI Memory 8x - VentureBeat

5. TurboQuant PyTorch Implementation - GitHub (tonbistudio)

6. KV Cache Transform Coding for Compact Storage in LLM Inference - arXiv (Nvidia KVTC)

7. NVIDIA Researchers Introduce KVTC Transform Coding Pipeline - MarkTechPost

Three AI company CEOs walked into San Francisco in the same week. Sam Altman claimed 800 million weekly ChatGPT users. Sundar Pichai pushed Gemini into every Google product. And Aravind Srinivas, the 31-year-old IIT Madras graduate who built Perplexity AI, quietly dropped something different entirely. On February 25, 2026, Perplexity launched Computer, a multi-model AI agent that orchestrates 19 different AI models to complete complex, long-running tasks on your behalf. No single chatbot. No one-model bottleneck. Just one system that picks the right AI for each job and runs until it is done.

I have been watching AI tools long enough to know hype from substance. And this one, I think, is substance. Not because of the marketing. Because of the architecture.

. What Is Perplexity Computer?

Perplexity Computer is an autonomous AI agent launched on February 25, 2026, that coordinates 19 different AI models to complete complex, multi-step workflows entirely in the background. You describe a goal, and Computer breaks it into subtasks, assigns each to the best-suited AI model, runs them simultaneously using specialized sub-agents, and delivers finished results.

Think of it this way: before Computer, using AI meant switching between tools. You would use Claude for coding, Gemini for image analysis, GPT-5.2 for long documents. Manual juggling. Computer eliminates that by doing the juggling for you, automatically.

The product is currently available exclusively to Perplexity Max subscribers at $200 per month. It runs entirely in the cloud, meaning you do not need a powerful local machine. Tasks execute in an isolated environment with a real filesystem, browser access, and connections to over 400 applications including Slack, Gmail, GitHub, and Notion.

Here is why this matters: in January 2025, over 90% of enterprise AI tasks ran through just two models. By December 2025, no single model handled more than 25% of usage across businesses. Models stopped converging into general-purpose tools. They started specializing. Computer is built around that reality.

2. How Does Perplexity Computer Work?

The architecture is where this gets genuinely interesting. Computer is not one AI doing everything. It is an orchestration layer that routes each part of your task to the model that handles that type of work best.

The 5-step workflow inside every Computer task:

•        Step 1: Goal Input - You describe what you want. 'Build me an interactive stock dashboard for my top 10 holdings' or 'Plan and execute a content calendar for my SaaS product launch.'

•        Step 2: Task Decomposition - Computer breaks that goal into specific subtasks: research, data collection, writing, design, code generation, etc.

•        Step 3: Model Selection - The system routes each subtask to the right model. Claude Opus 4.6 for reasoning and software engineering. Gemini for deep research and visual outputs. GPT-5.2 for long-context recall. Grok for fast, lightweight tasks. Nano Banana for image generation. Veo 3.1 for video.

•        Step 4: Parallel Execution - Sub-agents run simultaneously. The entire workflow does not wait for one model to finish before the next starts.

•        Step 5: Continuous Optimization - The system monitors output quality, self-corrects, and delivers final results.

The result is a system that can handle workflows that would take a human team hours, days, or even months. Early users demonstrated Computer building Bloomberg Terminal-style financial dashboards, replacing entire six-figure marketing tool stacks over a single weekend, and automating data pipelines that previously required dedicated engineers.

My honest take: the 19-model orchestration is genuinely clever engineering. But the credit system, which charges per task complexity without publishing a clear table of costs, is a problem I will address in the pricing section.

3. Perplexity Computer vs ChatGPT: Key Differences

The most common question I see: is Perplexity the same as ChatGPT? Short answer: no. Longer answer: they are solving different problems.

ChatGPT is a conversational AI. It excels at writing, explaining concepts, generating code snippets, and having back-and-forth dialogue. You ask, it answers. It is fundamentally reactive.

Perplexity Computer is proactive and agentic. You set a goal, walk away, and come back to a finished deliverable. It is less 'chat assistant' and more 'autonomous digital employee.' That is a meaningful distinction.

The comparison that actually matters is not ChatGPT vs Perplexity Computer. It is single-model tools vs multi-model orchestration. OpenAI's tools optimize within one model. Perplexity's bet is that the future belongs to whoever orchestrates all models together.

I think Perplexity is right about the direction. Whether $200/month is the right price for where the technology is right now, that is a separate conversation.

4. Perplexity Computer Pricing Breakdown

Pricing is where things get complicated. Here is the full picture as of March 2026:

The Max tier gives subscribers 10,000 credits per month. Each task consumes credits based on complexity. Simple research tasks use fewer credits. Long multi-day workflows burn through them faster. The problem: Perplexity has not published a clear table showing exactly how many credits each task type costs. That makes budgeting frustrating for heavy users.

The Enterprise tier at $325 per seat per month ($3,250/year) adds organization-level security controls, SCIM provisioning, configurable data retention, audit logs, and Slack integration where employees can query @computer directly inside team channels.

My take on the pricing: $200/month is steep for individual users. For a small business that currently pays for separate research tools, marketing software, and data analysis subscriptions, the math could work out. For individuals just experimenting with AI, start with the free tier or Pro at $20/month first.

5. Perplexity Personal Computer: The Local Desktop Agent

Perplexity Personal Computer is a separate product launched on March 11, 2026, at the inaugural Ask 2026 developer conference. It runs on a dedicated local device, such as a Mac Mini, giving the cloud-based AI agent persistent access to your local files, applications, and sessions.

Here is the difference between the two products:

•        Perplexity Computer (cloud-based): Runs entirely in Perplexity's cloud infrastructure. Fast, scalable, no local hardware required. Best for research, content creation, data workflows.

•        Perplexity Personal Computer (local): Runs on your physical device with access to local files. The AI can open apps, manage files, and operate sessions that persist even when you are offline.

The local product addresses a privacy concern that many users raised about the cloud version: sensitive documents, proprietary code, and personal files never need to leave your machine.

Perplexity says Personal Computer includes user approval requirements for all sensitive actions, a full audit trail for every session, and a kill switch for emergency stop. Given that similar open-source tools like OpenClaw have caused serious damage to users' systems when running autonomously, those safeguards are not optional extras. They are table stakes.

6. Is Perplexity Computer Available on PC?

Yes, Perplexity Computer is available on PC and all major platforms. The cloud-based version of Computer runs in your browser, accessible from any Windows PC, Mac, Linux machine, or mobile device. You do not need to install anything.

For Windows users specifically, access works through:

•        Perplexity's web interface at perplexity.ai (any browser, including Chrome, Edge, Firefox)

•        The Perplexity Chrome extension for quick access while browsing

•        The Perplexity Android and iOS mobile apps

•        Slack integration (for enterprise users querying @computer in channels)

The Personal Computer local agent is currently Mac-only (designed around Mac Mini hardware). A Windows version has not been officially announced as of March 2026. If you are a Windows-only user wanting the local-file-access functionality, you will need to wait for an update or use the cloud version in the meantime.

The free tier of Perplexity AI (basic search functionality) is available to everyone without registration. The Computer agent specifically requires a Max subscription at $200/month.

7. Who Is the Perplexity CEO and Is He a Billionaire?

Aravind Srinivas is the CEO and co-founder of Perplexity AI. Born in Chennai, Tamil Nadu, on June 7, 1994, he studied Electrical Engineering at IIT Madras before earning his PhD in Computer Science from UC Berkeley. Before founding Perplexity, he held research roles at Google Brain, DeepMind, and OpenAI.

Yes, Aravind Srinivas is a billionaire. In October 2025, he debuted on the M3M Hurun India Rich List with an estimated net worth of approximately $2.5 billion (roughly 211 billion rupees), making him India's youngest billionaire at just 31 years old. His wealth is primarily tied to his equity stake in Perplexity AI, which reached a valuation of $21.21 billion following its Series E-6 funding round in early 2026.

He co-founded Perplexity in August 2022 alongside Denis Yarats, Johnny Ho, and Andy Konwinski. The company has raised approximately $1.5 billion in total funding, with investors including Jeff Bezos, Nvidia, and Databricks.

What I find interesting about Srinivas is his public contrarianism. While most AI CEOs talk about making AI more human, he talks about making users more productive. His March 2026 All-In podcast appearance, where he called AI-driven layoffs a 'glorious future,' was controversial. But the underlying argument, that AI enables individuals to build businesses they could never build before, is consistent with what Perplexity Computer is actually designed to do.

8. Real-World Use Cases for Perplexity Computer

The gap between AI demos and real-world usefulness is usually enormous. So what are people actually doing with Computer?

Marketing and Campaign Automation

Marketers have used Computer to plan, execute, and optimize complete digital marketing campaigns without manually switching tools. One case that went viral: a solo founder replaced a six-figure marketing tool stack over a single weekend by having Computer handle campaign research, ad copy generation, performance tracking, and reporting in a single workflow.

Financial Analysis and Dashboards

Early users built Bloomberg Terminal-style financial dashboards by instructing Computer to pull SEC filings, analyze competitive data, generate visualizations, and package results as a shareable web page. Finance analysts at enterprise customers reported pulling revenue breakdowns by vertical from Snowflake simultaneously with competitive context from CRM data, with Computer writing and executing the queries.

Software Development Workflows

For software engineering tasks, Computer routes work to Claude Opus 4.6, which has emerged as the most-used model for coding tasks across Perplexity's enterprise customer base. Developers have used it to automate end-to-end workflows including code generation, documentation, testing, and deployment scripting.

Research and Competitive Intelligence

Perplexity benchmarked Computer across 16,000 queries against institutional standards from McKinsey, Harvard, MIT, and BCG. The system is being used by business teams to produce research reports, competitive landscapes, and market analyses that previously required analyst teams.

9. Is Perplexity Computer Worth It?

I want to be honest here, because the $200/month price tag is a real barrier for most people.

Perplexity Computer is worth $200/month if:

•        You currently pay for multiple SaaS research, analytics, or marketing tools that could be replaced

•        You or your team regularly spends hours on workflows that could be automated: competitive research, reporting, data analysis, content creation at scale

•        You are an enterprise team where the per-seat cost beats hiring dedicated analysts

Perplexity Computer is not worth $200/month if:

•        You primarily want an AI chatbot for writing and quick questions (ChatGPT Plus at $20/month covers this)

•        You want to run a few tests and see how it works (start with the free tier)

•        Your workflows are simple enough that single-model tools handle them fine

The global agentic AI market is projected to grow from $9.14 billion in 2026 to $139 billion by 2034. Perplexity is entering this market at exactly the right moment. But entering at the right moment and pricing correctly for your target market are two different things. The credit system needs more transparency before I would call this a must-buy for individuals.

For enterprise teams, the conversation is different. When 92% of the Fortune 500 already have employees using Perplexity through personal accounts anyway, formalizing that into a proper enterprise contract with security controls and audit trails makes clear business sense.

10. FAQ: Everything People Ask About Perplexity Computer

What is a Perplexity Computer?

Perplexity Computer is an autonomous AI agent launched by Perplexity AI on February 25, 2026. It orchestrates 19 different AI models simultaneously to complete complex, multi-step tasks without constant human input. It runs in the cloud and is available exclusively to Perplexity Max subscribers at $200 per month.

Is Perplexity the same as ChatGPT?

No. Perplexity AI started as an AI-powered answer engine with real-time web search and cited sources. ChatGPT is a conversational AI built on OpenAI's GPT models. Perplexity Computer specifically is an autonomous multi-model agent, while ChatGPT remains primarily a single-model conversational tool. They serve different primary use cases.

Is Perplexity AI better than Google?

For direct, cited answers with real-time web data, many users find Perplexity more efficient than Google's traditional link-based results. Perplexity Computer goes further by executing autonomous workflows, not just answering queries. For broad discovery and localized results, Google still leads. For AI-first research tasks, Perplexity competes seriously.

Is Perplexity free or paid?

Perplexity has a free tier available without registration that provides basic AI search with cited answers. Perplexity Pro costs $20 per month. Perplexity Max, which includes full access to the Computer agent, costs $200 per month. Enterprise Max is priced at $325 per seat per month.

Is Perplexity CEO a billionaire?

Yes. Aravind Srinivas, the CEO and co-founder of Perplexity AI, debuted on the M3M Hurun India Rich List in October 2025 with an estimated net worth of approximately $2.5 billion. He became India's youngest billionaire at 31, primarily through his equity stake in Perplexity AI, which is valued at over $21 billion as of early 2026.

What is Perplexity AI mostly used for?

Perplexity AI is primarily used as an answer engine that provides direct, cited responses to research questions by searching the web in real time. It is popular among students, researchers, journalists, and professionals for getting fast, accurate answers with source attribution. The newer Computer agent is used for autonomous workflow automation across marketing, finance, coding, and research.

How to use Perplexity on a computer?

Access Perplexity through your browser at perplexity.ai on any Windows PC, Mac, or Linux machine. No installation is required for the cloud-based version. For the Computer agent specifically, you need a Max subscription ($200/month). The Personal Computer local agent is currently Mac-only and requires hardware setup on a dedicated device such as a Mac Mini.

Can I run Perplexity locally?

Perplexity's main service is cloud-based and cannot be run locally in the traditional sense. However, Perplexity Personal Computer, announced on March 11, 2026, is a local-device agent that runs on Mac hardware (currently Mac Mini) with access to local files and apps. It is separate from the cloud-based Computer agent and designed to complement it.

Who are the big 4 of AI in 2026?

The most discussed AI leaders in 2026 are OpenAI (ChatGPT, GPT-5 series), Google DeepMind (Gemini, Veo), Anthropic (Claude Opus 4.6, Claude Sonnet), and Meta AI (Llama open-source models). Perplexity AI is increasingly recognized as a major challenger in the AI search and agent space, though it operates differently as an orchestration platform rather than a single frontier model developer.

Recommended Blogs

If you found this useful, these related articles from Build Fast with AI cover topics worth reading next:

  How to Build AI Agents

  Claude Opus 4.6 vs GPT-5: Which AI Model Wins in 2026?

what is claude cowork

References

1.     VentureBeat - Perplexity Computer Enterprise Launch:

3.     TechCrunch - Perplexity Computer Deep Dive:

4.     Wikipedia - Perplexity AI:

5.     SentiSight - What Is Perplexity Computer:

6.     Gulf News - Aravind Srinivas Billionaire Profile:

Comments

Every developer who has used Claude Code knows the routine. You kick off a task. Claude writes two lines. It asks permission to save a file. You click yes. It writes three more lines. It asks permission to run a bash command. You click yes again. Repeat this for 45 minutes, and you start wondering whether you are the developer or the approval button.

Anthropic shipped auto mode for Claude Code on March 24, 2026, and it directly solves this. The idea is simple: let Claude make low-risk permission decisions on its own, while a dedicated AI safety classifier watches every tool call before it runs. No more permission fatigue. No more babysitting a terminal.

I think this is one of the most practical Claude Code updates since the tool launched. Not because it is flashy, but because it fixes a real workflow pain point that was quietly driving developers toward the much riskier --dangerously-skip-permissions flag. Let me break down exactly what it does, how it works, and what you should actually know before you turn it on.

What Is Claude Code Auto Mode?

Claude Code auto mode is a new permission setting that allows Claude to autonomously approve and execute file edits and bash commands without requiring a human confirmation for each action. It is positioned as a middle path between Claude Code's cautious default behavior (approve everything) and the all-or-nothing --dangerously-skip-permissions flag (approve nothing, skip everything).

Before auto mode existed, developers had two real options: accept constant approval prompts, or flip the danger flag and hope nothing went sideways. Auto mode gives you a third choice. Claude makes the low-stakes permission calls itself, and a background classifier catches anything that looks risky before it ever executes.

Anthropic describes it as: a mode where Claude makes permission decisions on your behalf, with safeguards monitoring actions before they run. The key word is before. The safety check happens prior to execution, not as a post-audit.

I think the framing here is important. This is not Anthropic saying "trust Claude blindly." It is Anthropic saying "here is a structured way to give Claude more autonomy with a guardrail layer built in." That is a meaningful distinction.

How the Auto Mode Safety Classifier Works

The safety classifier is a dedicated AI model that reviews every tool call before Claude executes it. Think of it as a second AI sitting alongside Claude Code, scanning each proposed action against a checklist of potentially destructive behaviors.

Safe actions proceed automatically. Risky ones get blocked, and Claude is redirected to attempt a different approach. If Claude keeps trying to take actions that are repeatedly blocked, the system eventually surfaces a human permission prompt.

The classifier evaluates each action in real time, before execution. This is not a log-review system. It is a pre-execution gate.

There are some practical side effects worth knowing: auto mode may have a small impact on token consumption, cost, and latency for tool calls, since each tool call now involves an additional model evaluation. Anthropic has not published exact overhead figures, but they describe it as a small impact.

One thing I find genuinely clever about this design: the classifier is separate from Claude itself. Claude is not self-policing, which means you are not relying on the same model to both propose and evaluate an action. That independent review layer is a more robust safety architecture than asking a single model to check its own work.

Auto Mode vs Default Mode vs --dangerously-skip-permissions

Here is a direct comparison of all three permission modes in Claude Code:

The --dangerously-skip-permissions flag has its legitimate uses. Sandboxed CI pipelines, Docker containers, and isolated testing environments where data loss is irrelevant are valid cases. But developers should not run it on a live codebase or production environment, and Anthropic explicitly says so.

Auto mode changes the calculus. You get the workflow speed of skipping prompts for routine tasks, but you keep a safety net for actions that genuinely warrant human review. For most real development work on actual codebases, auto mode is the right choice over the danger flag.

What Auto Mode Blocks by Default

The classifier targets a specific set of high-risk actions. According to Anthropic's documentation, the default block list includes:

•       Mass file deletion (wiping multiple files or directories at once)

•       Sensitive data exfiltration (attempts to read and transmit private credentials, API keys, or personal data)

•       Malicious code execution (running scripts that attempt to damage systems or escalate privileges)

•       Actions that create ambiguous or irreversible consequences in unclear environments

Critically, the classifier is not a static rules engine. It uses an AI model to assess context, which means it can reason about ambiguous situations. If the user's intent is unclear, the classifier errs on the side of caution.

That said, it is not perfect. Anthropic is transparent about this: the classifier may still allow some risky actions when user intent is ambiguous, or when Claude lacks enough context about the environment to assess risk accurately. It may also occasionally block benign actions. This is a research preview, not a production-hardened security system.

My take: the occasional false positive (a safe action getting blocked) is a far better outcome than a false negative (a destructive action getting approved). I will gladly click one extra confirmation per session to avoid an accidental mass delete.

How to Enable Claude Code Auto Mode

Getting auto mode running depends on where you are using Claude Code. Here are the steps for each environment:

Command Line (CLI)

•       Run: claude --enable-auto-mode to activate auto mode

•       Once enabled, cycle to it within a session using Shift+Tab

•       Auto mode persists across commands in the session until you switch back

VS Code Extension

•       Open VS Code Settings and navigate to Claude Code settings

•       Toggle auto mode to On

•       In an active session, select auto mode from the permission mode dropdown

Claude Desktop App

•       Auto mode is disabled by default on the desktop app

•       Go to Organization Settings, then Claude Code to toggle it on

•       Requires Team plan access as of March 2026

For Enterprise Admins

Admins who want to disable auto mode organization-wide can set "disableAutoMode": "disable" in managed settings. This blocks both the CLI flag and the VS Code extension toggle for all users in the organization.

Enterprise and API rollout was described by Anthropic as coming in the days immediately following the March 24 launch. If you are on an API plan and do not see it yet, it is likely in the queue.

Who Can Use Auto Mode and When It Is Rolling Out

As of March 25, 2026, auto mode is available as a research preview on the Claude Team plan. It works with both Claude Sonnet 4.6 and Opus 4.6.

Anthropic's rollout schedule:

•       Team plan users: Available now (March 24, 2026)

•       Enterprise plan users: Rolling out in the days after launch

•       API users: Rolling out in the days after launch

•       Claude Desktop app: Disabled by default, toggleable via Organization Settings

The research preview label matters. Anthropic is actively collecting feedback and plans to improve the classifier over time. Expect changes to the block list and classifier behavior as real-world usage surfaces edge cases.

If you are a Team plan subscriber and do not see the option, check for a Claude Code update. The feature requires the latest version of the CLI and VS Code extension.

What to Watch Out For: Honest Limitations

I want to be direct here because the developer community deserves a straight read, not a press release rewrite.

Auto mode is not a sandbox. Anthropic recommends using it in isolated environments. That means containers, VMs, or dedicated dev environments, not directly on your production machine or live codebase if you can avoid it. The classifier reduces risk, it does not eliminate it.

The classifier can be wrong. Ambiguous intent is the primary failure mode. If Claude does not have enough context about your environment, a risky action might slip through. Always review what Claude has done after a long autonomous run, especially file deletions or network calls.

Token cost goes up slightly. Every tool call now involves an additional classifier evaluation. For small tasks this is negligible. For a 200-tool-call session, the overhead adds up. Not a dealbreaker, but worth budgeting for.

None of these limitations make auto mode a bad feature. They make it a responsible preview. Anthropic shipping this with caveats and a clear block list, rather than overpromising, is the right approach.

Frequently Asked Questions

What is Claude Code auto mode?

Claude Code auto mode is a permission setting launched by Anthropic on March 24, 2026 that allows Claude to execute file writes and bash commands without requesting user approval for each action. A dedicated AI safety classifier reviews every tool call before execution, blocking high-risk actions like mass file deletion or sensitive data exfiltration.

How do I enable Claude Code auto mode?

In the CLI, run claude --enable-auto-mode, then use Shift+Tab to cycle to it in a session. In VS Code, toggle it on in Claude Code settings, then select it from the permission mode dropdown. In the desktop app, enable it via Organization Settings, then Claude Code.

Is Claude Code auto mode safe to use on production code?

Anthropic recommends using auto mode in isolated environments such as containers, VMs, or sandboxes. While the classifier blocks the most common destructive actions, it is a research preview and can miss edge cases. Do not run it directly on production systems without a backup strategy.

What is the difference between auto mode and --dangerously-skip-permissions?

The --dangerously-skip-permissions flag bypasses all permission checks with zero safety net. Auto mode adds a pre-execution AI classifier that blocks destructive actions before they run. Auto mode is meaningfully safer for real-world development work and is designed to replace the danger flag for most use cases.

Does auto mode cost more to use?

Yes, slightly. Every tool call in auto mode runs through an additional classifier model, which increases token consumption, cost, and latency by a small amount. Anthropic has not published exact overhead figures, but describes the impact as small.

Which Claude models work with auto mode?

Auto mode works with both Claude Sonnet 4.6 and Claude Opus 4.6 as of the March 2026 launch.

When will auto mode be available for Enterprise and API users?

Anthropic announced that Enterprise plan and API users would receive access in the days immediately following the March 24, 2026 Team plan launch. If you are on those plans and do not see it, check for a Claude Code update.

Can Enterprise admins disable auto mode for their organization?

Yes. Enterprise admins can set "disableAutoMode": "disable" in managed settings to block auto mode for all users on the CLI and VS Code extension.

Can we automate Claude Code completely with auto mode?

Auto mode allows Claude Code to execute file writes and bash commands without per-action approvals, but it is not fully unattended. If the classifier repeatedly blocks an action, it will prompt the human. For truly headless automation, it is still safest to run in a sandboxed container.

Does Claude Code automatically use agents in auto mode?

Auto mode affects permission behavior, not agent invocation. Claude Code does not automatically spin up sub-agents in auto mode. It gives Claude more autonomy to execute tool calls without waiting for user approvals.

Does Claude Code auto mode automatically select the model?

No. Model selection (Sonnet 4.6 vs Opus 4.6) remains manual. Auto mode only governs permission behavior, not which underlying model handles the task.

Is auto mode safer than --dangerously-skip-permissions?

Yes, significantly. The danger flag bypasses all permission checks with no safety net. Auto mode adds a pre-execution classifier that blocks mass deletions, data exfiltration, and malicious code execution. For any work on real codebases, auto mode is the right choice.

What does the auto mode classifier block by default?

The classifier blocks mass file deletion, sensitive data exfiltration, malicious code execution, and ambiguous high-risk actions. The block list is managed by Anthropic and will be updated as the research preview matures.

Which plans support Claude Code auto mode?

As of March 2026, auto mode is available to Team plan users as a research preview. Enterprise and API plan rollout was announced for the days immediately following the March 24 launch. Free plan availability has not been announced.

Recommended Reads

If this update has you thinking about Claude and AI coding tools, these posts from Build Fast with AI go deeper on related topics:

7 AI Tools That Changed Developer Workflow (March 2026)

150 Best Claude Prompts That Work in 2026

Claude AI 2026: Models, Features, Desktop & More

Best AI for Coding 2026: Nemotron vs GPT-5.3 vs Opus 4.6

Every AI Model Compared: Best One Per Task (2026)

References

1.      Auto Mode for Claude Code - Official Anthropic Blog

2.      Claude Code Permission Modes Documentation

3.      How Claude Code's New Auto Mode Prevents AI Risks - ZDNET, March 25 2026

4.      Auto Mode for Claude Code - Simon Willison's Weblog, March 24 2026

Claude Code Gets Auto Mode to Reduce Interruptions - Techzine Global, March 25 2026

I didn't expect much. Honestly. Another Chinese AI lab dropping a benchmark-topping model that sounds incredible on paper and disappoints in practice. That was my attitude when Moonshot AI quietly shipped Kimi K2.5 on January 27, 2026. Then I started running it.

The headline numbers alone are hard to ignore: 76.8% on SWE-Bench Verified, 96.1% on AIME 2025, and a Humanity's Last Exam (HLE) score of 50.2% that actually beats Claude Opus 4.5's 32.0% and GPT-5.2 High's 41.7%. All of this at $0.60 per million input tokens. Claude Opus charges $5 per million. That's an 8x price gap.

But the thing that made me stop scrolling was Agent Swarm: the ability to coordinate up to 100 specialized AI sub-agents working in parallel on a single task. No other frontier model does t

his. Not GPT. Not Claude. Not Gemini.

So I spent three weeks running Kimi K2.5 through real workflows. Coding, research, visual tasks, document analysis. Here is everything I found, including where Kimi genuinely shines and where Claude still wins.

1. What Is Kimi 2.5?

Kimi K2.5 is Moonshot AI's most advanced language model, released on January 27, 2026. It is a multimodal, open-source AI model with 1.04 trillion total parameters and 32 billion active parameters, built on a Mixture-of-Experts (MoE) architecture. The model processes both text and visual inputs, supports a 256,000-token context window, and runs in four distinct operational modes.

Moonshot AI is a Chinese AI startup founded in 2023. Their previous model, Kimi K2, earned a strong reputation as a coding-focused model. K2.5 takes that foundation and adds native vision capabilities, Agent Swarm technology, and significant improvements in reasoning and document understanding.

My hot take: Kimi K2.5 is the most significant open-source model release since Meta's Llama 3. Not because it beats everything. It doesn't. But because it genuinely closes the gap with closed-source giants at a fraction of the cost, and introduces a capability (Agent Swarm) that nobody else has shipped yet.

The model is available for free on kimi.com with usage limits, and commercially via API through Moonshot AI's platform at platform.moonshot.ai.

2. Kimi K2.5 Key Features and Architecture

The architecture choices behind Kimi K2.5 explain why it performs the way it does. Here is what matters.

Mixture-of-Experts (MoE) Design

Kimi K2.5 uses a 1.04 trillion parameter MoE model with only 32 billion parameters active per token inference. This means it achieves the intelligence of a trillion-parameter model while running at the speed and cost of a much smaller one. The model has 384 specialized experts, with a routing mechanism that selects 8 experts per token. It also uses Multi-head Latent Attention (MLA) and native INT4 quantization for a 2x generation speedup on standard hardware.

Native Multimodal Architecture

Unlike earlier models that bolt a vision adapter onto a text backbone, Kimi K2.5 was trained from scratch on approximately 15 trillion mixed visual and text tokens. This native approach is why visual coding tasks work so well. You can drop a Figma design screenshot into the model and get working React or Vue code out. Feed it a Loom video of a bug and it watches, reasons, and suggests a fix.

Four Operational Modes

Each mode uses the same underlying model weights. The switching happens through decoding strategy and tool permissions.

256K Context Window

Kimi K2.5 supports 256,000 tokens natively, which is 28% more than Claude's default 200K context.

In practical coding terms, 256K tokens means you can load approximately 200,000 lines of code into a single conversation without chunking. You can maintain full project context across a long refactoring session. For developers working on large monorepos, this is genuinely useful.

3. Kimi K2.5 Benchmark Performance

Let's get into the actual numbers. I'm going to focus on the benchmarks that matter for real-world use, not academic demonstrations.

What the numbers actually mean: Kimi K2.5 trails Claude by about 4 points on SWE-Bench, which is the benchmark most developers care about for real code quality. That 4-point gap translates to slightly more debugging cycles and fewer first-attempt solutions on hard engineering problems. It's real. But on competitive programming (LiveCodeBench: 85.0% vs 64.0%) and agentic research tasks, Kimi leads by substantial margins.

My honest read: the gap between Kimi and Claude has closed to the point where the right choice depends almost entirely on your use case and budget, not raw capability.

4. Is Kimi K2.5 Better Than Claude for Coding?

This is the question everyone is asking. Short answer: it depends on the type of coding.

Where Kimi K2.5 Wins

•        Frontend and UI development from screenshots, Figma exports, or screen recordings

•        Competitive programming and algorithm challenges (85.0% LiveCodeBench vs Claude's 64.0%)

•        Large codebase analysis that needs the full 256K context window

•        High-volume batch code generation where the 8x cost difference matters

•        Visual debugging: upload a screen recording of a bug and get a fix

Where Claude Still Wins

•        Production-grade code quality on complex engineering problems (80.9% SWE-Bench vs 76.8%)

•        Terminal-intensive agentic workflows requiring consistent tool use

•        Code review with nuanced judgment about architecture and maintainability

•        Enterprise environments where proven reliability matters more than cost savings

•        Projects needing the largest possible context window (Claude Opus 4.6 supports 1M tokens)

I ran the same complex refactoring task through both models over several weeks. Claude's output required fewer iterations. Kimi's output was faster to generate and cost roughly a tenth as much. For a startup burning through API tokens on code generation, that math is hard to ignore.

Contrarian take: The narrative that Claude is simply 'better' for coding is becoming less accurate. For visual-first workflows and competitive algorithms, Kimi K2.5 is actually the stronger choice right now. The benchmark gap on SWE-Bench is 4 points. That's narrow enough to matter only at the edges.

5. Kimi K2.5 Agent Swarm: How It Works

This is the feature that has no equivalent anywhere else in the market. Agent Swarm is currently in research preview and represents a fundamentally different approach to complex task execution.

Standard AI models process tasks sequentially. One step, then the next, then the next. Agent Swarm deploys an orchestrator that analyzes the task, identifies parallelizable subtasks, spins up specialized sub-agents (think: AI Researcher, Physics Expert, Fact Checker, Code Reviewer), and runs them simultaneously.

The result: 4.5x faster task completion on wide-search tasks and an 80% reduction in end-to-end runtime compared to sequential single-agent approaches, according to Moonshot AI's January 2026 testing data.

Agent Swarm vs Standard Agent: Real Numbers

Moonshot AI trained Agent Swarm using a new technique called Parallel Agent Reinforcement Learning (PARL). Early training rewards parallel execution. Later training shifts to task quality. The final reward function balances completion quality (80%) with critical path efficiency (20%). This prevents the model from artificially splitting tasks without any actual performance benefit.

For a 50-competitor market research task that would take a single agent 3+ hours, Agent Swarm completes it in 40-60 minutes. At 9x lower cost than Claude Opus, that's a genuinely different economic proposition.

6. Kimi K2.5 Pricing: Is It Free?

Kimi K2.5 has three access tiers, and the pricing structure is one of its strongest selling points.

The cost comparison is stark.

•        Kimi K2.5 API: $0.60 per million input tokens

•        Claude Opus 4.5: $5 per million input tokens

•        GPT-5.2: approximately $2.50-10 per million input tokens

For a fintech startup running one million API requests annually with typical 5K output token responses, the annual cost breaks down to roughly $13,800 for Kimi K2.5 versus $150,000 for Claude Opus 4.5. That's a $136,000 difference on a single workload.

The open-source license (modified MIT) allows commercial use with attribution required only if you exceed 100 million monthly active users or $20 million monthly revenue. For the vast majority of companies, that means effectively free commercial use of the model weights.

7. Kimi K2.5 vs Claude vs GPT-5.2: Full Comparison

8. Kimi K2.5 API and Kimi Code CLI

API Access

The Kimi API is fully compatible with OpenAI's API format, meaning existing codebases can switch with minimal changes. The model string is 'kimi-k2.5' and the API endpoint runs through platform.moonshot.ai. Moonshot also provides an Anthropic-compatible API.

Two key parameters for API usage: set temperature to 1.0 for Thinking mode and 0.6 for Instant mode. Set top_p to 0.95 for both. To disable thinking mode and run in Instant mode, pass {'chat_template_kwargs': {'thinking': false}} in extra_body.

Kimi Code CLI

Moonshot AI released Kimi Code CLI as a direct Claude Code alternative. It's open-source under Apache 2.0, has 6,400+ GitHub stars as of February 2026, and supports MCP tools, VS Code, Cursor, and Zed integration. Install via pip: 'pip install kimi-cli'. The CLI acts as an autonomous coding agent that can handle debugging, refactoring, and multi-step development workflows in your terminal.

Where Claude Code has an edge: web search reliability is noticeably better, and the artifact rendering inside the chat interface means you can test interactive components without leaving the conversation. Where Kimi Code CLI holds up: context persistence across long agent sessions, strong execution discipline on multi-step tool chains, and meaningfully lower rate limit friction at the $60/month tier versus Claude's $200/month.

9. Who Should Use Kimi K2.5?

Use Kimi K2.5 if:

•        You're building frontend applications and want to generate code directly from design files

•        You run high-volume batch coding tasks and the 8x cost difference actually matters to your budget

•        You need Agent Swarm for complex parallel research or analysis tasks

•        You want to self-host a frontier-class model on your own infrastructure

•        You're working with competitive programming problems where LiveCodeBench performance matters

Stick with Claude if:

•        Code quality on complex engineering problems is the top priority and you need that 80.9% SWE-Bench reliability

•        You need a context window larger than 256K (Claude Opus supports up to 1M tokens)

•        You're doing terminal-heavy agentic workflows where Claude's tool use consistency still leads

•        Enterprise procurement processes require proven production case studies and reliability SLAs

My personal recommendation for most teams: run Kimi K2.5 for frontend work, batch operations, and research tasks. Route to Claude for complex backend architecture, code review, and production-critical code. Model routing is the actual winning strategy in 2026.

Frequently Asked Questions

What can Kimi 2.5 do?

Kimi K2.5 handles text generation, code writing, visual understanding, document analysis, and agentic tasks. Its standout capabilities are visual-to-code generation (turning UI screenshots into working React or Vue code), Agent Swarm coordination (up to 100 parallel sub-agents), and competitive programming. It supports 256K token contexts and runs in Instant, Thinking, Agent, and Agent Swarm modes.

Is Kimi better than Claude for coding?

It depends on the coding type. Kimi K2.5 leads Claude on LiveCodeBench (85.0% vs 64.0%) and visual coding tasks. Claude Opus 4.5 leads on SWE-Bench Verified (80.9% vs 76.8%), terminal-intensive agentic workflows, and production code quality for complex engineering problems. For daily development and frontend work, Kimi K2.5 offers roughly 80-90% of Claude's capability at approximately 8x lower API cost.

Is Kimi 2.5 free to use?

Yes. Kimi K2.5 is free on kimi.com with usage limits across all four operational modes. The model weights are also freely available on Hugging Face for self-hosting under a modified MIT license. Commercial API access costs $0.60 per million input tokens through Moonshot AI's platform.

What is Kimi K2.5's context window?

Kimi K2.5 supports 256,000 tokens natively, implemented using the YaRN extension. This is 28% larger than Claude's default 200K context and double GPT-5.2's 128K. In practical terms, 256K tokens can hold approximately 200,000 lines of code, making it suitable for analyzing large monorepos in a single session.

Is Kimi AI good for coding?

Yes, particularly for frontend development, visual programming, and high-volume tasks. Kimi K2.5 scores 85.0% on LiveCodeBench and 76.8% on SWE-Bench Verified as of January 2026. Its native multimodal architecture allows direct code generation from UI design screenshots, and the Kimi Code CLI provides a full terminal-based coding agent experience as an alternative to Claude Code.

What is the Kimi K2.5 API price?

Kimi K2.5 API pricing is $0.60 per million input tokens and $2.50-3.00 per million output tokens through platform.moonshot.ai. This is approximately 8x cheaper than Claude Opus on input tokens ($5/M) and 3-4x cheaper than most GPT-5.2 tiers. The API is fully compatible with OpenAI's format, allowing drop-in migration from existing integrations.

Is Kimi K2.5 open source?

Yes. Kimi K2.5 is released under a modified MIT license. Model weights are freely downloadable from Hugging Face and support deployment via vLLM, SGLang, or KTransformers. Commercial use requires attribution only above 100 million monthly active users or $20 million monthly revenue.

What is Kimi K2.5's Agent Swarm?

Agent Swarm is Kimi K2.5's most distinctive feature. It coordinates up to 100 specialized sub-agents working simultaneously on a complex task. An orchestrator decomposes the task, assigns subtasks to specialists, and manages parallel execution. In Moonshot AI's testing from January 2026, Agent Swarm delivered 4.5x faster task completion and 80% runtime reduction compared to sequential single-agent execution.

Recommended Blogs

If you found this useful, these posts from Build Fast with AI cover related topics worth reading:

•        GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5 (2026)

•        Build Fast with AI Blog Archive

References

11.  Kimi K2.5 Official Tech Blog - Moonshot AI:

12.  Kimi K2.5 on Hugging Face - moonshotai/Kimi-K2.5:

13.  Kimi API Platform Documentation:

14.  Kimi K2.5 Developer Guide - NxCode (February 2026):

15.  Kimi K2.5 Complete Guide - Codecademy:

16.  Moonshot AI Releases Kimi K2.5 - InfoQ (February 17, 2026):

17.  Kimi K2.5 vs Claude Opus 4.5 Comparison (January 28, 2026):

18.  NVIDIA NIM - Kimi K2.5 Model Card:

Cursor just released a coding model that beats Claude Opus 4.6 on Terminal-Bench 2.0 while costing 10 times less. That is not a typo. Composer 2 launched on March 19, 2026, and I have been going through every piece of data Cursor published to give you the most complete picture of what this model actually does, what it costs, and whether it should change how your team uses AI for coding.

The short version: Composer 2 scores 61.3 on CursorBench, 61.7 on Terminal-Bench 2.0, and 73.7 on SWE-bench Multilingual. Cursor's prior model, Composer 1.5, scored 44.2, 47.9, and 65.9 respectively. That is not a small jump. It is also worth knowing that Composer 2 is built on Kimi K2.5, an open-source model from Moonshot AI, with Cursor's own continued pretraining and reinforcement learning layered on top. The provenance detail matters, and I will get into why.

I am going to break down the architecture, the benchmark data, the pricing comparison against GPT-5.4 and Claude Opus 4.6, and what the Kimi K2.5 base actually means for people who care about model transparency.

What Is Cursor Composer 2?

Cursor Composer 2 is Cursor's third-generation proprietary coding model, released on March 19, 2026, and available directly inside the Cursor IDE. It is positioned as a frontier-level agentic coding model that can handle complex, multi-step coding tasks requiring hundreds of sequential actions.

Cursor, the AI code editor built by San Francisco startup Anysphere (currently valued at $29.3 billion), first introduced its in-house Composer model series in October 2025 alongside the Cursor 2.0 platform redesign. Composer 1.5 followed in February 2026. Composer 2 is the biggest leap so far.

The model ships with a 200,000-token context window and comes in two variants: a standard version priced at $0.50 per million input tokens, and a fast version at $1.50 per million input tokens. The fast variant is now the default option inside Cursor.

What makes Composer 2 different from simply plugging in a third-party model like Claude or GPT-5.4 is deep IDE integration. Composer 2 has direct access to search, terminals, version control, and isolated worktrees inside Cursor, which reduces the friction of multi-file, multi-step coding tasks compared to chat-based alternatives.

How Composer 2 Was Built: Architecture and Training

Composer 2 uses a Mixture-of-Experts (MoE) architecture built on Kimi K2.5, the open-source model from Moonshot AI, enhanced with Cursor's own continued pretraining and reinforcement learning. Cursor confirmed the Kimi K2.5 base on March 20, 2026, after a user discovered it in API request headers. Lee Robinson, VP of Developer Education at Cursor, acknowledged that roughly 25% of the model's computational foundation derives from the original Kimi K2.5 architecture.

Here is what changed compared to Composer 1.5. Prior Composer models were built by applying reinforcement learning directly on top of a frozen base model. Think of it like teaching advanced skills on a foundation that was never specifically prepared for them. Composer 2 flips this: Cursor first ran continued pretraining to update the foundational model weights using coding-specific data, then applied RL on top of that stronger base.

The RL training itself focuses on long-horizon coding tasks. Cursor's approach, which they call compaction-in-the-loop reinforcement learning, builds context summarization directly into the training process. When a generation sequence hits a token-length threshold, the model compresses its own context to approximately 1,000 tokens from 5,000 or more. According to Cursor's March 2026 research documentation, this approach reduces compaction error by 50% compared to prior methods and enables the agent to work through hundreds of sequential actions on project-scale refactors without losing its goal.

The MoE architecture means only a subset of model parameters activates for any given input, which keeps inference fast while maintaining a large total parameter count. Cursor has not published the exact total parameter count.

Benchmark Results: Composer 2 vs Opus 4.6 vs GPT-5.4

Composer 2 outperforms Claude Opus 4.6 on Terminal-Bench 2.0, scoring 61.7 against Opus 4.6's 58.0, while GPT-5.4 still leads the field at 75.1 on the same benchmark. Here is the full comparison across all three benchmarks Cursor reported:

A few things I want to flag about these numbers. CursorBench is Cursor's own proprietary evaluation suite, which means the scores there are self-reported and not independently verified yet. Terminal-Bench 2.0 is maintained by the Laude Institute and uses the Harbor evaluation framework, which gives it more credibility as a third-party standard. SWE-bench Multilingual is a well-established benchmark for multi-language software engineering tasks.

The gain from Composer 1.5 to Composer 2 is genuinely large: 38% improvement on CursorBench and 29% on Terminal-Bench 2.0. The benchmark jump is also bigger than the jump from Composer 1 to 1.5, which makes sense given the architectural change from RL-only scaling to continued pretraining plus RL.

Cursor is not claiming the top spot overall. GPT-5.4 still leads Terminal-Bench 2.0 at 75.1, and Cursor's messaging is deliberately pragmatic: Composer 2 offers a strong cost-to-intelligence ratio for everyday coding inside the Cursor IDE, not universal benchmark dominance. That honesty, I think, is the right move.

Pricing: How Much Does Composer 2 Cost?

Composer 2 Standard costs $0.50 per million input tokens and $2.50 per million output tokens, which is approximately 86% cheaper than Composer 1.5's previous pricing of $3.50 and $17.50 respectively. Here is how Composer 2 stacks up against competing models:

The price drop is significant. Composer 1.5 cost $3.50 per million input tokens and $17.50 per million output tokens in February 2026. Composer 2 Standard is 86% cheaper on both counts. Even Composer 2 Fast at $1.50/$7.50 is 57% cheaper than Composer 1.5.

On individual Cursor plans, Composer model usage falls within a separate usage pool with a generous base allocation. When you use Cursor's Auto mode (letting it pick the best model per request), Composer usage is unlimited on paid plans with no credit deduction. Third-party models like GPT-5.4 and Opus 4.6 draw from your monthly credit pool instead.

Cache-read pricing is also discounted: $0.20 per million tokens for Composer 2 Standard and $0.35 per million for Composer 2 Fast, compared to $0.35 per million for Composer 1.5.

Cursor Composer 2 vs Claude Code: Which One Should You Use?

Cursor Composer 2 and Claude Code serve different workflows and are more complementary than competitive. According to a 2026 developer survey cited by DataCamp, Claude Code now leads as the most-used AI coding tool among professionals, with 46% naming it the tool they love most. Cursor came in second at 19%.

The practical difference comes down to where you work. Claude Code is Anthropic's terminal-based coding agent. It excels at complex, autonomous tasks that benefit from deep reasoning, like long-term system maintenance and multi-step architectural decisions. Many developers use Cursor for everyday IDE editing and switch to Claude Code for more demanding autonomous tasks.

Composer 2's advantage is its tight integration with Cursor's IDE environment. It has direct access to your codebase's search, terminal, file system, and version control without requiring external tooling. That makes it faster and less friction-heavy for routine coding, multi-file edits, and iterative development cycles.

My take: if you are already a Cursor user, Composer 2 should be your default model for day-to-day coding. It is unlimited on paid plans when used through Auto mode, and the benchmark data shows it is now legitimately competitive with the frontier. For complex reasoning tasks or system-level operations, Claude Code still has an edge, as one analyst noted that Composer lacks the reasoning depth of Opus 4.6 for non-coding tasks. But for writing, editing, and testing code inside an IDE? Composer 2 makes a strong case.

GitHub Copilot, for comparison, still has the widest adoption at over 20 million all-time users, but many developers report that Cursor's multi-file editing capabilities go deeper than Copilot's Agent mode. Roughly 70% of developers now use two to four AI tools simultaneously, so picking one tool as your exclusive option is increasingly a minority approach.

The Kimi K2.5 Controversy: What It Means for You

Cursor did not disclose at launch that Composer 2 is built on Kimi K2.5, an open-source model developed by Moonshot AI in China. The disclosure came one day after launch, after a user discovered the base model identity in API request headers.

Lee Robinson, Cursor's VP of Developer Education, confirmed the Kimi K2.5 foundation and clarified that Cursor's continued pretraining and RL account for about 75% of what makes Composer 2 perform the way it does. Robinson stated the performance is now very different from the base Kimi K2.5 model.

I think the lack of upfront disclosure was a mistake, not a scandal. Open-source model bases are common in the industry. The more relevant question for most teams is: does the model work well, and is it priced appropriately? On both counts, the data suggests yes.

For teams with strict data sovereignty requirements or supply chain policies around Chinese-origin technology, the Kimi K2.5 foundation is a real consideration that should factor into your procurement process. Cursor does enforce sandbox execution and commit signing, and provides audit trails for enterprise governance. But the underlying model origin is a legitimate question for compliance-sensitive environments.

How to Use Composer 2 in Cursor

Composer 2 is available now inside Cursor and in the early alpha of Cursor's new interface called Glass. Here is how to access it:

•       Open Cursor and navigate to the model selector in the Composer panel.

•       Select Composer 2 or Composer 2 Fast from the model list. Fast is now the default option.

•       Alternatively, use Auto mode and Cursor will route appropriate requests to Composer 2 automatically, with unlimited usage on paid plans.

•       API access is available via Cursor's model API at $0.50/$2.50 per million tokens for Standard and $1.50/$7.50 for Fast.

Cursor's individual plan includes Composer 2 usage in a standalone pool separate from third-party model credits. If you are currently spending credits on Opus 4.6 or GPT-5.4 for routine coding tasks, switching to Composer 2 through Auto mode is likely to reduce your credit burn without a meaningful quality drop for most use cases.

Is Cursor Composer 2 Worth It? My Honest Take

The benchmark improvements are real and substantial. A 38% jump on CursorBench and a pass rate of 73.7 on SWE-bench Multilingual puts Composer 2 firmly in the competitive tier of coding models, not a budget option that makes you feel the tradeoff.

The pricing story is even more interesting. At $0.50/$2.50 per million tokens, Cursor has priced Composer 2 more aggressively than any comparable frontier coding model. Claude Opus 4.6 costs 10 times more on input tokens and 10 times more on output tokens. GPT-5.4 costs 5 times more on input and 6 times more on output. For teams running high token volumes, the economics shift significantly.

The contarian point I will make: benchmark leadership does not always translate to daily-use satisfaction. Composer 2 does not match GPT-5.4's Terminal-Bench 2.0 score of 75.1, and Opus 4.6 still has stronger general reasoning capabilities outside pure coding tasks. If your workflows require the model to do significant reasoning about system design or long-term planning beyond just writing code, Composer 2 may not fully replace a frontier reasoning model.

But for what most developers actually use Cursor for? Editing files, refactoring functions, generating boilerplate, fixing bugs, writing tests? Composer 2 at this price point is hard to argue against.

Frequently Asked Questions

What is Composer 2 in Cursor?

Composer 2 is Cursor's third-generation proprietary AI coding model, released on March 19, 2026. It is built on Kimi K2.5 from Moonshot AI with additional continued pretraining and reinforcement learning. The model scores 61.3 on CursorBench, 61.7 on Terminal-Bench 2.0, and 73.7 on SWE-bench Multilingual.

How much does Cursor Composer 2 cost?

Composer 2 Standard is priced at $0.50 per million input tokens and $2.50 per million output tokens. The fast variant, which is now the default, costs $1.50 per million input tokens and $7.50 per million output tokens. Both variants are roughly 86% and 57% cheaper, respectively, than Composer 1.5.

Is Composer 2 free on Cursor?

Composer 2 usage is included in a standalone usage pool on Cursor's individual paid plans. When using Auto mode, Composer model usage is unlimited on paid plans with no credit deduction. Direct access to third-party frontier models like GPT-5.4 and Opus 4.6 still draws from your monthly credit pool.

How does Composer 2 compare to Claude Code?

Cursor Composer 2 and Claude Code serve different use cases. A 2026 developer survey found that 46% of professionals named Claude Code as their most-loved AI coding tool versus 19% for Cursor. Composer 2 excels at in-IDE coding tasks with tight integration into Cursor's file system, terminal, and version control. Claude Code is preferred for more complex, autonomous, reasoning-heavy tasks outside the IDE context.

What benchmarks does Composer 2 score on?

Composer 2 scores 61.3 on CursorBench (up from 44.2 for Composer 1.5), 61.7 on Terminal-Bench 2.0 (up from 47.9), and 73.7 on SWE-bench Multilingual (up from 65.9). It outperforms Claude Opus 4.6's Terminal-Bench 2.0 score of 58.0 but trails GPT-5.4 at 75.1 on the same benchmark.

Is Cursor Composer 2 built on Kimi K2.5?

Yes. Cursor confirmed on March 20, 2026, that Composer 2 is built on Kimi K2.5, an open-source model developed by Moonshot AI. Cursor applied continued pretraining and reinforcement learning on top of the Kimi K2.5 base. Lee Robinson, VP of Developer Education at Cursor, stated that roughly 75% of Composer 2's performance characteristics come from Cursor's additional training.

What is the context window for Cursor Composer 2?

Cursor Composer 2 ships with a 200,000-token context window, which is sufficient for large codebase operations and project-scale refactoring tasks.

Cursor Composer 2 vs Composer 1: What changed?

Composer 2 represents the largest generational jump in the Composer series. The main architectural change is the introduction of continued pretraining on the base model before applying reinforcement learning. Composer 1 scored 38.0 on CursorBench and 40.0 on Terminal-Bench 2.0. Composer 2 scores 61.3 and 61.7 on the same benchmarks, a gain of over 50% on Terminal-Bench 2.0.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•       7 AI Tools That Changed Developer Workflow (March 2026)

•       Best AI for Coding 2026: Nemotron vs GPT-5.3 vs Opus 4.6

•       Every AI Model Compared: Best One Per Task (2026)

•       GPT-5.4 Mini vs Nano: Pricing, Benchmarks & When to Use Each

•       12+ AI Models in March 2026: The Week That Changed AI

References

11.   Introducing Composer 2 - (Official Cursor Blog, March 19, 2026)

13.   Cursor's Composer 2 beats Opus 4.6 on coding benchmarks at a fraction of the price - thenewstack.io (The New Stack, March 2026)

15.   Cursor Admits Composer 2 Is Built on Chinese AI Model Kimi K2.5 - (eWeek, March 2026)

16.   Cursor launches Composer 2 with state-of-the-art coding - (TechZine, March 2026)

17.   How Good is Cursor's Composer 2? - offthegridxp.substack.com (Michael Spencer, March 2026)

Your engineering team is shipping faster than ever. Pull requests are piling up. And your senior developers are spending 2-3 hours a day doing code review instead of building.

That was Anthropic's exact problem. Code output per engineer grew by 200% after they started using Claude internally. But review became the new bottleneck. So they built a solution and in March 2025, they shipped it to everyone.

Claude Code Review is a multi-agent AI system that deploys five parallel specialized agents on every pull request, catches bugs before your team even sees the PR, and posts findings as inline comments. I've gone deep on how it works, how to set it up, what it actually costs, and whether it's genuinely worth $15-25 per review.

The short answer: for teams shipping more than 3-4 PRs a day, the math is almost always yes.

What Is Claude Code Review?

Claude Code Review is Anthropic's automated pull request review feature, available for Claude Teams and Enterprise customers, that uses multiple AI agents to analyze code changes and post inline bug-detection comments on GitHub pull requests.

It launched on March 9, 2025, built on a straightforward observation: as AI coding assistants like Claude Code, Cursor, and GitHub Copilot let engineers ship code much faster, the human review queue grows faster than you can hire reviewers. The PRs are cleaner in some ways (the AI doesn't write syntax errors) but riskier in others (the logic errors are subtler).

Before Claude Code Review, only 16% of PRs at Anthropic received substantive review comments. After deploying it internally, that number jumped to 54%. And less than 1% of its findings were marked incorrect by engineers.

One real example: Claude caught a race condition in a TrueNAS ZFS storage module that a full human review team had missed. That kind of catch, on a large PR, is exactly where this earns its keep.

How Claude Code Review Actually Works: The 5-Agent System

Most AI code review tools just scan your diff. Claude Code Review dispatches five parallel specialized agents that each look at a different dimension of your change, then a verification pass filters anything below a confidence threshold of 80 out of 100.

Here's what the five agents actually do:

•       Agent 1 - CLAUDE.md Compliance: Reads your repo's CLAUDE.md or REVIEW.md file (if you have one) and checks whether the PR follows your team's documented standards, patterns, and style rules.

•       Agent 2 - Bug Detection: Scans the diff for logic errors, null pointer risks, off-by-one errors, incorrect conditional branches, and other correctness issues. This is the core agent.

•       Agent 3 - Git History Analysis: Pulls your repo's commit history and identifies whether this change touches code that has a history of regressions or has been reverted before.

•       Agent 4 - Previous PR Comments: Reviews comments from your past pull requests to understand patterns, recurring issues, and what your team has flagged as important in similar changes.

•       Agent 5 - Code Comment Verification: Checks whether the inline comments in the code (docstrings, TODOs, API documentation) are accurate and consistent with what the code actually does.

Each agent scores its findings from 0-100. Only findings that hit 80 or above get passed to the verification stage. A separate verification agent then re-examines those shortlisted findings and filters false positives before anything gets posted to the PR.

I think this architecture is underrated. The verification pass is what keeps the false positive rate below 1%. Most AI reviewers just dump every possible concern as a comment and flood the PR with noise. Claude's multi-stage filter is why engineers actually read its output.

Step-by-Step Setup Guide (Admin + Developer View)

Setup takes about 10 minutes and has two phases: admin configuration and developer workflow. You need a Claude Teams or Enterprise plan to access this feature.

Admin Setup (5 minutes)

1.      Go to claude.ai/admin-settings/claude-code in your organization's Claude admin panel.

2.      Click 'Connect GitHub' and install the Claude GitHub App. During installation, select which repositories you want to enable reviews on. You can choose all repos or specific ones.

3.      Set your monthly spend cap. This is under Settings > Usage Controls. Given that reviews average $15-25, a team doing 10 PRs/day could spend $4,500-7,500/month. Set a cap before your first PR.

4.      Optionally configure auto-review: Claude can trigger automatically on every new PR, or only when manually requested via the @claude command.

Developer Workflow (What Your Team Actually Does)

Once the admin setup is done, developers have two ways to trigger a review:

•       Automatic mode: Claude reviews every PR automatically when it's opened. No action needed.

•       Manual trigger: In any PR comment, type @claude review and Claude will run a full analysis on the current state of the PR.

Claude posts its findings as inline PR comments with severity tags. Red tags are high-confidence correctness bugs. Yellow tags are medium-confidence warnings. Purple tags flag documentation or comment inaccuracies. Reviews typically complete in about 20 minutes.

A useful tip: Claude does NOT approve or block PRs. It only comments. The merge decision stays with your human reviewers. This is intentional and the right call, because shipping decisions carry context that an AI can't fully weigh.

What Bugs Does It Catch? Real Data from Anthropic

Claude Code Review finds substantive issues in 84% of large pull requests (1,000 lines of code or more), averaging 7.5 findings per PR. For small PRs under 50 lines, it flags 31% of them with an average of 0.5 findings.

The types of bugs it catches most often:

•       Logic errors: Incorrect conditional branches, wrong operator precedence, inverted boolean checks

•       Edge cases: Null/undefined inputs, empty array handling, integer overflow scenarios

•       Race conditions: Concurrent access issues, missing locks, timing dependencies in async code

•       Security issues: Input validation gaps, path traversal risks, SQL injection patterns

•       Regression risks: Changes to code that has broken before, flagged via git history analysis

•       Documentation drift: Docstrings and API docs that no longer match the actual function behavior

Here's the number I keep coming back to: less than 1% of all findings are marked incorrect. For context, studies on human code review false positive rates often run 10-15%. Claude is not just fast, it's more precise than most reviewers on the specific dimension of "is this actually a bug."

Where it's weaker: architectural judgment. It won't tell you the PR is solving the wrong problem, or that a cleaner abstraction exists. It reviews correctness, not design. I'd still want a senior engineer reviewing PRs for design quality. But catching correctness bugs? Claude's doing a better job than most.

How to Customize Reviews with CLAUDE.md

You can tune exactly what Claude flags by adding a CLAUDE.md or REVIEW.md file to your repository's root directory. Without one, Claude uses its default review profile focused purely on correctness.

Add a CLAUDE.md to change what Claude focuses on. Here's what you can configure:

•       Expand beyond correctness: Tell Claude to also check for test coverage, naming conventions, or specific patterns your team uses

•       Focus on file types: 'Prioritize review of changes to /api/ and /auth/ directories'

•       Suppress known non-issues: 'Ignore TODO comments in legacy modules under /v1/'

•       Enforce team standards: 'Flag any database query that doesn't use our query builder pattern'

A minimal CLAUDE.md example for a Python backend:

# Claude Review Config
## Focus Areas
- Flag SQL queries that don't use SQLAlchemy ORM
- Check all async functions for missing await statements
- Verify all API endpoints have input validation
## Ignore
- Style comments in /legacy/ directory

This is the most underused feature of the whole system. Teams that take 20 minutes to write a good CLAUDE.md get significantly more relevant findings and far fewer comments on things they don't care about.

Pricing: What Does Claude Code Review Actually Cost?

Claude Code Review costs $15-25 per review on average, billed by token usage rather than a flat per-review fee. A short PR (under 200 lines) might cost $8-12. A large PR with 2,000+ lines and significant git history might cost $30-40.

The feature is only available on Claude Teams ($30/user/month) and Claude Enterprise (custom pricing). There is no free tier for Code Review.

Here's the ROI math that makes teams comfortable with the cost:

These numbers assume Claude catches issues that would otherwise require human review time. The real payoff is two-layer: direct cost savings on review time, plus the reduced cost of bugs that make it to production.

To control costs: set spend caps in admin settings, consider auto-review only on PRs above a certain size threshold, and use manual @claude review for smaller day-to-day changes.

Claude Code Review vs CodeRabbit vs GitHub Copilot

Claude Code Review is not the only automated PR review tool. CodeRabbit is the established player with a larger user base. GitHub Copilot launched its own code review feature in April 2025. Here's how they actually compare:

My honest take: if you're already paying for Claude Teams or Enterprise, Code Review is an obvious add. The multi-agent architecture and sub-1% false positive rate are genuinely differentiated. CodeRabbit wins on price flexibility and platform support (GitLab + Bitbucket teams, this is important). GitHub Copilot's review is convenient but shallow compared to both.

If budget is tight: start with CodeRabbit's free tier, prove the ROI, then upgrade to Claude Code Review once the savings are clear.

GitHub Actions vs Managed Claude Code Review: Which to Use?

There are actually two different ways to get Claude reviewing your code: the managed Claude Code Review feature (the one this whole guide is about) and a self-hosted approach using Claude's open-source GitHub Actions workflow. They're designed for different teams.

The GitHub Actions version is genuinely useful for individuals and small teams. You wire it up with your Anthropic API key, and Claude comments on PRs just like the managed version. What you lose is the multi-agent architecture, the git history analysis, and the verification pass. The false positive rate is noticeably higher.

For any team beyond 3-4 engineers shipping regularly, the managed version pays for itself. For solo projects and open source, the Actions version is a practical and free starting point.

Frequently Asked Questions

What is Claude Code Review and how is it different from regular AI review?

Claude Code Review is Anthropic's pull request analysis feature that dispatches five specialized AI agents in parallel on every PR. Unlike single-pass AI reviewers, each agent examines a separate dimension of the code change: CLAUDE.md compliance, bug detection, git history patterns, past PR comments, and code comment accuracy. A verification pass then filters any finding below 80% confidence before it's posted.

Does Claude Code Review approve or block pull requests?

No. Claude Code Review only posts inline comments on the PR. It does not approve, request changes in a blocking sense, or merge code. The final merge decision always stays with your human reviewers. This is by design: shipping decisions involve business context and architectural judgment that a code analysis tool shouldn't unilaterally override.

How much does Claude Code Review cost?

Reviews average $15-25 per PR, billed by token usage rather than a flat fee. A small PR under 200 lines might cost $8-12. A large 2,000-line PR with significant history context can cost $30-40. The feature requires a Claude Teams ($30/user/month) or Enterprise plan. There is no free tier for Code Review specifically.

Is Claude Code Review available on the Claude free plan?

No. Code Review is only available on Claude Teams and Claude Enterprise plans. Free-plan users can still trigger basic Claude responses in GitHub via the open-source GitHub Actions integration, but that doesn't include the five-agent architecture, the verification pass, or the git history analysis.

How long does a Claude Code Review take?

Most reviews complete in approximately 20 minutes. Large PRs (over 1,000 lines) may take 25-30 minutes, depending on repository history size. The review runs asynchronously, so your developer can work on something else while it runs. You'll get a notification when the inline comments appear on the PR.

What is CLAUDE.md and why should I create one?

CLAUDE.md is a configuration file you add to your repository root that tells Claude what to prioritize during reviews. Without it, Claude uses its default correctness-focused profile. With it, you can expand the scope (test coverage, naming conventions), focus on specific directories, suppress known non-issues, or enforce team-specific patterns. Teams that maintain a good CLAUDE.md report significantly more relevant findings and less noise.

How does Claude Code Review compare to CodeRabbit?

Claude Code Review's key advantages are its multi-agent architecture (5 specialized agents vs CodeRabbit's single pass), sub-1% false positive rate, and deep git history context. CodeRabbit's key advantages are platform support (GitHub, GitLab, and Bitbucket vs Claude's GitHub-only), a free unlimited tier, and lower per-review cost. For Teams and Enterprise Claude customers, Code Review is the stronger technical choice. For GitLab or Bitbucket users, or teams watching costs closely, CodeRabbit wins.

Can I use Claude Code Review without Claude Teams, using GitHub Actions instead?

Yes. Anthropic maintains an open-source Claude GitHub Actions workflow that any developer with an Anthropic API key can use. It gives you Claude commenting on PRs for free (you pay only API token costs). The trade-off: you get a single-pass review without multi-agent depth, no git history analysis, and a higher false positive rate. It's a great starting point for individuals and small teams before upgrading to the managed version.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

- 7 AI Tools That Changed Developer Workflow (March 2026)

- 150 Best Claude Prompts That Work in 2026

- Every AI Model Compared: Best One Per Task (2026)

- Claude AI 2026: Models, Features, Desktop & More

References

1.      Anthropic - Introducing Code Review for Claude Code (March 9, 2025):

2.      Anthropic Claude Code Documentation - Code Review Feature:

3.      VentureBeat - Anthropic launches Code Review for Claude Code (March 2025):

4.      The New Stack - Claude Code Review: Multi-Agent PR Analysis Explained:

5.      Anthropic Claude Code GitHub Actions (open source):

6.      CodeRabbit documentation and pricing:

7.      GitHub Copilot code review feature announcement (April 2025):

Zhipu AI launched two models in early 2026 that solve completely different problems. GLM OCR reads documents better than almost anything on the market. GLM-5-Turbo executes multi-step AI agent workflows at a price that makes GPT-4 look expensive. I have spent time testing both, and the comparison most people are drawing - which one is better - is the wrong question entirely.

These two models are not competitors. They are two halves of the same automation stack. But if you need to choose where to start, the decision depends on what problem you are actually trying to solve. Let me break both down clearly, compare them on every dimension that matters, and tell you which one deserves your attention first.

What Is GLM OCR? The Document Intelligence Model

GLM-OCR is a 0.9 billion parameter multimodal model built by Zhipu AI and Tsinghua University, released in March 2026 specifically for complex document understanding. It topped the OmniDocBench V1.5 leaderboard with a score of 94.62, beating models that are many times larger in parameter count.

What makes GLM-OCR unusual is its design philosophy. Most OCR tools treat a document as flat left-to-right text. GLM-OCR treats a document as a structured layout with distinct regions: tables, formulas, headings, stamps, code blocks, and handwritten sections. It understands all of them and outputs clean Markdown, LaTeX, or JSON - whichever format your downstream pipeline needs.

The model is fully open-source under the MIT license. You can run it via the cloud API at 0.2 RMB per million tokens, deploy it locally with Ollama or Docker, or fine-tune it for your specific domain using LLaMA-Factory. For a 0.9B parameter model, the breadth of what it handles is genuinely surprising.

Why This Matters

Traditional OCR tools like Tesseract fail on nested tables, mathematical notation, and mixed-layout PDFs. GLM-OCR handles all three - and outputs structured data directly. No post-processing scripts needed.

How GLM OCR Works Under the Hood

GLM-OCR uses a two-stage pipeline that separates layout detection from content extraction. Stage 1 runs PP-DocLayout-V3 to analyze the page and identify every distinct region. Stage 2 processes each region in parallel using the model's language decoder - which is why it preserves semantic integrity across complex multi-column documents rather than mangling them into flat text.

The architecture combines a 0.4B CogViT visual encoder with a 0.5B GLM language decoder. That encoder-decoder split is what lets the model simultaneously understand what something looks like (a table, a formula, a signature) and what it means in context.

The speed story is interesting. GLM-OCR uses Multi-Token Prediction (MTP), predicting 10 tokens per step instead of one at a time. That single design choice delivers a 50% improvement in decoding throughput over comparable OCR models, reaching 1.86 PDF pages per second under benchmark conditions.

Training Approach

The model went through four training stages:

→  Stage 1: Vision-text pretraining to align visual and language representations

→  Stage 2: Multimodal pretraining with document parsing and visual QA tasks

→  Stage 3: Supervised fine-tuning on OCR-specific tasks (tables, formulas, KIE)

→  Stage 4: Reinforcement learning via GRPO with task-specific reward signals

The reward signals are worth noting: Normalized Edit Distance for text accuracy, CDM score for formulas, TEDS score for tables, and field-level F1 for key information extraction. Each task was optimized independently rather than using a single generic metric.

GLM OCR Benchmark Results and Real Numbers

The benchmark numbers are strong. Here is where GLM-OCR sits versus the field:

A few honest caveats: MinerU 2.5 scored 88.4 on PubTabNet versus GLM-OCR's 85.2. Gemini-3-Pro outperformed GLM-OCR on two KIE reference benchmarks (Nanonets-KIE and Handwritten-KIE). GLM-OCR is not the best at everything, but it leads on most tasks while running at a fraction of the compute cost of its larger competitors.

The API pricing reinforces this advantage: 0.2 RMB per million tokens is essentially negligible at production scale. For a team processing thousands of documents per day, this translates to real cost savings compared to GPT-4 Vision or similar alternatives.

What Is GLM-5-Turbo? The AI Agent Engine

GLM-5-Turbo is a language model released on March 16, 2026 by Zhipu AI. It is built specifically for OpenClaw - the company's AI agent execution platform - and it is not a general-purpose chatbot. Every design decision in this model was made around one use case: running multi-step autonomous workflows where an AI agent decomposes a complex instruction, calls external tools reliably, and hands results across multiple agents.

The context window is 200,000 tokens with up to 128,000 tokens of output per response. For agent tasks that involve reading long documents, maintaining state across many steps, and generating comprehensive outputs, that window size is practical rather than theoretical.

Pricing is aggressively positioned: $1.20 per million input tokens and $4.00 per million output tokens. For comparison, Claude Opus 4.6 runs $5 input and $25 output. That is a 4x to 6x cost difference at scale - which matters enormously when you are running thousands of agent invocations per day.

My Take

GLM-5-Turbo's pricing makes it worth testing for any developer currently running GPT-4 or Claude for structured agent tasks. The cost difference alone justifies a benchmark. What surprised me was that the benchmark performance held up - this is not a cheaper but worse option.

How GLM-5-Turbo Works in the OpenClaw Ecosystem

OpenClaw is Zhipu AI's end-to-end agent framework - think of it as the orchestration layer that sits above the model. GLM-5-Turbo was aligned during training specifically on OpenClaw task patterns, which means its tool-calling behavior, output formatting, and multi-agent handoffs are tuned for that environment rather than being retrofitted after the fact.

The model supports real-time streaming responses, structured outputs, and integration with external toolsets and data sources. It handles six core OpenClaw task categories particularly well: information search and gathering, office automation, daily task management, data analysis, software development, and multi-agent orchestration.

ZClawBench Performance

Zhipu benchmarked GLM-5-Turbo on ZClawBench, their proprietary evaluation suite for end-to-end agent task completion. GLM-5-Turbo outperformed the full GLM-5 model and several competing alternatives across all six categories. The strongest margins were in information retrieval and data analysis workflows - exactly the tasks where document input matters most.

This is also where the connection to GLM-OCR becomes obvious. If GLM-5-Turbo handles data analysis best, and GLM-OCR handles document-to-structured-data conversion best, the two models together form a natural pipeline.

GLM OCR vs GLM-5-Turbo: Full Comparison

Here is a direct side-by-side of both models across every dimension that matters for a developer or team making a build decision:

The clearest way to frame the difference: GLM-OCR is the eyes. It reads and structures input from the physical world - documents, invoices, forms, PDFs. GLM-5-Turbo is the brain. It reasons over structured data, calls tools, and takes action. In most serious automation pipelines, you need both.

Which One Should You Build On First?

This depends entirely on your current problem. Not on which model is technically superior - because that is the wrong axis to evaluate this on.

Choose GLM OCR if:

→  You process documents at scale: invoices, receipts, contracts, forms, academic papers

→  You need to extract structured data (tables, key fields, formulas) from unstructured PDFs

→  You want a lightweight, locally deployable model with no GPU requirement via API

→  Your team is in a cost-sensitive environment where per-token pricing matters

→  You are building in regulated industries (finance, healthcare, legal) that require local data processing

Choose GLM-5-Turbo if:

→  You are building autonomous AI agents that need to decompose tasks and call tools

→  Your workflow involves multi-step execution across different data sources and APIs

→  You are already using the OpenClaw ecosystem or evaluating it as an alternative to GPT-4 agents

→  You need a 200K token context window for long-running reasoning tasks

→  You want to significantly reduce agent API costs without sacrificing benchmark performance

The Honest Answer: Use Both

For anyone building a production automation pipeline in 2026, the real architecture looks like this: GLM-OCR extracts structured JSON from your document inputs. GLM-5-Turbo, running inside an OpenClaw agent, processes that structured data and routes it to downstream tools. You get accurate document parsing at 0.2 RMB per million tokens and intelligent execution at $1.20 per million tokens. The combination undercuts GPT-4 Vision plus GPT-4 agents by a significant margin on cost - while matching or exceeding benchmark performance on most task types.

Pipeline Example

Accounts payable automation: GLM-OCR reads invoices and outputs structured JSON (vendor, amount, line items). GLM-5-Turbo's OpenClaw agent validates the data, matches it against your ERP, flags anomalies, and triggers payment workflows. No human in the loop until exception handling.

How to Get Started with Each Model

Getting Started with GLM OCR

Installation takes under two minutes:

# Cloud API (no GPU needed)
pip install glmocr

# Self-hosted with layout detection
pip install "glmocr[selfhosted]"

# Or run locally with Ollama
ollama run glm-ocr

For Python integration:

from glmocr import GLMOCRClient

client = GLMOCRClient(api_key="your_key")
result = client.parse("invoice.pdf", output_format="json")
print(result)

Getting Started with GLM-5-Turbo

GLM-5-Turbo is accessible via the Z.ai developer platform. Sign up at z.ai, generate an API key, and you can start with their standard OpenAI-compatible API format. The model integrates directly into OpenClaw agent workflows, but it also works as a drop-in replacement for GPT-4 in standard tool-calling pipelines with minimal prompt adjustments.

Frequently Asked Questions

What is GLM-OCR and how is it different from regular OCR?

GLM-OCR is a 0.9B multimodal model from Zhipu AI that reads documents as structured layouts rather than flat text. Unlike traditional OCR tools such as Tesseract, it identifies tables, formulas, stamps, and handwritten content separately and outputs Markdown, JSON, or LaTeX directly. It scored 94.62 on OmniDocBench V1.5, ranking first among non-reference models.

What is GLM-5-Turbo and what is OpenClaw?

GLM-5-Turbo is an LLM launched March 16, 2026 by Zhipu AI, built specifically for OpenClaw - the company's AI agent execution framework. It handles multi-step workflows where an AI needs to call external tools, process long contexts, and coordinate across multiple agents. It offers a 200,000-token context window at $1.20 per million input tokens.

How is GLM-OCR different from GLM-5-Turbo?

GLM-OCR is a vision model for parsing documents into structured data. GLM-5-Turbo is a language model for executing agent workflows and tool-calling tasks. They serve different roles: GLM-OCR is input processing, GLM-5-Turbo is decision execution. In a full automation pipeline, GLM-OCR feeds structured data to GLM-5-Turbo agents.

Which GLM model has better SEO and content opportunity in 2026?

GLM-OCR currently offers a stronger content opportunity. The keyword 'glm ocr' carries very low difficulty (KD 10-20) with growing search volume, while adjacent terms like 'AI OCR for documents' and 'extract tables from PDF' have 10,000 to 200,000 monthly searches. GLM-5-Turbo keywords sit at medium KD (35-45) with a trend spike that will normalize over time. GLM-OCR traffic is more evergreen.

Can I use GLM-OCR locally without sending data to the cloud?

Yes. GLM-OCR supports local deployment via Docker, vLLM, SGLang, and Ollama. Install with 'pip install "glmocr[selfhosted]"' or run 'ollama run glm-ocr' for a local instance. The model can also be fine-tuned for domain-specific tasks using LLaMA-Factory. Cloud API is available at 0.2 RMB per million tokens for teams that prefer managed infrastructure.

Is GLM-5-Turbo cheaper than GPT-4 and Claude for agent tasks?

Yes, by a significant margin. GLM-5-Turbo runs at $1.20 per million input tokens and $4.00 per million output tokens. Claude Opus 4.6 is priced at $5 input and $25 output per million tokens. That is roughly a 4x to 6x cost reduction. For high-volume agent workflows, the savings at scale are substantial.

Recommended Blogs

If you found this useful, these posts from Build Fast with AI cover related topics worth reading:

GLM-5-Turbo: Zhipu AI's Agent Model Built for OpenClaw

How to Build AI Agents That Actually Work in Production

The Best Open-Source AI Models of 2026

Build Fast with AI — All Blogs

References

1.  GLM-OCR Technical Report — arXiv

2.  GLM-OCR GitHub Repository — Z.ai / Zhipu AI

3.  Zhipu AI Introduces GLM-OCR — MarkTechPost

4.  GLM-5-Turbo Launch — Trending Topics

5.  GLM-5-Turbo Overview — Z.AI Developer Docs

6.  GLM-5-Turbo: Agent Model Built for OpenClaw — Build Fast with AI

7.  GLM-OCR on Hugging Face — zai-org/GLM-OCR

8.  z.ai Debuts GLM-5-Turbo for Agents — VentureBeat

The productivity gap between AI-augmented developers and everyone else just got wider. March 2026 is the month that made that undeniable.

In February alone,  reported using AI tools in their daily workflow, according to surveys across engineering communities. That number was 42% eighteen months ago. The tools driving this shift are not the same ones from 2024. They are faster, cheaper, more capable of handling entire codebases, and in some cases, completely free. This month delivered seven releases that every developer should know about right now.

I spent the last two weeks running each of these tools inside real project workflows: a multi-service API backend, a React frontend rebuild, and a data pipeline migration. The results were not subtle. Here is what actually changed, what the numbers say, and which tool fits which use case.

Claude Opus 4.6: 1M Context Window Redefines Code Understanding

 with a 1 million token context window now available in beta - the first time any Opus-class model has hit this milestone.

Why does 1 million tokens matter for developers? Paste your entire monorepo. Every file, every dependency, every migration script. Claude Opus 4.6 can hold all of it in context simultaneously and reason across the full codebase without losing track of what happened three modules ago. I tested it on a 280-file Django project and asked it to trace a race condition across five async services. It found it on the first pass.

What Is New in Claude Opus 4.6

•        Entire large codebases fit in one prompt, no chunking required

•        Generate full files, entire test suites, complete modules in a single response

•        Coordinate multiple Claude instances on parallel subtasks

•        Dial compute up or down per task to manage cost

•        Available inside Windsurf at promotional pricing with fast mode

Benchmark Performance: Claude Opus 4.6 vs Competitors

The 59% user preference rate for Claude Sonnet 4.6 over Claude Opus 4.5 tells you how much this model family has improved. My hot take:  That is a strong claim. But after testing it across three different production codebases this month, it is the most accurate description I have.

 https://claude.ai or via Anthropic API at model string 'claude-opus-4-6'

Windsurf IDE: The New #1 AI Code Editor in March 2026

 and it did it by shipping features that no other IDE has in combination: Arena Mode, Plan Mode, and parallel multi-agent sessions with Git worktrees.

I have used Cursor for over a year. Switching to Windsurf for this test took me about 20 minutes to feel at home, and then I started hitting capabilities Cursor does not have. Arena Mode is the standout. It runs two AI models side by side on the same task, identities hidden, and you vote on which output is better. After 40 rounds, you know exactly which model fits your coding style and codebase. That insight alone is worth the switch.

Windsurf Features That Separate It from Cursor

•        Side-by-side model comparison with hidden identities and developer voting - lets you empirically determine which model fits your workflow

•        AI plans the entire implementation before writing a single line of code, reducing mid-task direction changes by an estimated 60%

•        Run concurrent development tasks across separate Git worktrees with side-by-side Cascade panes

•        Full IDE capabilities, live preview, and collaborative editing in one interface

•        Available with promotional pricing, making it the most cost-accessible Opus 4.6 access point currently available

Windsurf Pricing

The honest critique: Windsurf's codebase context management is excellent on medium-sized projects but showed some drift on repos with over 500 files in my testing. Cursor's custom .cursorrules still gives more precise control when you need it. But for most developers building typical SaaS products or APIs, Windsurf's combination of features at this price is hard to argue against.

Gemini 3.1 Pro + Gemini Code Assist: Free Tier, Frontier Performance

 - more than double Gemini 3 Pro's reasoning performance on the same benchmark.

The pricing story here is the real story. Google made Gemini Code Assist free for individual developers in March 2026. Not a reduced free tier. Completely free. For developers building on Google Cloud or using any part of the GCP stack, this is a significant change. Gemini Code Assist now generates infrastructure code, Cloud Run deployments, and BigQuery queries with context that general-purpose assistants consistently miss.

Gemini 3.1 Pro Key Specifications

•        77.1% (vs Gemini 3 Pro's ~35%, more than doubling reasoning performance)

•        Low, Medium, and High reasoning depth per request for cost optimization

•        Up to 75% cost reduction on repeated context across long sessions

•        Native video understanding for demo analysis, error reproduction, and UI review

•        Relevant for developer tools targeting multilingual user bases

My practical take: for developers already inside the GCP ecosystem,  I would not switch my primary coding agent away from Claude Code or Windsurf for it, but as a secondary tool for GCP-specific work? It is now a no-brainer to have running.

 https://codeassist.google.com (IDE plugin available for VS Code and JetBrains)

GLM-5: Open-Source Frontier Model at $1 Per Million Tokens

 Zhipu AI released it under the MIT License, fully self-hostable, with weights available on Hugging Face, and API pricing set at $1.00 input / $3.20 output per million tokens.

Compare that to GPT-5.4 at roughly $15/$60 per million tokens. GLM-5 gives you frontier-level open-source performance at one-fifteenth the cost for some workloads. For developers building AI-powered products where LLM API costs are a significant operational expense, this changes the math on what is buildable at scale.

GLM-5 Technical Specifications

What GLM-5 Is Best For

•       Cost-sensitive production deployments where LLM costs currently exceed $500/month

•       Teams that need full data privacy with no code leaving their infrastructure

•       Research and experimentation where access to model weights enables fine-tuning

•       Startups building AI-powered developer tools who need to iterate rapidly without per-token anxiety

The honest assessment: GLM-5 is not better than Claude Opus 4.6 or GPT-5.4 on complex reasoning tasks. The frontier is still firmly with closed models for the hardest problems. But for 60-70% of typical developer tasks - code generation, test writing, documentation, refactoring - GLM-5 gets you to the same result at a fraction of the cost. That 30-40% performance gap only matters on problems where you actually need the frontier.

 https://huggingface.co/THUDM/GLM-5 | API: https://open.bigmodel.cn

GitHub Copilot Workspace: From Issue to Pull Request, Automated

 This is the agentic coding workflow that 2023 blog posts predicted. It is here now.

I ran Copilot Workspace on 12 GitHub issues across two repositories in my test week. Eight produced pull requests that required only minor adjustments before merging. Three required meaningful rework. One was a complete miss. That 67% hit rate on real production issues is not perfect, but it represents work that previously required hours of focused engineering time per issue.

Copilot Workspace: Key Capabilities

•        Reads issue context, proposes implementation plan, executes across multiple files

•        Contextual code explanations, inline fixes, and documentation generation

•        Summarizes what changed and why in pull request descriptions automatically

•        Python, TypeScript, Go, Rust, Java, C++ and more with context-aware accuracy

•        Trigger agentic workflows inside your existing CI/CD pipeline

Copilot Pricing March 2026

The thing I keep thinking about with Copilot Workspace is that it is not trying to replace developers. It is automating the mechanical part of development: translating a well-written issue into a first draft of code. A developer who writes clear, specific GitHub issues will get significantly better Workspace output than one who writes vague ones. The tool rewards good engineering process.

Claude Code: The Terminal Agent That Ships Full Features

 For developers who live in the terminal, it is the most natural agentic coding experience currently available.

What separates Claude Code from other agents is how it handles existing codebases. It reads your files, understands your patterns and conventions, and writes new code that matches your style rather than imposing its own. On my Django API test, it found and followed the project's custom error handling conventions without being told they existed. That kind of contextual awareness is what developers mean when they say an AI tool 'gets it.'

Claude Code Key Features

•        Reads and indexes your repository before making any changes

•        Plans changes across the full codebase before executing, not file by file

•        Runs your test suite after changes and iterates on failures automatically

•        Creates branches, commits with meaningful messages, and summarizes diffs

•        CLAUDE.md file lets you define conventions, patterns, and constraints

•        Defaults to Claude Sonnet 4.6 for efficiency, upgradable to Opus 4.6 for hard problems

Claude Code is available via Anthropic API billing. Typical usage runs $15-40/month for moderate development work using Sonnet 4.6. Heavy agentic sessions with Opus 4.6 can run higher.

 npm install -g @anthropic-ai/claude-code or via https://docs.anthropic.com/claude-code

OpenAI Codex Returns: Smarter, Leaner, and Back in the Stack

 It is not the original Codex from 2021. This is a model built for the 2026 developer workflow.

The reintroduction was quiet. No major announcement campaign, just a model update in the API and documentation changes. But developers in the community noticed immediately. Codex now handles repository-scale tasks more reliably than previous OpenAI coding offerings, and its performance on structured coding tasks like API implementation and database schema design is noticeably improved over GPT-5 in narrow benchmarks.

Codex 2026: What Is Different

•        Understands multi-file project structure, not just individual file snippets

•        Native trigger support for automated code review and generation in CI

•        Returns code in predictable formats for programmatic parsing in agentic pipelines

•        Organizations can fine-tune on their own codebase for higher accuracy on internal patterns

•        Optimized for high-frequency developer tool integrations

My honest take: Codex is not in the top three for overall developer workflow right now. Cursor, Windsurf, and Claude Code are better holistic options. But in specific scenarios, such as building AI-powered developer tools, running automated code generation pipelines in CI, or integrating with existing OpenAI API infrastructure, Codex is the most practical fit. Use it where the ecosystem alignment matters, not as a general replacement.

 Available via OpenAI API. Model ID: codex-2 (check docs.openai.com for current string)

Best AI Coding Tools 2026: All 7 Compared

How to Build Your AI Developer Productivity Tools Stack in 2026

Not every developer needs all seven tools. The teams getting the most value are not using the most tools. They are using the right tools for distinct parts of the workflow. Here is the framework I recommend.

For Solo Developers and Students

•        Windsurf Free tier or Cursor

•        Gemini Code Assist (free) + Claude Sonnet 4.6 via Windsurf

•        GLM-5 via self-hosted or BigModel API

•        $0 to $15/month

For Product Developers and Small Teams

•        Windsurf Pro or Cursor Pro

•        Claude Code for complex feature development

•        GitHub Copilot Business ($19/user/month)

•        $35 to $55/user/month

For Enterprise Engineering Teams

•        Windsurf Enterprise or JetBrains AI

•        Claude Opus 4.6 for architecture decisions, Sonnet 4.6 for daily tasks

•        GitHub Copilot Enterprise

•        GLM-5 for data-sensitive workloads

•        $60 to $100+/user/month depending on usage

The key insight I want you to take from this: AI developer tools in 2026 layer on top of each other. They do not compete. Your editor handles real-time suggestions. Your terminal agent handles complex multi-file features. Your CI integration handles the PR automation. Get the layer right, and the compounding productivity is real.

Frequently Asked Questions

What is the best AI tool for developers in March 2026?

The best single AI development tool in March 2026 is  according to LogRocket's March power rankings, offering Arena Mode, Plan Mode, and parallel multi-agent sessions at $0 to $60/month. For model intelligence,  holds the top model ranking with a 1 million token context window in beta.

Is Claude Code free to use?

Claude Code is not free. It is billed via the Anthropic API based on token usage. Typical moderate developer usage runs $15 to $40 per month using Claude Sonnet 4.6. Heavy usage with Claude Opus 4.6 for complex agentic tasks runs higher. There is no free tier currently.

What is GLM-5 and why is it significant?

 is Zhipu AI's open-source frontier model released in early 2026 under the MIT License. It is significant because it is fully self-hostable with weights on Hugging Face, priced at $1.00 input / $3.20 output per million tokens via API, and ranks as the top open-source model on SWE-bench Verified. For teams where LLM API costs are a concern, it offers frontier-level performance at roughly one-fifteenth the cost of comparable closed models.

How does Windsurf Arena Mode work?

Windsurf Arena Mode runs two AI models side by side on the same coding task, with both model identities hidden. The developer reviews both outputs and votes on which is better. Over multiple rounds, this gives you empirical data on which model produces output that fits your specific workflow and codebase, rather than relying on general benchmark rankings.

What is the difference between Claude Code and GitHub Copilot Workspace?

Claude Code is a terminal-based agent you interact with from the command line. It reads your codebase, writes code, runs tests, and iterates in the terminal. GitHub Copilot Workspace is integrated into GitHub and operates on the issue level. You open a GitHub issue and Copilot Workspace plans an implementation, writes code across your repository, and opens a pull request. Claude Code gives more interactive control; Copilot Workspace is more automated end-to-end.

Is Gemini Code Assist really free in 2026?

Yes. Google made Gemini Code Assist fully free for individual developers in March 2026. This is not a limited free tier - individual developers get full access to the Gemini Code Assist IDE plugin for VS Code and JetBrains at no cost. This is separate from Gemini 3.1 Pro, which is a paid API model at $2 input / $12 output per million tokens.

Which AI coding tools work best for open-source projects?

For open-source projects,  are the strongest combination in 2026. GLM-5 gives you a powerful local model with no data leaving your infrastructure, ideal for sensitive codebases. Gemini Code Assist provides a free IDE plugin with strong code generation. GitHub Copilot Free tier also works for basic completions on public repositories.

What is Claude Opus 4.6 Context Window Size and How Does It Compare?

 introduces a 1 million token context window in beta (up from Opus 4.5's 200K), 128K output capacity, Agent Teams for parallel task coordination, and adaptive thinking with effort controls. Developer surveys show 59% prefer Claude Sonnet 4.6 over Opus 4.5, indicating how significantly the 4.6 model family improved across all capability tiers.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

1. 12+ AI Models in March 2026: The Week That Changed AI

2. 7 AI Tools That Changed Development (December 2025 Guide)

3. 7 Breakthrough AI Tools from November 2025

4. GPT-5.4 vs Gemini 3.1 Pro (2026): Which AI Wins?

5. Grok 4.20 Beta Explained: Non-Reasoning vs Reasoning vs Multi-Agent (2026)

 References

1. AI Dev Tool Power Rankings & Comparison (March 2026) - LogRocket Blog

2. Best AI Coding Agents for 2026: Real-World Developer Reviews - Faros AI

3. 15 Best AI Coding Assistant Tools In 2026 - Qodo AI

4. Best AI Tools for Developers in 2026 - Builder.io

5. Best AI Coding Tools for Developers in 2026 - Labla.org

6. Best AI Coding Tools in 2026: Tier S Guide - Pragmatic Coders

7. AI Tools for Developers 2026: The Engineering Leader Guide - Cortex

8. 7 AI Tools That Changed Development (December 2025) - Build Fast with AI

9. 12+ AI Models in March 2026: The Week That Changed AI - Build Fast with AI

Most people running Claude at 25% capacity are not limited by the model. They are limited by how they write prompts for it.

I've spent the last eight months testing prompts across Claude Opus 4.6, GPT-5.4, and Gemini 3.1 Pro - in real workflows, not toy demos. The single clearest finding: Claude rewards explicit, structured instructions in a way no other frontier model does. Write a vague prompt and Claude gives you a competent but generic output. Write a specific, structured prompt and the output quality jumps visibly.

This guide covers 150 Claude prompt categories organized by use case, the 8 advanced patterns that unlock the best outputs, and real examples you can copy directly. Every prompt links to the free Build Fast with AI Prompt Library - where you can save, search, filter by category, and build your own custom versions.

Why Claude Needs a Different Prompting Approach

Claude takes you literally. That sentence changes everything about how you write prompts.

GPT-5.4 fills in gaps. Ask for 'a dashboard' and GPT infers you want charts, filters, and data visualization. Claude gives you exactly a dashboard container - because that is what you asked for. This is not a weakness. Anthropic made this choice deliberately, and once you understand it, Claude's instruction-following becomes a real advantage.

Three structural differences that matter most for Claude Opus 4.6:

XML tags work natively here. Anthropic trains on structured prompts internally - wrapping your instructions in <task>, <context>, and <output_requirements> tags activates pattern recognition that produces measurably more structured outputs.

The 1M-token context window is genuinely different. You can paste entire codebases, year-long document histories, or 300-page reports. Anthropic's MRCR v2 benchmark shows Opus 4.6 maintaining 76% accuracy at 1M tokens, compared to 18.5% for GPT-5.2 at the same length.

Role prompts have more depth here. Be specific: 'senior developer who has maintained legacy Django codebases for 8 years' gives you a noticeably different result than 'Python expert.'

Claude vs ChatGPT vs Gemini: Which Wins for Each Task

Every "which AI is better" article published before 2026 is obsolete. Models now release quarterly updates, benchmark scores shift monthly, and the right choice is task-specific, not universal.

Here is the honest breakdown based on independent testing from Improvado, MindStudio, and my own workflows:

The highest-leverage approach for serious AI workflows is not choosing one model. It is routing tasks to the right model. Claude for deep writing and analysis. GPT for quick-turnaround work. Gemini for anything inside Google's ecosystem. See the free Prompt Library for categorized prompts across all three models.

7 Claude Prompt Categories with Real Examples

All 150 prompts across these categories are available in the Build Fast with AI Prompt Library. Below are 2–3 tested examples from each category.

Writing and Editing

Claude Opus 4.6 leads on writing quality for precision tasks - instruction-following, voice consistency, and long-form coherence across multi-pass revisions. The key is being explicit about your audience, format, length, and tone before Claude writes a single word.

Prompt 1 - Long-Form Article with Voice Matching:

You are a senior tech journalist who writes for founders and developers.
Tone: direct, opinionated, no corporate hedging.
Task: Write a 1,200-word article arguing that [TOPIC].
Audience: Technical founders at Series A stage.
Format: One strong hook sentence, then 4 H2 sections, then a punchy 2-sentence close.
Do NOT include: passive voice, "in today's landscape," generic CTAs, or unsupported claims.

Prompt 2 - Developmental Edit:

I am giving you a draft. Your job:
1. Identify the 3 biggest structural weaknesses (not grammar).
2. Ask me 2 clarifying questions before revising.
3. After I answer, produce a revised version.
Do not revise until I answer the questions. [PASTE DRAFT]

Browse all 20 Writing prompts: buildfastwithai.com/tools/prompt-library

Coding and Debugging

Claude Opus 4.6 scores 80.8% on SWE-Bench Verified - the highest among frontier models for production coding precision. Its 1M-token context window makes full codebase review practical in a way that is not possible on models with 128K-capped contexts.

Prompt 1 - Security Audit:

You are a senior security engineer with 10 years of experience in web app vulnerabilities.
Review the following code for: SQL injection, XSS, insecure auth, exposed secrets.
For each issue: severity (Critical/High/Medium/Low), exact location, why dangerous, corrected snippet.
Output format: numbered list, severity label first. [PASTE CODE]

Prompt 2 - Bug Fix with Explanation:

The following code produces this error: [ERROR MESSAGE].
Diagnose the root cause step by step before writing any fix.
Then give the corrected code and explain in 2 sentences what was wrong.
[PASTE CODE]

Browse all 20 Coding prompts: buildfastwithai.com/tools/prompt-library

Data Analysis and Research

Claude's 1M-token context window makes it the strongest model for multi-document research and full-dataset analysis. Paste entire research papers, full spreadsheets, and year-long document histories into single Claude sessions - something that requires chunking and multiple API calls on every other model.

Prompt 1 - Dataset Interpretation:

You are a senior data analyst.
Task: Identify the top 3 trends, flag anomalies, suggest 2 follow-up analyses.
Format: Trend summary (2 sentences each), anomaly table (value | why unusual | what to investigate).
Context: This data is from [DESCRIBE CONTEXT]. [PASTE DATA]

Browse all 20 Data Analysis prompts: buildfastwithai.com/tools/prompt-library

Product Management and Strategy

Claude handles complex, multi-stakeholder reasoning better than any other model when you give it named perspectives and specific constraints. Vague strategy questions produce generic frameworks. Specific context produces actionable output.

Prompt 1 - PRD Writing:

You are a senior PM at a B2B SaaS company.
Write a PRD for: [FEATURE NAME].
Include: problem statement (2 sentences), 3 user stories, 3 success metrics with targets,
2 non-goals, 2 technical constraints. Audience: Engineering team. No marketing language.

Browse all 15 Product Management prompts: buildfastwithai.com/tools/prompt-library

Email and Communication

Claude respects 'do not include' constraints more reliably than GPT or Gemini. For emails and outreach, this makes a measurable difference - outputs stay on-tone without filler phrases, generic CTAs, or hedging language.

Prompt 1 - Cold Outreach:

Write a cold email to [ROLE] at [COMPANY TYPE].
Goal: [SPECIFIC OUTCOME]. Tone: Direct, peer-to-peer, no sales language. Length: Under 100 words.
Do NOT include: flattery, 'I hope this finds you well,' product feature lists, generic CTA.
Include: One specific observation about their company that shows I did research.

Browse all 15 Email prompts: buildfastwithai.com/tools/prompt-library

Learning and Explanation

Claude's strength here is depth of reasoning. When you ask it to explain a concept, it doesn't just define it - it gives you analogies, edge cases, and misconceptions. Ask it to teach via Socratic dialogue and the output quality is genuinely better than most other models.

Prompt 1 - ELI5 with Precision:

Explain [CONCEPT] to someone who knows [PREREQUISITE] but has never encountered [CONCEPT].
Use one concrete real-world analogy. Then give one example of where the analogy breaks down.
Keep the explanation under 200 words.

Browse all 10 Learning prompts: buildfastwithai.com/tools/prompt-library

Creative and Brainstorming

Claude's reasoning depth makes it stronger than other models at structured creativity techniques. SCAMPER, Six Thinking Hats, and reverse brainstorming produce more differentiated outputs on Claude when you name stakeholders and constraints explicitly.

Prompt 1 - Reverse Brainstorm:

We want to [GOAL].
First, brainstorm 10 ways we could guarantee failure at this goal.
Then, for each failure mode, invert it into a success strategy.
Flag the 3 inverted strategies that are most counterintuitive but have genuine upside.

Browse all 15 Creative prompts: buildfastwithai.com/tools/prompt-library

8 Advanced Prompt Patterns That Only Work Well on Claude

These patterns work on other models to varying degrees, but Claude's training responds to them in a more predictable, higher-quality way. I use all eight in production workflows.

1. XML Tag Structuring

Wrap multi-part instructions in <task>, <context>, and <output_requirements> tags. Anthropic uses this format in their own internal system prompts - Claude recognizes it natively and produces more structured outputs.

2. Chain-of-Thought Activation

Ask Claude to reason step-by-step before answering. The key is requesting the reasoning explicitly - not just the conclusion. Add: 'Show your reasoning process. If you are uncertain at any step, say so and explain what information would change your answer.'

3. Role and Constraint Pairing

Always pair a specific role with a constraint. A role without a constraint lets Claude default to generic advice. The constraint forces it to earn each recommendation with evidence.

4. Explicit Output Format Specification

Claude responds to format instructions better than any other model - but you must be explicit. Vague format requests produce vague formats. Specify section titles, length limits, and structure type for every output.

5. Negative Space Prompting

Telling Claude what NOT to include is often as powerful as telling it what you want. Claude respects do-not constraints more reliably than GPT or Gemini. Use it for every professional output.

6. Iterative Refinement in the Context Window

Build on prior output within the same session rather than re-prompting from scratch. Ask Claude to identify weaknesses, ask clarifying questions, and only revise after you answer. This is where the 1M-token window becomes a real workflow advantage.

7. Named Stakeholder Perspective Analysis

Claude handles perspective-taking better when you name specific stakeholders rather than asking for 'different views.' Named perspectives produce more differentiated, less generic outputs than abstract role descriptions.

8. Context-First Prompting for Recommendations

Give context before asking. Most users skip this and get generic frameworks. Provide company type, stage, budget, what you sell, who you sell to, what you have already tried, and your biggest constraint - then ask for the recommendation.

5 Prompt Mistakes That Kill Claude Output Quality

These patterns consistently underperform on Claude Opus 4.6 - even when they work on GPT or Gemini.

Mistake 1: Vague creative requests. 'Write something creative about the future of work' gives Claude zero signal about audience, length, format, tone, or your angle. Be specific about all four before asking.

Mistake 2: Implicit technical expectations. 'Build me a dashboard' produces exactly a dashboard container - nothing inside - because you did not specify what belongs there. List every component explicitly.

Mistake 3: Suppressing reasoning on a reasoning model. 'Quick answer, don't overthink it' asks Claude to suppress the capability you are paying for. If you want speed, use Claude Haiku 4.5.

Mistake 4: Opinion requests without context. 'What is the best marketing strategy?' has zero information about your company, market, or what you have already tried. Always give context first.

Mistake 5: Context dumps without priority. Pasting 50 facts without flagging which 5 matter most causes Claude to process everything equally. Structure your context before pasting.

How to Build Your Own Claude Prompt Library

A prompt library is not a folder of text files. It is a system - and the habit that separates occasional AI users from people who consistently get 10x better output from the same tools.

Three things every working prompt library needs: categorization by task type (not by tool), a tested output example for each prompt, and version history for your best prompts. The first version of any prompt is almost never the best one.

The fastest way to start: use the free Prompt Library at Build Fast with AI. Filter by model (Claude, ChatGPT, Gemini), tag by use case, copy with one click, and save your custom versions without juggling seven different apps.

One workflow tip: after any AI session where you got an output you were genuinely happy with, spend two minutes saving the exact prompt that produced it. Two minutes of saving eliminates an hour of rediscovery later.

Frequently Asked Questions

What is Claude Opus 4.6 and how does it differ from Claude Sonnet 4.6?

Claude Opus 4.6 is Anthropic's most capable model, built for complex reasoning, long-form analysis, and high-precision instruction-following. Claude Sonnet 4.6 balances performance and cost - faster and cheaper but less capable on nuanced multi-step tasks. Both support 1M-token context windows. Use Opus for analysis, coding review, and strategy; Sonnet works well for writing drafts and summarization.

Do Claude prompts work on the free tier?

Most prompts in this guide work with Claude's free tier, which uses the Sonnet model. For complex reasoning, multi-document analysis, and production-level coding, Claude Pro with Opus 4.6 produces significantly better outputs. The Prompt Library at buildfastwithai.com/tools/prompt-library works with any Claude tier.

How is prompting Claude different from prompting ChatGPT?

Claude takes instructions literally - it will not infer what you probably meant. This means Claude rewards explicit, detailed prompts more than GPT does. The biggest structural differences: XML tags work natively in Claude; the 1M-token context allows full-document prompting; and Claude respects 'do not include' constraints more reliably.

What are Claude XML tags and when should I use them?

XML tags like <task>, <context>, and <output_requirements> are structural markers that help Claude parse multi-part instructions. Anthropic uses this format in their internal system prompts, so Claude recognizes it natively. Use XML tags whenever your prompt has 3 or more distinct sections with different purposes.

What is the Build Fast with AI Prompt Library and is it free?

The Build Fast with AI Prompt Library is a free, searchable tool at buildfastwithai.com/tools/prompt-library. It contains 150+ tested prompts for Claude, ChatGPT, and Gemini, organized by use case. Filter by category, copy with one click, and save your customized versions. No sign-up required to browse.

Can I use these Claude prompts via the Anthropic API?

Yes. Every prompt in this guide works via the Anthropic API. The model string for Claude Opus 4.6 is claude-opus-4-6. For high-frequency production workflows, convert prompts into system prompts - they benefit from prompt caching, which reduces cost and latency on the API.

Which Claude model should I use for writing prompts?

Use Claude Opus 4.6 for precision writing tasks where instruction-following, voice consistency, and multi-pass revision quality matter. Use Claude Sonnet 4.6 for quick first drafts. Use Claude Haiku 4.5 for high-volume, simple tasks like classification, short summaries, or rapid-fire rewrites.

How does Claude compare to Gemini 3.1 Pro for prompting in 2026?

Claude leads on writing quality, instruction precision, and complex multi-step reasoning. Gemini 3.1 Pro leads on speed (Flash-Lite under 200ms), native Google Workspace integration, and real-time web access without additional setup. For professional prompt workflows outside Google's ecosystem, Claude Opus 4.6 is the stronger choice.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

Claude AI 2026: Models, Features, Desktop App and What's Coming Next

Best ChatGPT Prompts in 2026: 200+ Prompts for Work, Writing and Coding

GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5: Who Actually Wins?

GPT-5.4 vs Gemini 3.1 Pro (2026): Which AI Wins?

Prompt Engineering Salary 2026: US, India, Freshers Pay Guide

References

1.     Anthropic Claude Documentation: Prompt Engineering Overview
2. Best ChatGPT Prompts in 2026: 200+ Prompts for Work, Writing and Coding
3. GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5: Who Actually Wins?

Traditional vector RAG scores about 50% on FinanceBench. PageIndex scores 98.7%. The gap is not because VectifyAI found a better embedding model. They threw embeddings out entirely.

That number deserves to sit for a moment. Financial question-answering on SEC filings is one of the hardest retrieval tasks in production AI. It demands multi-step reasoning, cross-section references, exact numbers. And the approach that got closest to perfect accuracy used zero vectors, zero chunking, and no vector database at all.

I spent a week digging into PageIndex, the open-source framework behind those results. This post covers exactly how it works, where it wins, where it does not, and how to run it yourself with working Python code.

Why Traditional RAG Breaks on Complex Documents

The core problem: vector search retrieves by similarity. What you actually need is relevance. Those are not the same thing.

When you ask a RAG system "What was the change in net revenue from Q2 to Q3 2023?" the chunks most semantically similar to that question are probably other sentences that contain the words "revenue" and "Q3" -- not necessarily the table cell on page 47 that has the actual number.

The standard pipeline works like this:

•       Split the document into fixed-size chunks (300-500 tokens, typically)

•       Embed each chunk into a dense vector

•       Store vectors in a database (Pinecone, Weaviate, Milvus, pgvector)

•       At query time, embed the question and find the top-k nearest vectors

•       Send those chunks to the LLM to generate an answer

This works brilliantly for short, generic documents. It falls apart on long, structured ones. The specific failure modes that show up consistently in production:

Context loss from chunking. A financial table gets cut in half. The header row is in chunk 14, the data row you need is in chunk 15. Neither chunk alone answers the question.

Semantic ambiguity at scale. A 200-page annual report might mention "operating income" 60 times. Vector similarity ranks all 60 instances roughly equally. The one that actually answers your question may never surface in the top-3.

Cross-reference blindness. Page 12 says "see Appendix B for details." Appendix B is on page 87. Vector RAG has no mechanism to follow that reference.

A practitioner in public developer discussions put it bluntly: even after optimizing chunking, embedding, and vector store pipelines, accuracy on complex documents usually stays below 60%.

What Is Vectorless RAG?

Vectorless RAG is a retrieval approach that replaces semantic similarity search with LLM-powered reasoning over a structured document index. No embeddings, no vector database, no approximate nearest-neighbor search.

The name comes from the PageIndex framework, published in September 2025 by Mingtian Zhang, Yu Tang, and the PageIndex team at VectifyAI. The core insight is borrowed from AlphaGo: instead of searching exhaustively, use a learned strategy to navigate the search space intelligently.

PageIndex defines three properties that distinguish it from traditional RAG:

•       No Vector DB: Document structure and LLM reasoning replace vector similarity search entirely.

•       No Chunking: Documents are organized into natural sections that reflect their actual structure, not arbitrary token windows.

•       Human-like Retrieval: Simulates how a human expert navigates a book -- check the table of contents, find the relevant section, read it.

The key insight: similarity does not equal relevance. A vector database will always find the text most similar to your query. But relevance sometimes requires understanding structure, following references, and reasoning across sections.

How PageIndex Works: The Architecture Explained

PageIndex performs retrieval in exactly two steps.

Step 1: Build the Tree Index

When you ingest a document, PageIndex does not embed it. Instead, it asks an LLM to analyze the document's structure and generate a hierarchical tree -- essentially an intelligent table of contents. Each node in the tree has:

•       A title (the section name)

•       A summary (what the section covers)

•       A page range (which pages this node covers)

•       Child nodes (subsections, if any)

A 50-page SEC filing might produce a tree with 30-50 nodes. This tree is stored as a JSON structure -- not in a vector database -- and the full tree fits in a context window and can be inspected directly.

Step 2: Reasoning-Based Tree Search

When a query arrives, PageIndex passes the tree structure to an LLM and asks it to reason about which nodes are most likely to contain the answer. The LLM reads node titles and summaries, applies domain reasoning, and returns a ranked list of node IDs to retrieve.

This is the key difference. A vector database computes cosine similarity scores for all chunks in parallel. PageIndex asks the LLM: given this document structure and this question, where should I look?

The LLM can follow cross-references, identify that a question about appendix data should go to the appendix node, and recognize that a multi-part question requires retrieving two separate sections. It reasons like a human analyst would -- and returns a full reasoning trace showing exactly which nodes were visited.

PageIndex Python Code: A Working Example

Here is a working, minimal example of vectorless RAG with PageIndex, adapted from the official cookbook.

Installation

pip install pageindex openai requests

Environment Setup

import os
import asyncio
from pageindex import PageIndexClient

os.environ["PAGEINDEX_API_KEY"] = "your_pageindex_api_key"
os.environ["OPENAI_API_KEY"] = "your_openai_api_key"

client = PageIndexClient(api_key=os.environ["PAGEINDEX_API_KEY"])

Step 1: Ingest a Document and Build the Tree Index

 import requests

# Upload and index a PDF document
with open("annual_report.pdf", "rb") as f:
    document = client.documents.create(
        file=f.read(),
        filename="annual_report.pdf",
        media_type="application/pdf"
    )

doc_id = document.id
print(f"Document indexed: {doc_id}")

# Inspect the tree structure
tree = client.documents.get_tree(doc_id)
for node in tree.nodes[:5]:
    print(f"[{node.id}] {node.title} (pages {node.page_start}-{node.page_end})")
    print(f"  Summary: {node.summary[:100]}...")

Step 2: Reasoning-Based Tree Search and Answer Generation

from openai import AsyncOpenAI
import json

openai_client = AsyncOpenAI(api_key=os.environ["OPENAI_API_KEY"])

async def pageindex_rag(doc_id: str, query: str) -> dict:
    # Load the tree structure
    tree = client.documents.get_tree(doc_id)
    tree_json = tree.to_json()

    # Ask LLM which nodes to retrieve
    tree_search_prompt = f"""
    You are a document retrieval expert.
    Given the document tree and query, return node IDs to retrieve.

    Tree: {tree_json}
    Query: {query}

    Return JSON only: {{"node_ids": ["N001", "N003"]}}
    """

    tree_response = await openai_client.chat.completions.create(
        model="gpt-4.1",
        messages=[{"role": "user", "content": tree_search_prompt}],
        response_format={"type": "json_object"}
    )

    selected_nodes = json.loads(
        tree_response.choices[0].message.content
    )["node_ids"]

    # Retrieve content from selected nodes
    context_parts = []
    for node_id in selected_nodes:
        node = client.documents.get_node_content(doc_id, node_id)
        context_parts.append(
            f"[{node.title} | pages {node.page_start}-{node.page_end}]\n{node.text}"
        )

    context = "\n\n".join(context_parts)

    # Generate final answer
    answer_response = await openai_client.chat.completions.create(
        model="gpt-4.1",
        messages=[{"role": "user", "content":
            f"Context:\n{context}\n\nQuestion: {query}\nAnswer:"}]
    )

    return {
        "answer": answer_response.choices[0].message.content,
        "retrieved_nodes": selected_nodes
    }

# Run
query = "What was total revenue in FY2024 vs FY2023?"
result = asyncio.run(pageindex_rag(doc_id, query))
print(result["answer"])

MCP Integration (Claude, Cursor, and Other Agents)

{
  "mcpServers": {
    "pageindex": {
      "type": "http",
      "url": "https://api.pageindex.ai/mcp",
      "headers": {
        "Authorization": "Bearer your_api_key"
      }
    }
  }
}

Benchmark Results: PageIndex vs Traditional RAG

The headline numbers come from FinanceBench, the industry standard for evaluating LLMs on financial document QA. It uses real SEC filings and requires exact answers from complex 10-K and 10-Q reports.

The gap between PageIndex (98.7%) and general vector RAG (~50%) is 48.7 percentage points. That is not a marginal improvement. It is a fundamentally different class of result.

Why does it work so much better? Three reasons show up consistently:

Cross-reference following. PageIndex identifies the Appendix A node when a document says 'see Appendix A' and retrieves it. Vector similarity has no concept of document-level cross-references.

Structure preservation. Financial tables have headers, subheaders, footnotes, and cell relationships. PageIndex preserves these as sections in the tree. Chunking destroys them.

Multi-hop reasoning. Questions like 'What was the year-over-year change in operating margin?' require numbers from two sections plus a calculation. PageIndex navigates to both sections.

One honest note: PageIndex has zero published latency or throughput benchmarks. Each query requires multiple sequential LLM calls. It is slower and more expensive per query than vector retrieval. For high-volume, low-latency use cases, that tradeoff does not work.

When to Use PageIndex (And When Not To)

PageIndex is a specialized tool, not a universal RAG replacement. I have seen developers treat it that way -- that is the wrong frame.

Use PageIndex when:

•       Working with long, structured professional documents (annual reports, legal contracts, regulatory filings, technical manuals)

•       Accuracy is the dominant constraint and you can tolerate higher latency

•       Queries require multi-step reasoning or cross-section reference following

•       You need a full audit trail -- PageIndex returns node references and reasoning traces for every answer

•       Building for regulated industries (finance, legal, medical) where 'close enough' is not acceptable

Do not use PageIndex when:

•       You need sub-second response times at high query volume

•       Documents are short, unstructured, or conversational

•       You have a large corpus of many small documents (vector search wins on cost and speed)

•       Building a consumer-facing chatbot where 90% accuracy is acceptable

The vector database market is projected to hit $10.6 billion by 2032. PageIndex does not invalidate that market. It creates a more accurate alternative for long, structured, high-stakes documents where vector retrieval has always had a known weakness.

Vectorless RAG vs Vector RAG: Side-by-Side Comparison

The traceability point matters more than I initially thought. In financial analysis, legal review, and medical records, the answer alone is not enough. A financial analyst needs to know exactly which paragraph of which SEC filing the number came from. PageIndex returns that. Vector RAG returns a chunk that might contain the answer -- not the same thing.

How to Get Started with PageIndex

Three paths, depending on what you want.

Option 1: Cloud Platform (Fastest). Visit chat.pageindex.ai and upload any PDF. No code required. Good for testing retrieval quality on your own documents before building anything.

Option 2: Self-Hosted via GitHub. Clone the open-source repo and run it locally. Requires your own LLM API keys and Python 3.8+.

git clone https://github.com/VectifyAI/PageIndex
cd PageIndex
pip install -e .

Option 3: API Integration. Get an API key at docs.pageindex.ai and integrate via the Python SDK or TypeScript SDK.

pip install pageindex

from pageindex import PageIndexClient

client = PageIndexClient(api_key="your_api_key")

with open("document.pdf", "rb") as f:
    doc = client.documents.create(file=f.read(), filename="document.pdf")

results = client.documents.search(doc.id, query="What is total revenue?")
print(results)

Frequently Asked Questions

What is vectorless RAG?

Vectorless RAG is a retrieval approach that does not use vector embeddings or a vector database. Instead of computing semantic similarity scores between a query and document chunks, it builds a hierarchical tree index of a document and uses LLM reasoning to navigate that tree. PageIndex, built by VectifyAI, is the primary open-source implementation and achieved 98.7% accuracy on FinanceBench.

How does PageIndex work without a vector database?

PageIndex works in two steps. First, it ingests a document and generates a hierarchical tree structure where each node has a title, summary, and page range. Second, when a query arrives, an LLM reads the tree and reasons about which nodes are most likely to contain the answer. The content from those nodes feeds into the final answer generation. No embeddings or vector similarity calculations are involved.

Is RAG without chunking actually more accurate?

For long, structured professional documents, yes -- substantially more accurate. PageIndex scored 98.7% on FinanceBench compared to approximately 30-50% for vector-based RAG on the same benchmark. The improvement is most significant for documents with complex hierarchy like SEC filings, legal contracts, and technical manuals.

What is a hierarchical tree index for LLMs?

A hierarchical tree index is a structured representation of a document where sections and subsections are organized as nodes in a tree. Each node contains a title, a summary of its content, and its page range. This structure reflects the document's natural organization rather than arbitrary token boundaries -- similar to a very intelligent table of contents.

PageIndex vs Pinecone: which should I choose?

They solve different problems. Pinecone is optimized for fast, high-volume semantic search across large corpora of short documents. PageIndex is optimized for accurate, reasoning-based retrieval from long, structured documents where exact accuracy matters. If you're building a FAQ chatbot or semantic search across thousands of articles, use a vector database. For financial reports, legal filings, or regulatory documents, evaluate PageIndex.

What are the limitations of vectorless RAG?

The primary limitations are latency and cost. Each query requires multiple sequential LLM inference calls to navigate the tree, which is slower and more expensive than a single vector similarity search. There are currently no published latency or throughput benchmarks from VectifyAI. PageIndex also does not provide an advantage over vector retrieval for short or unstructured content.

Is PageIndex free and open source?

The core PageIndex framework is open source under the MIT License and available at github.com/VectifyAI/PageIndex. VectifyAI also offers a hosted cloud service at chat.pageindex.ai, and API/MCP access for integration. Enterprise and on-premises deployment options are available by contacting VectifyAI.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•       RAGLite: Efficient Retrieval-Augmented Generation Framework

•       Smolagents: A Smol Library to Build Great Agents

•       Agenta: The Ultimate Open-Source LLMOps Platform

•       LangChain Basics: Building Intelligent Workflows

Want to learn how to build AI agents and document pipelines like these?

Join Build Fast with AI's Gen AI Launchpad -- an 8-week structured program

to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

  References

1.      1. PageIndex: Document Index for Vectorless, Reasoning-based RAG - VectifyAI GitHub (September 2025)

2.      2. Mafin 2.5 Leads Financial QA Benchmark - PageIndex Blog (February 2025)

3.      3. VectifyAI Launches Mafin 2.5 and PageIndex - MarkTechPost (February 2026)

4.      4. Vectorless RAG Hits 98.7% Accuracy - ByteIota (January 2026)

5.      5. PageIndex vs Vector Databases - Accentel Insights

6.      6. The Hidden Cost of 98% Accuracy - Medium / Tao An (December 2025)

7.      7. Show HN: PageIndex -- Vectorless RAG - Hacker News (September 2025)

 I run AI workflows every week across coding, writing, research, and agents. Last month I tested Claude Opus 4.6, GPT-5.4, and Gemini 3.1 Pro on the same tasks. The results were not what the marketing said. Claude crushed coding. Gemini won science by a mile. GPT-5.4 was the safest choice for writing where accuracy matters. Here's the full breakdown — model by model, task by task, with the benchmark numbers and the real-world nuance the leaderboard sites skip.

I've been through all of it. And here's the honest answer: there is no single best AI model in 2026. What there is, instead, is a clear winner for almost every specific task. Coding? Claude Opus 4.6 at 75.6% SWE-Bench. Scientific reasoning? Gemini 3.1 Pro at 94.3% GPQA Diamond. Budget API at scale? DeepSeek V3.2 at $0.14 per million input tokens.

This guide covers every major model currently active in 2026, what each one is actually built to do, the benchmarks that prove it, and exactly which model to pick for your use case. No history. No filler. Just the map.

1. What Changed in AI in 2026 (and Why You're Probably Using the Wrong Model)

Four things define the AI model market in March 2026.

Parity at the frontier. Gemini 3.1 Pro, Claude Opus 4.6, and GPT-5.4 are all within single-digit percentage points on most benchmarks. A year ago, GPT-4 had a visible lead. Today, the gaps are small enough that the 'right' model is decided by use case, cost, and ecosystem, not raw intelligence.

Specialization is the new strategy. OpenAI built GPT-5.3 Codex specifically for agentic terminal coding. Anthropic built Claude Sonnet 4.6 specifically for sustained production workflows. Google built Gemini 3 Flash specifically for high-volume, low-cost API use. The generalist model still exists, but the specialists are winning their domains.

Open-source is genuinely competitive. Meta's Llama 4 Scout has a 10 million token context window. GLM-5 from Zhipu AI holds an Intelligence Index score of 50 on Artificial Analysis, placing it in the top tier among open-weight models. DeepSeek V3.2 costs $0.14 per million input tokens and delivers GPT-4o-class output. Self-hosting is now a real option, not just a hobbyist experiment.

Price dropped 80% year-over-year. API costs for frontier-quality models fell roughly 80% between 2025 and early 2026. Models that cost $0.06 per 1,000 tokens in 2023 now run below $0.002. This means AI applications that were economically impossible 18 months ago are now routine production workloads.

2. Full Model Directory: Every Major AI Model Right Now

Here is every significant AI model actively serving users in March 2026, organized by provider.

Anthropic: Claude Family

•       Claude Opus 4.6 (Adaptive Reasoning, Max Effort) - Flagship. SWE-Bench 75.6%, GPQA Diamond 91.3%, 1M context window (beta), 128K output tokens. Best for: complex coding, long-form analysis, agentic workflows requiring reasoning depth.

•       Claude Sonnet 4.6 - Default model on Claude.ai free and pro plans. GDPval-AA Elo 1,633 (leads all models). 1M context (beta). Preferred over Opus 4.5 in Claude Code 59% of the time. Best for: production workflows, content pipelines, AI-assisted development at scale.

•       Claude Haiku 4.5 - Fast, cost-efficient. $1.00 input / $5.00 output per million tokens. Best for: classification, summarization, high-volume tasks where cost matters more than depth.

OpenAI: GPT Family

•       GPT-5.4 - Tied #1 on Artificial Analysis Intelligence Index alongside Gemini 3.1 Pro. 1M token context. Reduced hallucinations vs GPT-5.2. Best for: long-form reasoning, critical documentation, general professional tasks.

•       GPT-5.3 Codex - Specialist model for agentic coding and terminal-based software development. Native computer use, can operate IDEs directly. Best for: software developers running terminal-heavy agentic tasks.

•       GPT-5 / GPT-5.2 - Earlier GPT-5 series. Still active. $1.25/$10 to $1.75/$14 per million tokens. Broad general-purpose strength.

•       GPT-4o - Multimodal (text, audio, image, video). Real-time voice with natural prosody. $10 output per million tokens. Best for: voice interfaces, image understanding, real-time conversation.

•       GPT-4o mini - Budget tier. Low cost, high speed. Best for: simple question answering, lightweight chatbots, prototyping.

•       O3 Pro - Reasoning model for the most demanding research tasks. $150+ per million tokens. Best for: expert-level scientific and mathematical analysis where cost is not a constraint.

Google DeepMind: Gemini Family

•       Gemini 3.1 Pro - Released February 2026. ARC-AGI-2 77.1% (more than double Gemini 3 Pro). GPQA Diamond 94.3%, leading all models. $2/$12 per million tokens. Best for: scientific reasoning, agentic multi-step tasks, large-context processing, Google Workspace workflows.

•       Gemini 3 Pro - Previous generation flagship. Still competitive on most benchmarks. Integrated natively across Google products.

•       Gemini 3.1 Flash - Low latency, 1M context window, $0.50/$3 per million tokens. Best for: high-volume API applications, multilingual tasks, document processing at scale.

•       Gemini 2.5 Pro - Older but still widely used. $1.25/$10 per million tokens. 1M context.

•       Gemini 2.0 Flash-Lite - $0.075/$0.30 per million tokens. Best cheapest option that still works well for simple tasks.

xAI: Grok Family

•       Grok 4.20 Beta - Multi-agent architecture: four AI agents running in parallel. Full API not yet open as of March 2026. SWE-Bench ~75% (based on Grok 4 baseline). Real-time access to X (Twitter) data. Best for: research, science, math, social media intelligence.

•       Grok 4.1 - $0.20 input / $0.50 output per million tokens, the cheapest closed-source frontier-tier option. 2M context window. Best for: cost-sensitive deployments that need real-time data access.

•       Grok 4.1 Fast - 2M context, lowest latency in the Grok lineup. Good for real-time applications.

Meta: Llama Family (Open Source)

•       Llama 4 Scout - 10 million token context window, the largest of any model in 2026. Open weights under Meta's commercial license. Best for: extremely long-context tasks, RAG over entire knowledge bases, self-hosted deployments.

•       Llama 4 Maverick - Larger capability Llama 4 model. Competitive with closed-source models on many benchmarks. Open weights.

•       Llama 3.3 70B - Previous generation, widely fine-tuned community variant. Efficient, proven in production.

DeepSeek: Budget Frontier (Open Source)

•       DeepSeek V3.2 - $0.14 input / $0.28 output per million tokens. Best price-to-performance of any model for production API use. Open weights under MIT License. Strong on coding and reasoning.

•       DeepSeek R1 - Reasoning model. Matches OpenAI o1 on math and coding benchmarks at 95% lower training cost. Open source.

Mistral: European Open Source

•       Mistral Large 2 - Apache 2.0. Strong on technical and multilingual tasks. Leading choice for European enterprise deployments with data residency requirements.

•       Mistral 7B / Mistral Nemo - Ultra-lightweight. $0.02 per million tokens (Nemo). Runs on modest hardware. Best for edge deployments.

Alibaba: Qwen Family

•       Qwen 3.5 - Latest open-source model from Alibaba. Competitive with GPT-4o class on many benchmarks. Particularly strong on Chinese-language tasks. Apache 2.0.

Zhipu AI: GLM Family

•       GLM-5 - Highest-ranked open-weight model on Artificial Analysis Intelligence Index with a score of 50. 744 billion total parameters, 40 billion active (mixture-of-experts). MIT License. Available on Hugging Face.

Microsoft: Phi Family

•       Phi-4 - Small language model. Strong benchmark performance at 14 billion parameters. Best for: edge computing, fine-tuning on domain-specific data, environments with compute constraints.

Cohere: Command Family

•       Command R+ - 104 billion parameters. Optimized for retrieval-augmented generation. Strong multilingual performance. Best for: enterprise search, knowledge base Q&A, RAG pipelines.

3. Master Benchmark Table: All Models Side by Side

Benchmarks as of March 2026. SWE-Bench Verified measures real software engineering task completion. GPQA Diamond tests expert-level scientific knowledge. ARC-AGI-2 measures novel problem-solving that cannot be memorized. HLE (Humanity's Last Exam) uses 2,500 expert-curated multi-domain questions.

Note: Some benchmarks are not publicly available for all models. '~' indicates community consensus estimates.

In my own testing on a 3,000-line TypeScript refactor, Opus 4.6 caught 4 type errors that Gemini 3.1 Pro missed entirely. Sonnet 4.6 caught 3 of the 4 at a fifth of the cost — which is why it's now my daily driver for production work.

4. Best AI Model by Task: The Definitive 2026 Rankings

This is the section most people actually need. For each task category, I've identified the winner and one strong runner-up, with the benchmark evidence behind the call.

CODE  Best for Coding & Software Engineering

Winner: Claude Opus 4.6 (winner) + GPT-5.3 Codex (agentic terminal tasks)

Opus 4.6 leads on SWE-Bench at 75.6%. For terminal-heavy agentic coding, GPT-5.3 Codex is purpose-built and arguably the specialist winner.

Claude Opus 4.6 earns 75.6% on SWE-Bench Verified, the highest publicly confirmed score among general-purpose models. It powers Cursor and Windsurf by default. It has 128K output tokens, which matters when you're generating entire codebases. 59% of users in Claude Code testing preferred Sonnet 4.6 over Opus 4.5, so Sonnet is worth testing for cost reasons on everyday tasks.

GPT-5.3 Codex is a different animal. It doesn't compete on general benchmarks. It's built specifically for agentic terminal use: editing files, running commands, debugging in environments. If your workflow is software-development-as-an-agent rather than chat-assisted coding, Codex is the specialist pick.

Grok 4 also clocks ~75% on SWE-Bench with its multi-agent architecture where four agents run in parallel on the same problem. I'd watch Grok 4.20 when the full API opens.

SCIENCE  Best for Scientific & Expert Reasoning

Winner: Gemini 3.1 Pro

94.3% GPQA Diamond, leading all models. ARC-AGI-2 at 77.1%, more than double its predecessor.

Gemini 3.1 Pro's 94.3% on GPQA Diamond is the number to know. GPQA Diamond tests expert-level scientific knowledge across biology, chemistry, and physics. The previous record was held by GPT-5.4 at 92.8% and Claude Opus 4.6 at 91.3%. Gemini's margin here is meaningful, not marginal.

For ARC-AGI-2, which tests pure novel logic that can't be memorized, Gemini 3.1 Pro scores 77.1%. That's more than double Gemini 3 Pro's score. The jump suggests a genuine architectural improvement in how the model handles novel problems, not just better recall of training data.

If your work involves interpreting research papers, answering expert-level medical or scientific questions, or running structured experiments through an AI system, Gemini 3.1 Pro is the call.

WRITING  Best for Writing, Content & Long-Form Work

Winner: Claude Sonnet 4.6 (production) + GPT-5.4 (research-heavy)

GDPval-AA Elo 1,633 for Sonnet 4.6, leading all models on expert-level real office work.

Claude Sonnet 4.6 leads GDPval-AA, an OpenAI-created benchmark measuring AI performance on 44 professional knowledge work occupations. An Elo of 1,633 places it above Opus 4.6 and Gemini 3.1 Pro on real expert-level office work. For sustained writing tasks, content pipelines, and editorial work, this is the model I use.

GPT-5.4 is the strong second for anything requiring broad factual depth. Its hallucination rate is 33% lower than GPT-5.2, which matters when you're writing about topics where accuracy counts. For research-heavy long-form writing, the reduced hallucination profile justifies the slightly higher cost.

For pure creative writing with lots of personality and voice? Claude still reads more like a human writer than GPT's outputs, which tend to run more encyclopedic.

MATH  Best for Mathematics & Competition Problems

Winner: Gemini 3.1 Pro + OpenAI o3 Pro (extreme difficulty)

Leads on MATH-Level 5 and AIME-class problems. o3 Pro for genuinely research-level mathematics.

Gemini 3.1 Pro's tiered thinking levels (Low, Medium, High) let you control compute per problem, which is a genuinely useful design for math workloads where some problems need 5 seconds of reasoning and others need 5 minutes.

For AIME and competition-level mathematics, the reasoning models outperform the general ones. OpenAI's o3 Pro sits at the extreme end: $150+ per million tokens, manual-rubric-graded responses, designed for genuine research-level mathematics. For 99.9% of people, that's overkill. For academic researchers solving open problems, it's the only serious option.

MULTIMODAL  Best for Images, Audio & Video Understanding

Winner: GPT-4o (voice/audio) + Gemini 3.1 Pro (video/documents)

GPT-4o: real-time voice with natural prosody. Gemini 3.1 Pro: full video processing, 24-language voice.

GPT-4o's voice mode remains the most natural of any model. It matches prosody, recognizes emotional tone, and responds with something close to genuine conversational rhythm. If you're building voice interfaces or anything requiring natural spoken interaction, GPT-4o is the current standard.

Gemini 3.1 Pro handles the video and document analysis side: full-length video processing, 24-language voice support, 75% prompt caching discounts on repeated content. For applications that need to process video files, long PDFs, or audio transcripts at scale, Gemini's multimodal stack is ahead.

AGENTS  Best for AI Agents & Autonomous Task Completion

Winner: Claude Opus 4.6 (complex agents) + Gemini 3.1 Pro (tool orchestration)

Claude's Agent Teams and adaptive thinking. Gemini's native tool use and structured output reliability.

Agentic AI, meaning models that take sequences of actions with tools to complete goals, has become the defining use case of 2026. Two models lead here for different reasons.

Claude Opus 4.6's Agent Teams feature lets multiple Claude instances collaborate on the same task. Combined with adaptive thinking and effort controls, it handles the kind of multi-hour, multi-step research and coding tasks that earlier models couldn't sustain.

Gemini 3.1 Pro's native tool use is more tightly integrated with real-time APIs, Google Search, and structured data outputs. For agents that need to interact with the open web or structured enterprise data, Gemini's tool reliability is better documented in production.

Grok 4.20's parallel multi-agent architecture, four agents running simultaneously on the same problem, is a genuinely different approach that hasn't fully landed in the market yet. Worth watching when the API opens.

LONG CONTEXT  Best for Processing Very Long Documents

Winner: Llama 4 Scout (10M tokens) + Gemini 3.1 Pro (1M tokens, best closed-source)

Llama 4 Scout holds the largest context window of any model at 10 million tokens.

Llama 4 Scout's 10 million token context window is the largest in the industry. To put that in perspective, 10 million tokens is roughly 7,500,000 words, or around 25 full-length novels. If you need to process entire legal document repositories, giant codebases, or multi-year research archives in a single prompt, this is the only model that can do it.

Among closed-source options, Gemini 3.1 Pro at 1 million tokens and GPT-5.4 at 1 million tokens are equally matched, but Gemini's prompt caching discount (up to 75% off repeated content) makes it significantly cheaper for long-context applications that reuse the same context across many requests.

TRANSLATION  Best for Multilingual & Translation Tasks

Winner: Gemini 3.1 Pro + Qwen 3.5 (Asian languages)

Gemini: 24-language voice, trained for global multilingual. Qwen: best on Chinese, Japanese, Korean.

Gemini 3.1 Pro's multilingual training is documented across 100+ languages with native voice in 24. For European and global language pairs, it consistently outperforms competitors on accuracy and register.

For East Asian languages, particularly Chinese-language tasks, Qwen 3.5 from Alibaba is the specialist pick. It was trained with native Chinese language data at a scale that no US lab matches. If your use case involves Chinese, Japanese, or Korean at volume, Qwen should be in your evaluation.

CUSTOMER SUPPORT  Best for Customer Service Automation

Winner: Kimi K2 (Moonshot AI) + Claude Sonnet 4.6

Kimi K2 holds the #1 spot on Tau2-Bench Telecom, the agentic customer support benchmark.

Moonshot AI's Kimi K2 achieved the number one position on the Tau2-Bench Telecom benchmark, which specifically measures customer support automation in agentic settings. This is a data point most Western AI coverage misses, but for anyone building customer service agents, it's the most directly relevant benchmark available.

For English-language customer support at scale, Claude Sonnet 4.6 is the production-proven choice. At $3/$15 per million tokens with batch API discounts of 50% for non-urgent tasks, the economics for high-volume customer support work out better than GPT-5.4.

ENTERPRISE PRIVACY  Best for Self-Hosted & Privacy-Sensitive Deployments

Winner: Llama 4 Maverick + DeepSeek V3.2

Open weights, self-hostable, no data sent to external APIs. Enterprise-grade quality.

 

Any organization that cannot send data to a third-party API, due to HIPAA, GDPR, client agreements, or security requirements, needs an open-weight model they can run on their own infrastructure.

Llama 4 Maverick offers the strongest combination of capability and ecosystem. The Meta ecosystem of fine-tuning tools, quantization recipes, and community adapters is larger than any other open-weight model family. DeepSeek V3.2 is a strong second: MIT License, GPT-4o-class performance, and $0.14 per million tokens on third-party hosting if full self-hosting isn't feasible.

5. Best AI Model by Budget

Budget shapes model choice as much as capability does. Here's the honest breakdown by spending tier.

Best Free AI Model in 2026

What You Get Without Paying Google Gemini Flash gives you 1,000 free API requests per day — the most generous free tier of any frontier model. For the web interface, Claude.ai free gives you access to Claude Sonnet 4.6 (the model that tops professional writing benchmarks at Elo 1,633) with a limited daily message cap. ChatGPT free still runs on GPT-4o mini by default, not GPT-5. For daily use without paying anything: Gemini free tier is the best deal if you need volume. Claude free is the best deal if you need writing quality. ChatGPT free is the most familiar but no longer the most capable at the free tier.

6. Open-Source vs Closed-Source: Which Should You Choose?

The open vs closed question used to have an obvious answer: closed-source models were clearly better. In 2026, that's no longer true at the mid-tier and below.

Choose open-source if:

•       You have data privacy or compliance requirements that prevent sending data to external APIs

•       You need to fine-tune on proprietary data and want to own the resulting model

•       You're building in a cost-sensitive environment where $0.01 per request is too expensive at scale

•       You want to run inference on your own hardware with no ongoing API costs

Choose closed-source if:

•       You need the absolute best performance on complex reasoning or coding tasks

•       You want managed infrastructure, reliability SLAs, and support contracts

•       You're building quickly and don't have ML engineers to handle model deployment

•       You need multimodal capabilities, especially audio and video, which remain stronger in closed models

The honest middle ground: start with an open-weight model for development and cost estimation, then switch to a closed-source model only where the quality gap justifies the price. For many production applications, DeepSeek V3.2 or Llama 4 Maverick will be 'good enough' at 1/20th the cost.

7. Claude Pro vs ChatGPT Plus vs Gemini Advanced: Is the $20/Month Worth It?

For people who don't use the API and just want a monthly subscription:

For most individual professionals, Claude Pro at $20/month ($17/month annual) offers the best combination of context window, output quality, and access to both Sonnet and Opus tiers. For anyone already inside the Google ecosystem, Gemini AI Pro's bundled 2TB storage and Workspace integration makes it the better value.

8. API Pricing Comparison Table (Per Million Tokens)

Current API pricing as of March 2026. Input and output prices are listed separately. Output tokens cost 3-8x more than input tokens across most providers.

Cost-saving tip: All major providers offer prompt caching. Repeated system prompts or context can be cached at up to 90% off the standard input price. Anthropic's batch API offers 50% off for non-urgent, asynchronous tasks. Gemini's context caching provides up to 75% discounts on repeated long-context content.

9. How to Choose the Right AI Model for Your Use Case

Run through this decision tree before picking a model:

Step 1: What's your primary task? Use Section 4's winner boxes. If your task is coding, start with Claude Opus 4.6. If it's scientific reasoning, start with Gemini 3.1 Pro. Match task to domain winner first.

Step 2: Do you have data privacy requirements? If yes, you need an open-weight model. Llama 4 Maverick or DeepSeek V3.2 are the top choices depending on your compute budget.

Step 3: What's your token budget? If you're building a production application at scale, the cost difference between models is enormous. $0.14/M (DeepSeek) vs $5/M (Claude Opus) is a 35x difference. At 100 million tokens per month, that's $14,000 vs $500,000 per year.

Step 4: What does your ecosystem look like? Already deep in Google Workspace? Gemini 3.1 Pro integrates natively. Running GitHub Copilot? Claude Sonnet 4.6 powers it. Using Cursor or Windsurf? Claude Opus 4.6 is the default. Ecosystem fit matters for friction.

Step 5: Test before committing. Every major provider offers either a free tier or free credits. Run your actual use case, not a generic benchmark, against your top 2 candidates. Real-world task performance often differs from published benchmark scores.

Frequently Asked Questions

Which AI model is best for coding in 2026?

Claude Opus 4.6 leads on SWE-Bench Verified at 75.6%, making it the benchmark winner for general software engineering. For agentic terminal-based coding workflows, GPT-5.3 Codex is purpose-built and edges ahead. Grok 4.20's parallel multi-agent architecture is a strong emerging option at ~75% SWE-Bench.

Which AI model is best for scientific reasoning?

Gemini 3.1 Pro leads all models on GPQA Diamond (expert-level science) at 94.3%, ahead of GPT-5.4 at 92.8% and Claude Opus 4.6 at 91.3%. It also leads on ARC-AGI-2 at 77.1%, which tests novel problem-solving that cannot be memorized from training data.

What is the cheapest AI model that actually works in 2026?

DeepSeek V3.2 at $0.14 input / $0.28 output per million tokens delivers GPT-4o-class performance at roughly 95% less cost. For free options, Google offers 1,000 free requests per day on Gemini Flash-class models. Grok 4.1 at $0.20/$0.50 per million tokens is the cheapest closed-source frontier option.

What is the best open-source AI model in 2026?

Meta's Llama 4 Scout leads on context window at 10 million tokens, the largest of any model. GLM-5 from Zhipu AI holds the highest open-weight Intelligence Index score at 50. DeepSeek V3.2 offers the best price-to-performance of any open model for API use. All three are strong candidates depending on whether you prioritize context, intelligence, or cost.

Is Gemini 3.1 Pro better than Claude Opus 4.6?

On pure benchmark scores: Gemini 3.1 Pro leads on GPQA Diamond (94.3% vs 91.3%) and ARC-AGI-2 (77.1% vs 68.8%). Claude Opus 4.6 leads on SWE-Bench (75.6% vs 63.8%) and GDPval professional work tasks. Gemini is also cheaper at $2/$12 vs Claude's $5/$25 per million tokens. For science and long-context reasoning, Gemini wins. For coding and professional documents, Claude wins.

What is the best AI model for writing?

Claude Sonnet 4.6 leads the GDPval-AA Elo benchmark (1,633 points), which measures AI performance on expert-level professional writing tasks. For research-heavy long-form writing where factual accuracy matters, GPT-5.4's 33% lower hallucination rate compared to GPT-5.2 makes it the safer choice.

What AI models work without sending data to external servers?

Llama 4 (Meta), DeepSeek V3.2, Mistral Large 2, Qwen 3.5, and GLM-5 are all open-weight models that can be self-hosted on your own infrastructure. Llama 4 Maverick is the strongest general-purpose option with the largest fine-tuning ecosystem. DeepSeek V3.2 offers the best benchmark performance relative to compute cost.

How much does GPT-5 cost vs Claude in 2026?

GPT-5 / GPT-5.2 starts at $1.25/$10 per million input/output tokens. Claude Sonnet 4.6 costs $3/$15. Claude Opus 4.6 costs $5/$25. GPT-5.4 starts at approximately $2.50 per million input tokens. Grok 4.1 is the cheapest closed-source option at $0.20/$0.50. Gemini 3.1 Pro at $2/$12 currently offers the best price-to-capability ratio among frontier closed models.

 Q: Is Claude better than ChatGPT in 2026?

Claude Sonnet 4.6 leads ChatGPT on professional writing (GDPval-AA Elo 1,633 vs GPT-5.4's 1,601) and coding (SWE-Bench 75.6% vs ~74.9%). ChatGPT (GPT-5.4) leads on broad factual accuracy with 33% fewer hallucinations than GPT-5.2. For coding and writing: Claude. For research documents: GPT-5.4.

Which AI should I use every day in 2026?

Claude Sonnet 4.6 for most professionals — it leads real-world office task benchmarks and costs $3 per million input tokens. If you're already in the Google ecosystem, Gemini Advanced is the better daily driver. For coding specifically, Claude Code powered by Opus 4.6 is the daily standard.

Is GPT-5 better than Claude Opus 4.6?

On different tasks: GPT-5.4 scores higher on hallucination reduction (33% improvement over GPT-5.2) and broad general reasoning. Claude Opus 4.6 scores higher on coding (SWE-Bench 75.6% vs GPT-5.4's ~74.9%) and professional writing. Neither is universally better — the task decides.

What is the best AI model for image generation in 2026?

Claude, GPT, and Gemini are text models — they do not generate images natively. For image generation: Midjourney v7 leads on artistic quality, Google Imagen 4 leads on photorealism and text accuracy, and Stable Diffusion 3.5 is the open-source standard.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper:

•       12+ AI Models in March 2026: The Week That Changed AI

•       GPT-5.4 vs Gemini 3.1 Pro (2026): Which AI Wins?

•       GPT-5.4 Review: Features, Benchmarks & Access (2026)

•       Grok 4.20 Beta Explained: Non-Reasoning vs Reasoning vs Multi-Agent (2026)

•       Gemini 3.1 Flash Lite vs 2.5 Flash: Speed, Cost & Benchmarks (2026)

•       Gemini Embedding 2: First Multimodal Embedding Model (2026)

•       Sarvam-105B: India's Open-Source LLM for 22 Indian Languages (2026)

Want to deploy these models in real products?

Join Build Fast with AI's Gen AI Launchpad, an 8-week program to go from 0 to 1 in building AI-powered apps with the best models available today.

Register: buildfastwithai.com/genai-course

References

1. Artificial Analysis - AI Model Intelligence Index & Leaderboard (March 2026)

2. LogRocket - AI Dev Tool Power Rankings March 2026

3. Design for Online - The Best AI Models So Far in 2026

4. IntuitionLabs - AI API Pricing Comparison 2026: Grok vs Gemini vs GPT vs Claude

5. TLDL - LLM API Pricing March 2026 (GPT-5.4, Claude, Gemini, DeepSeek)

6. Pluralsight - Best AI Models in 2026: What Model to Pick for Your Use Case

7. gurusup.com - Best AI Model 2026: Comparison Guide

8. LM Council - AI Model Benchmarks March 2026

9. Anthropic - Claude 4.6 Model Card

10. Google DeepMind - Gemini 3.1 Pro Technical Overview

4% of all public GitHub commits are now authored by Claude Code. That number doubled in a single month.

Stop and reread that. Not 4% of AI-assisted commits. 4% of every public commit on GitHub. Anthropic has quietly moved from the thoughtful alternative to ChatGPT to running infrastructure that millions of developers rely on every working day. In the last 30 days alone they shipped more than most AI companies do in a year: memory for every free user, a security scanner that crashed cybersecurity stocks by up to 9%, a desktop productivity agent called Cowork, and a complete overhaul of Claude Code's architecture.

This guide covers everything: all three models, every new feature, pricing, real benchmark data, head-to-head comparisons against ChatGPT, Gemini, Grok, and DeepSeek, and a look at what Claude 5 might look like when it ships.

What Is Claude AI? The Basics for New Users

Claude is an AI assistant built by Anthropic, a safety-focused company founded in 2021 by Dario Amodei, Daniela Amodei, and a team of former OpenAI researchers. Claude is available as a web, mobile, and desktop chat interface at claude.ai, through the Anthropic API, on AWS Bedrock, and on Google Vertex AI.

What actually differentiates Claude from ChatGPT or Gemini is Constitutional AI. Instead of training purely on human preference ratings, Anthropic teaches Claude a set of principles (a 'constitution') and lets the model reason about its behavior against those principles. The 2026 version of that constitution has grown from 2,700 words in 2023 to 23,000 words today. That is not legal padding. It is an attempt to build a model with genuine ethical judgment, not just a rule filter.

I believe this is Anthropic's most underappreciated technical advantage. Scaling a coherent ethical reasoning framework as model capability increases is a harder and more defensible engineering problem than training on preference labels alone.

Claude is currently on its 4.6 generation of models. The top model, Opus 4.6, supports 1 million tokens of context and generates up to 128,000 output tokens per response.

All Three Claude Models Explained: Opus 4.6, Sonnet 4.6, Haiku 4.5

Claude Opus 4.6 - The Flagship

Opus 4.6 launched February 5, 2026. It is the most capable production model Anthropic has shipped. Specs: 1 million token context window, 128,000 max output tokens per response (doubled from the previous 64k cap), full adaptive thinking support, and 80.9% on GPQA Diamond (graduate-level science reasoning), 80.8% on SWE-bench verified. API pricing: $15/million input tokens, $75/million output tokens.

The 128k max output matters more than the spec suggests. It means Claude can generate an entire codebase module, a multi-file refactor, or a 50,000-word research report in a single response without truncation.

Claude Sonnet 4.6 - The Daily Driver

Sonnet 4.6 is where most professional users should default. Same 1M token context window as Opus. 64k max output. 79.6% on SWE-bench, which is near-Opus performance at 5x lower cost ($3/M input, $15/M output). For production coding agents, document analysis, or enterprise workflows, Sonnet 4.6 is almost always the rational pick.

Claude Haiku 4.5 - The Speed Model

Haiku 4.5 is built for throughput. 200k token context, 200+ tokens per second, $0.80/M input. The key achievement: it is the first Haiku model to support Extended Thinking, bringing chain-of-thought reasoning to the fastest and cheapest tier. Still scores 73.3% on SWE-bench at this price point

One million tokens equals approximately 750,000 words. Three complete novels side by side. For enterprises processing contracts, codebases, or research libraries in single prompts, this context window is not a benchmark stat. It is a workflow transformation.

Every New Feature Released in the Last 30 Days

Adaptive Thinking: Claude Decides When to Reason

This received the least press coverage and has the most technical significance. The previous Extended Thinking approach required developers to set a budget_tokens parameter: you told Claude exactly how many tokens it was allowed to use for internal reasoning. That method is now deprecated on Opus 4.6.

The new approach: thinking: {type: 'adaptive'}. Claude evaluates each request and independently decides whether and how deeply to engage extended reasoning. On complex problems it almost always activates. On simple prompts it skips reasoning entirely to save compute and latency. This is meta-cognition baked into the API layer.

Memory for Every User (March 2026)

Anthropic pushed persistent memory to all Claude users, including the free tier, in early March 2026. Claude now retains your name, communication style, writing preferences, and ongoing project context across separate conversations. You start a new chat; Claude already knows who you are.

ChatGPT has had this feature for paid users since early 2024. Anthropic gave it to everyone, with full transparency controls: you can view every stored memory, edit individual entries, or wipe the entire history at any time.

Claude Code Security (February 20, 2026)

The biggest product launch in Anthropic's history by market impact. Claude Code Security launched as a limited research preview for Enterprise and Team customers. It uses Opus 4.6 to scan production codebases for vulnerabilities by reasoning about data flows and component interactions, the way a human security researcher does, not pattern-matching like traditional static analysis tools.

In pre-launch testing, Anthropic found over 500 vulnerabilities in real open-source production codebases, including bugs undetected for years despite active expert review. Every finding is severity-rated. No patch is applied without explicit human approval.

The market reaction was immediate: CrowdStrike fell 8%, Cloudflare dropped 8.1%, Okta declined 9.2%, Zscaler lost 5.5%, and the Global X Cybersecurity ETF closed at its lowest since November 2023.

Fast Mode and Data Residency Controls

Two enterprise developer additions: speed: 'fast' with the fast-mode-2026-02-01 beta flag accelerates Opus output generation for time-sensitive pipelines. The inference_geo parameter routes API calls to US-only infrastructure, satisfying data residency requirements in healthcare, finance, and government deployments.

Claude Code 2026: What Changed in the February Overhaul

Claude Code started as a command-line AI pair programmer. After February 2026, it is closer to an autonomous software operations platform. Five new capabilities defined the upgrade:

•       Remote Control: Access and monitor a running Claude Code session from a browser or mobile device. Start a long refactor at your desk, check progress from your phone.

•       Scheduled Tasks: Claude Code executes recurring workflows without manual prompts. Security audits every Monday. Test coverage reports after each deployment. PR summaries every Friday afternoon.

•       Plugin Ecosystem: Standardized MCP integrations let third-party tools plug into Claude Code natively, similar to VSCode extensions but at the agent layer.

•       Parallel Agents: Large tasks decompose into subtasks executed by multiple coordinated Claude instances simultaneously. Build frontend and backend in parallel. Scan security while writing docs.

•       Auto Memory: Persistent knowledge of your specific project - architecture decisions, naming conventions, team standards, past choices. Context that builds over time rather than restarting every session.

4% of all public GitHub commits are now authored by Claude Code. That figure doubled in one month. And approximately 90% of Claude Code's own code is now written by Claude Code itself, according to Anthropic engineers. These are not aspirational numbers. They are production metrics from a tool that has already escaped the experimental phase.

Claude Desktop App and Cowork: AI for Everyone

Claude Cowork launched January 12, 2026 in research preview. It is the desktop version of Claude's agentic capabilities, built for knowledge workers who do not live in terminals or code editors.

The interface is file-and-folder based. You grant Claude access to a directory. You describe the task. Claude reads existing files, executes the workflow, and produces deliverables in the same folder. Tasks it handles: restructuring messy file systems, pulling data from screenshots or PDFs into spreadsheets, drafting reports by synthesizing scattered documents, generating slide decks from raw notes, filling client briefs from email threads.

Anthropic's Head of Enterprise Scott White framed it as 'vibe working': the non-developer equivalent of vibe coding. The same way non-programmers can now describe a web app and have AI build it, knowledge workers can describe a deliverable and have Claude produce it.

Markets on launch day: ServiceNow -23%. Salesforce -22%. Thomson Reuters -31%. Institutional money read those moves as a verdict that a $20/month AI agent capable of doing workflow automation competes directly with enterprise software platforms charging hundreds of thousands of dollars annually.

Cowork requires a paid plan: Pro (~$20/month), Max ($100-$200/month), Team ($30/seat), or Enterprise. Connects to local files, Google Drive, Gmail, and Calendar via MCP integrations.

Claude Pricing in 2026: Every Plan and API Cost

The free tier is the most competitive it has ever been. Memory, web search, Artifacts, and Sonnet 4.6 access for $0 is a serious offering. Claude Pro at $20/month with Extended Thinking, full Claude Code, and Cowork preview delivers more capability-per-dollar than any comparable AI subscription. The Max tier makes sense only for power users or professionals who run Opus 4.6 as their primary work tool.

Benchmark Data: Claude vs ChatGPT, Gemini, Grok, DeepSeek

Here are the actual numbers from independent benchmark sources as of March 2026. Not marketing claims.

Three things I want to call out directly. First, GPT-5.3 Codex beats Claude on Terminal-Bench 2.0 by nearly 12 percentage points. That is a real gap for terminal-heavy agentic work; do not let Claude advocates minimize it. Second, both Gemini 3.1 Pro and Grok 4.20 offer 2M token context windows, which is larger than Claude's 1M. Third, on OSWorld computer use automation, Claude sits around 50% while GPT-5.4 has pushed to 75%. Anthropic appears to be making a deliberate choice to prioritize long-context quality over this specific benchmark.

Where Claude holds a defensible lead: SWE-bench (real-world software engineering), GPQA Diamond (graduate-level reasoning), 128k max output tokens (nobody else is close at these prices), and finance agent tasks (#1 ranked). These are not niche benchmarks. They are the tasks enterprises actually care about.

Claude Skills and Agentic Capabilities Explained

Skills are pre-built, reusable capability modules that extend what Claude can do inside Claude Code and Cowork. Think of them as specialized function libraries for AI agents, built on the Model Context Protocol (MCP) standard.

In Claude Code, skills enable actions that go beyond raw coding: running a full security audit, generating comprehensive test suites for a specific framework, producing API documentation from code comments, refactoring legacy code toward a modern standard. Each skill is a standardized MCP integration that Claude Code can invoke as part of a larger workflow.

The February 2026 Plugin Ecosystem opening means third parties can now publish skills into the Claude Marketplace. As of March 6, 2026, six enterprise partners are live:

•       GitLab: Code review automation, CI/CD pipeline integration, PR analysis

•       Harvey: Legal document analysis, contract review, regulatory compliance checking

•       Lovable: No-code app generation and iteration without touching a terminal

•       Replit: Cloud development environment creation and management

•       Rogo: Financial report analysis, earnings transcript processing, market research

•       Snowflake: Natural language querying of data warehouses, schema understanding

What this architecture enables in practice: a single Claude Code session can now orchestrate across GitHub, your database, your documentation system, your cloud infrastructure, and your legal review pipeline, using native skills for each, without custom integration code for every tool.

I think MCP and skills are the most underreported story in AI right now. Everyone covers benchmark scores. Almost no one is writing about the integration layer that turns benchmark scores into actual production value. The companies that figure out Claude as an orchestration layer, not just a smart autocomplete, are going to have significant workflow advantages by end of 2026.

Claude for Enterprise: Context, Market Share, and the Marketplace

Consumer web traffic data from SimilarWeb in January 2026 shows ChatGPT at approximately 64.5% of AI chatbot traffic, Gemini at 21.5%. Claude's consumer share is smaller.

But consumer web traffic is the wrong metric for understanding Anthropic's actual position. Three enterprise data points tell a different story:

Claude Code revenue grew 5.5x between Q1 and Q3 2025. Claude Enterprise provides 500,000 token context windows, more than double what ChatGPT Enterprise offers, and this enables use cases like processing an entire year of financial filings or a 300-file codebase in a single prompt. And the Claude Marketplace, launched March 6, 2026, consolidates procurement across six partner tools into a single Anthropic billing relationship, which is how enterprise software sales actually work.

Multi-cloud availability is also strategically important. All Claude models run on the Anthropic API, AWS Bedrock, and Google Vertex AI. Large enterprises cannot migrate their entire stack to a new vendor's platform. Meeting them where they already are is why Anthropic is winning deals that purely API-native companies cannot.

Head-to-Head: Claude vs ChatGPT, Gemini, Grok, DeepSeek

Claude vs ChatGPT (OpenAI GPT-5 Family)

Context window is Claude's clearest structural enterprise advantage. Claude Enterprise offers 500,000 tokens; ChatGPT Enterprise offers less than half. In a controlled blind test across 8 prompts with 134 participants, Claude won 4 out of 8 rounds, ChatGPT won 1, Gemini won 3. When Claude won, margins were 35 to 54 points. When Gemini won, margins were 3 to 11. Claude wins decisively or loses.

ChatGPT's real advantages: 200 million weekly users, the largest developer ecosystem, OpenAI's Operator network, and GPT-5.4's 75% OSWorld computer use score. For general consumer use and computer use automation, ChatGPT leads. For enterprise long-context reasoning and production coding: Claude leads.

Claude vs Gemini 3.1 Pro (Google)

Gemini is faster, offers a 2M token context window, and integrates natively with Google Workspace, Firebase, and Android development workflows. If your team is built on Google infrastructure, Gemini is a serious tool. Where Claude wins: complex multi-step reasoning, debugging logic errors in large codebases, and sustained agentic performance across long sessions. Gemini can produce code that looks clean but has subtle logical errors. Claude's outputs tend to be more reliably correct and debuggable.

Claude vs DeepSeek V4

DeepSeek V4 is the best performance-per-dollar model available in 2026. No debate on that point. For cost-sensitive teams willing to handle their own infrastructure or accept Chinese data residency, DeepSeek is the rational economic choice. For regulated industries, US compliance requirements, or organizations that need Anthropic's safety guarantees and model reliability track record: Claude wins on everything except pure cost.

Claude vs Grok 4.20 (xAI)

Grok 4.20 launched February 17, 2026 with a genuinely different architecture: four specialized agents (Grok, Harper, Benjamin, and Lucas) running in parallel, covering coordination, real-time fact-checking with live X data, logic and math, and contrarian analysis. This peer-review mechanism reduces hallucinations from approximately 12% to 4.2% according to benchmark data. Context window: 2M tokens. Consumer access requires SuperGrok ($30/month) or X Premium+. For real-time information tasks and social media analysis, Grok has an edge no other model can match. For deep long-context reasoning, enterprise coding, and document processing: Claude wins.

Claude vs Kimi K2.5 (Moonshot AI)

Kimi K2.5 launched January 27, 2026 with comparable coding performance to Claude Opus 4.6 at approximately 10x lower API pricing. 1 trillion total parameters, 32B active via Mixture of Experts, 256k context window, fully open-source. It is the dark horse in the 2026 coding model race. For pure coding workloads where cost matters more than reasoning quality or enterprise compliance: Kimi deserves serious evaluation. Anthropic is not trying to compete on price here. They are competing on trust, safety reputation, and enterprise tooling quality.

Controversies, Ethics, and the Pentagon Standoff

Anthropic is navigating two situations that test whether their safety positioning is genuine or marketing.

The Pentagon standoff: In February 2026, the US Department of Defense demanded Anthropic remove contractual prohibitions on using Claude for mass domestic surveillance and fully autonomous weapons. Defense Secretary Pete Hegseth set a February 27, 2026 deadline for Anthropic's response. Anthropic declined to comply. Claude's use by US federal agencies is now being phased out.

Anthropic turned down significant federal government revenue rather than allow Claude to be used in ways their safety principles prohibit. Whatever your view on the specific prohibitions, the fact that they held that position under pressure from the Pentagon is meaningful evidence that the safety commitments are not just positioning.

The Constitution update: Philosopher Amanda Askell expanded Claude's constitutional guidelines from 2,700 words to 23,000. The expansion is not new restrictions. It is detailed reasoning context so Claude can apply judgment in novel situations rather than pattern-match to rules. Whether this produces better behavior than traditional fine-tuning is still an open empirical question in the field.

What Is Coming Next: Claude 5 Leaks and Roadmap

Multiple sources report that Claude 5 (Sonnet 5, codenamed 'Fennec') has already appeared in Google Vertex AI infrastructure logs. Expected release window: mid-2026.

What early intelligence suggests about Claude 5:

•       Coding performance that surpasses Opus 4.6 at Sonnet-level pricing

•       'Dev Team' multi-agent mode: multiple specialized Claude instances coordinating on a single long-horizon engineering project

•       Pricing approximately 50% lower than current flagship models

•       Persistent memory baked into core architecture rather than layered on top

•       Sustained multi-week reasoning for enterprise projects that span months, not sessions

The March 2026 memory rollout reads like architectural groundwork for Claude 5. If persistent memory gets baked into the model's core training rather than existing as a retrieval layer, the resulting assistant would be genuinely different from anything currently available: a tool that builds a detailed model of you, your preferences, and your work context over months rather than minutes.

Claude Cowork moving from research preview to general availability is also expected by mid-2026, and the Marketplace is scheduled to add 15+ new enterprise partner integrations by Q3 2026.

Frequently Asked Questions

What is Claude AI and how does it differ from ChatGPT in 2026?

Claude is built by Anthropic using Constitutional AI, a training method where the model reasons about its own behavior against ethical principles rather than just optimizing for human preference ratings. Practical differences: Claude offers 1M token context (vs ChatGPT's 128k), tops enterprise coding benchmarks, and gives free-tier users memory and Sonnet 4.6. ChatGPT has 200M+ weekly users and a broader consumer ecosystem. Neither is dominant across every category.

What Claude models are available in 2026?

Three: Claude Opus 4.6 (1M context, 128k output, $15/M input), Claude Sonnet 4.6 (1M context, 64k output, $3/M input), and Claude Haiku 4.5 (200k context, 200+ tokens/sec, $0.80/M input). All available via claude.ai, Anthropic API, AWS Bedrock, and Google Vertex AI.

What is Claude Cowork and who should use it?

Claude Cowork is a desktop agent for knowledge workers launched January 12, 2026 in research preview. You give Claude access to a folder; it reads files, executes multi-step workflows, and produces deliverables autonomously. No coding required. Best for operations professionals, analysts, executives, and anyone who manages complex documents or recurring deliverables. Requires a paid Claude plan starting at $20/month.

What happened with Claude Code Security in February 2026?

Claude Code Security launched February 20, 2026 for Enterprise and Team customers. Using Opus 4.6, it found over 500 vulnerabilities in production open-source codebases through reasoning about data flows rather than pattern-matching. The launch caused major cybersecurity stock drops: CrowdStrike -8%, Okta -9.2%, Cloudflare -8.1%, Zscaler -5.5%. Every finding requires human approval before action.

Is Claude better than ChatGPT for coding in 2026?

For enterprise software engineering measured by SWE-bench, Claude Opus 4.6 (80.8%) outperforms most GPT models. GPT-5.3 Codex beats Claude on Terminal-Bench 2.0 (77.3% vs 65.4%), making it stronger for terminal-heavy workflows. Most professional developers use both: Claude for complex reasoning and large codebases, GPT-5.3 Codex for terminal-heavy batch operations.

How much does Claude cost in 2026?

Claude Free: $0 (Sonnet 4.6). Claude Pro: ~$20/month. Claude Max: $100 or $200/month. Team: $30/seat/month. Enterprise: custom. API: Haiku 4.5 at $0.80/M input, Sonnet 4.6 at $3/M input, Opus 4.6 at $15/M input.

What is adaptive thinking in Claude?

Adaptive thinking (thinking: {type: 'adaptive'}) is the new Extended Thinking API mode for Opus 4.6 and Sonnet 4.6. Unlike the deprecated budget_tokens approach, adaptive thinking lets Claude independently decide whether a prompt requires extended reasoning. Complex tasks get full chain-of-thought. Simple tasks skip reasoning entirely. This reduces unnecessary compute costs and removes manual reasoning management from developers.

What is Claude's context window and why does it matter?

Claude Opus 4.6 and Sonnet 4.6 support 1 million token context windows, approximately 750,000 words. Haiku 4.5 supports 200,000 tokens. Claude Enterprise starts at 500,000 tokens. This enables enterprises to process entire codebases, year-long document histories, or hundreds of contracts in a single prompt, which is not possible with 128k-capped models.

When is Claude 5 expected to release?

Based on code named 'Fennec' appearing in Google Vertex AI logs, Claude 5 is expected in mid-2026. Early signals suggest near-Opus performance at Sonnet prices, a Dev Team multi-agent mode, pricing 50% lower than current flagships, and persistent memory baked into the model's core architecture rather than layered on.

Recommended Reads

If you found this guide useful, these posts from Build Fast with AI go deeper on related topics:

Grok 4.20 Beta Explained: Non-Reasoning vs Reasoning vs Multi-Agent (2026)

GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5: Who Actually Wins? (2026)

Best ChatGPT Prompts in 2026: 200+ Prompts for Work, Writing and Coding

What Is Agenta: The LLMOps Platform Simplifying AI Development

References

1.      Claude Models Overview — Anthropic API Documentation

2.      Claude 4.6 What's New — Anthropic API Documentation

3.      Claude Code Security Launch — Anthropic

4.      Claude Code February 2026 Update Analysis — Nagarro

5.      GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5 — Build Fast with AI

6.      Grok 4.20 Beta Explained 2026 — Build Fast with AI

7.      Enterprise AI Comparison: Claude vs ChatGPT vs Gemini — Intuition Labs

8.      Best LLMs for Coding 2026 — Eden AI

Want to build real AI agents using Claude and other frontier models?

Join Build Fast with AI's Gen AI Launchpad - an 8-week structured program to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

OpenAI shipped GPT-5.4 on March 5, 2026. Thirteen days later, they dropped two more: GPT-5.4 Mini and GPT-5.4 Nano. The pace is relentless.

Here is what most coverage is missing: these are not cut-down versions of GPT-5.4. They are purpose-built for a completely different problem - and if you are still reaching for GPT-5 Mini out of habit, you are

overpaying and underperforming at the same time.

GPT-5.4 Mini runs over 2x faster than GPT-5 Mini while approaching flagship-level accuracy. GPT-5.4 Nano costs just $0.20 per million input tokens - cheaper than Google's Gemini Flash-Lite - and can describe 76,000 photos for $52. That changes the economics of building AI products in a serious way.

If you are building a coding assistant, an agentic system, or anything that hits OpenAI's API at scale, you need to understand exactly what these models can and cannot do.

What Is GPT-5.4 Mini?

GPT-5.4 Mini is OpenAI's fastest capable model for high-volume coding, reasoning, and multimodal tasks. Released on March 17, 2026, it is part of the GPT-5.4 family and brings most of what GPT-5.4 can do into a significantly faster and cheaper package.

OpenAI describes it as running more than 2x faster than GPT-5 Mini. That is not a marginal gain. On coding workflows where latency directly affects the product feel, this makes a real difference. GitHub Copilot immediately rolled GPT-5.4 Mini into general availability on the same day it launched - that signal alone tells you what the market thinks of it.

The model is multimodal. It handles text, images, and audio inputs. It connects to tools. It works inside agentic systems. On OSWorld-Verified - a benchmark that tests how well a model actually navigates a desktop computer by reading screenshots - Mini scored 72.1%, barely under the flagship's 75.0%. Both clear the human baseline of 72.4%. That is a result worth sitting with.

GPT-5.4 Mini is available in ChatGPT (Free and Go users can access it via the Thinking option in the + menu), in Codex, and through OpenAI's API.

What Is GPT-5.4 Nano?

GPT-5.4 Nano is OpenAI's smallest and cheapest model, built exclusively for speed and cost-sensitive workloads. It is API-only - no ChatGPT interface, no Codex toggle - which signals clearly that OpenAI sees this as a developer and infrastructure tool, not a consumer product.

OpenAI recommends Nano for classification, data extraction, ranking, and coding subagents that handle simpler supporting tasks. That framing matters. Nano is not trying to write an essay or reason through a complex problem. It is the workhorse in the background - the model processing a document, labeling a category, or routing a request while a larger model handles the parts that actually need intelligence.

According to Simon Willison, GPT-5.4 Nano's benchmark numbers show it out-performing GPT-5 Mini at maximum reasoning effort. That is the nano-class model beating the old mini-class at peak effort. The pace of progress on small models is genuinely fast.

GPT-5.4 Mini Pricing: Is It Free?

GPT-5.4 Mini is free for ChatGPT users on the Free and Go plans, available through the Thinking feature. That means most people can use it today without paying anything.

Here is how the ChatGPT subscription tiers work for GPT-5.4 Mini:

•       Free ($0/month): Access to GPT-5.4 Mini via the Thinking feature in the + menu

•       Go ($8/month): GPT-5.4 Mini access with expanded limits

•       Plus ($20/month): GPT-5.4 Mini as a rate limit fallback for GPT-5.4 Thinking

•       Pro ($200/month): Full GPT-5.4 Pro access with no rate limit caps

One nuance: for paid subscribers, GPT-5.4 Mini becomes the fallback model when you hit your GPT-5.4 rate limits. So it is less a downgrade and more a continuation - you keep working, just at slightly lower performance until the limit resets.

For developers using the API, Mini is not free. You pay per token. I think the free consumer access is strategic. OpenAI wants GPT-5.4 Mini to become the default baseline that people build on top of, and making it free in ChatGPT is the fastest way to make that happen.

GPT-5.4 Nano Pricing and API Costs

GPT-5.4 Nano costs $0.20 per million input tokens and $1.25 per million output tokens. This is API-only - there is no free tier or ChatGPT access for Nano.

To put those numbers in context: running 76,000 image descriptions costs approximately $52 using Nano. For high-volume classification or extraction pipelines, this is a meaningful drop in cost compared to any full-size model.

Nano is also cheaper than Google's Gemini 3.1 Flash-Lite, which is the benchmark most people use for ultra-cheap inference. That positioning is deliberate. OpenAI is not trying to compete with GPT-5.4 Pro on Nano - it is competing with the cheapest models from every other lab.

The Batch API is available for both Mini and Nano. Using it gives you a 50% discount on input and output tokens for non-time-sensitive tasks. If your pipeline runs nightly or in the background, Batch is almost always the right call for cost savings.

GPT-5.4 Mini vs Nano: Benchmarks and Speed

Here is a direct comparison on the benchmarks that matter most:

| Benchmark | GPT-5.4 Mini | GPT-5.4 Nano | Human Baseline |

| OSWorld-Verified | 72.1% | 39.0% | 72.4%

| SWE-Bench Pro | ~GPT-5.4 level | 52.4% | -

| Input Cost (API) | Higher | $0.20/M tokens | -

| Available In | ChatGPT + API | API only | -

The gap between Mini and Nano on OSWorld (72.1% vs 39.0%) is large. For tasks that require understanding visual interfaces, navigating a desktop, or doing anything complex with screenshots, Mini wins by a wide margin. Nano simply is not designed for that workload.

For SWE-Bench Pro - real GitHub-style software engineering tasks - Nano's 52.4% is still a real capability. It can handle code subagent work. It can read a file, fix a targeted bug, or output a structured payload. Just do not ask it to architect a system from scratch.

Perplexity Deputy CTO Jerry Ma tested both models in production: "Mini delivers strong reasoning, while Nano is responsive and efficient for live conversational workflows." That is the clearest summary of where each model belongs.

GPT-5.4 Mini vs GPT-5 Mini: What Actually Changed

GPT-5.4 Mini is not a minor update over GPT-5 Mini - it is a significant generational jump. The improvements hit four areas: coding, reasoning, multimodal understanding, and tool use.

The 2x+ speed improvement is the headline stat. But the accuracy gains matter just as much. On SWE-Bench Pro, GPT-5.4 Mini approaches the performance of the full GPT-5.4 model. On coding benchmarks, OpenAI says it consistently outperforms GPT-5 Mini at similar latencies.

The model also handles tool use more reliably. This is the quiet upgrade that builders care about. If you are running agents that call APIs, search the web, read documents, or interact with external services, better tool use reliability means fewer retries, fewer broken workflows, and less babysitting.

One thing that did not change: the general shape of the product. Mini is still the model for developers and free users. Nano is still API-only. GPT-5.4 is still the flagship. OpenAI's model strategy is converging around a clear three-tier approach - and I think this is smarter than the chaotic model lineup they had a year ago.

Real-World Use Cases for GPT-5.4 Mini and Nano

Both models are designed for high-volume, latency-sensitive workloads. Here is where each one belongs:

GPT-5.4 Mini is best for:

GPT-5.4 Mini belongs anywhere a user is actively waiting for a response. Coding assistants, agentic workflows that need planning and routing, computer-use apps reading screenshots, and document understanding at scale are all natural fits. The 72.1% OSWorld score is the real unlock here - it means Mini can actually navigate a real desktop, not just describe one. Nano is a different animal. You're not building a product on top of it.

You're using it as the invisible engine running classification pipelines, pulling structured data from invoices, ranking candidates, or handling the simple subtasks inside a larger multi-agent system. Nobody is watching

the clock when Nano runs. That's the point.

The simplest rule I can give you: if a user is staring at a loading spinner, use Mini. If no user is involved at all, evaluate Nano first.

The pattern: Mini is for when the user is waiting. Nano is for when the system is running in the background and nobody is watching the clock. If you are building a multi-agent system, the smarter architecture is a large model planning and coordinating, with Mini or Nano handling the grunt work in parallel.

Should Developers Use GPT-5.4 Mini or Nano?

For most developers, GPT-5.4 Mini is the right default — full stop. Fast, multimodal, cheaper than flagship GPT-5.4, and free for ChatGPT users. The fact that GitHub Copilot rolled it into general availability on launch day is not a coincidence. When a product used by millions of developers gets updated the same day a model ships, that's the market telling you something.

Use Nano specifically when three conditions are true: your task is well-defined and repetitive, no user is waiting on the result, and you are running enough volume that $0.20/M tokens actually moves the needle on your bill. If only two of those are true, Mini is probably still the better call. The reliability gap is real, even if the benchmark gap looks manageable on paper.

One honest criticism: OpenAI's model naming is starting to get exhausting. GPT-5.4 Mini, GPT-5.4 Nano, GPT-5.4 Pro, GPT-5.3 Instant, GPT-OSS - the lineup has grown fast and the differences between versions are not always obvious. I wish they would publish a clearer comparison table with benchmark scores side by side instead of making developers piece it together from multiple announcement posts.

That said: the models themselves are good. GPT-5.4 Mini running 2x faster than its predecessor while approaching flagship accuracy is exactly what the market needed. And Nano undercutting Gemini Flash-Lite on price is a signal that OpenAI is competing seriously at the low end, not just at the top.

Frequently Asked Questions

Is GPT-5.4 Mini free?

Yes, GPT-5.4 Mini is free for ChatGPT users on the Free and Go plans. Access it by selecting Thinking from the + menu in ChatGPT. API access is paid and billed per token like all OpenAI models.

What is GPT-5.4 Nano?

GPT-5.4 Nano is OpenAI's smallest, fastest, and cheapest model in the GPT-5.4 family. It is available exclusively through the API at $0.20 per million input tokens and $1.25 per million output tokens. OpenAI recommends it for classification, data extraction, ranking, and simple coding subagents.

What is the difference between GPT-5.4 Mini and GPT-5.4 Nano?

Mini is the capable, user-facing model: 72.1% on OSWorld, available in ChatGPT and the API, suited for real-time workflows. Nano is the infrastructure model: API-only, $0.20/M input tokens, built for background classification, extraction, and batch jobs where cost per call matters more than raw capability.

When was GPT-5.4 Mini released?

GPT-5.4 Mini and GPT-5.4 Nano were released on March 17, 2026, less than two weeks after the full GPT-5.4 model launched on March 5, 2026.

How fast is GPT-5.4 Mini compared to GPT-5 Mini?

GPT-5.4 Mini runs more than 2x faster than GPT-5 Mini while delivering higher accuracy across coding, reasoning, and multimodal benchmarks.

Is GPT-5.4 Nano available in ChatGPT?

No. GPT-5.4 Nano is API-only. It is not available through ChatGPT's consumer interface. Developers access it through the OpenAI API at $0.20 per million input tokens and $1.25 per million output tokens.

What benchmarks did GPT-5.4 Mini score on?

On OSWorld-Verified, GPT-5.4 Mini scored 72.1%, just below the flagship's 75.0% and above the human baseline of 72.4%. On SWE-Bench Pro, Mini approaches GPT-5.4's performance. GPT-5.4 Nano scored 52.4% on SWE-Bench Pro and 39.0% on OSWorld.

Can I use GPT-5.4 Mini for agentic workflows?

Yes. GPT-5.4 Mini is well-suited for agentic workflows, tool use, and multi-step tasks. It handles targeted code edits, codebase navigation, front-end generation, and debugging loops with low latency, making it a strong choice for coding agents and subagent systems.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•       OpenAI GPT-OSS Models: Complete Guide to 120B & 20B Open-Weight AI

•       Tiktoken: High-Performance Tokenizer for OpenAI Models

•       Instructor: The Most Popular Library for Structured Outputs

Want to learn how to build AI agents and apps with models like GPT-5.4 Mini and Nano?

Join Build Fast with AI's Gen AI Launchpad - an 8-week structured program to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

References

1.      Introducing GPT-5.4 Mini and Nano - OpenAI

2.      OpenAI Releases GPT-5.4 Mini and Nano - 9to5Mac (9to5mac.com)

3.      GPT-5.4 Mini and Nano, which can describe 76,000 photos for $52 - Simon Willison (simonwillison.net)

4.      OpenAI Releases GPT-5.4 Mini and Nano Models - Dataconomy (dataconomy.com)

6.      GPT-5.4 Mini is Now Generally Available for GitHub Copilot - GitHub Changelog (github.blog)

7.      ChatGPT's Free Tier Gets GPT 5.4 Mini Model - 9to5Google (9to5google.com)

A single person can operate like a team of 100 agents.

That is the exact sentence Harshil Mathur, CEO and co-founder of Razorpay, said at FTX 2026 in Bengaluru on March 12, 2026. And I think it is one of the most important statements made by any fintech founder this year, because Razorpay is not just talking about it. They shipped it.

On that day, Razorpay launched Agent Studio, described as the world's first AI-native agent platform built directly on top of payment infrastructure. Not beside it. Not connected to it via an API. On top of it, inside it, as the layer through which financial operations now happen autonomously.

India has over 10 million businesses on Razorpay, processing more than 1 billion transactions per quarter. The challenge has never been moving money - UPI, cards, and netbanking solved that years ago. The challenge has always been everything that happens around the transaction: recovering the abandoned checkout, fighting the chargeback, retrying the failed subscription, forecasting whether there is enough cash to run payroll on Friday. That work used to need human teams. Now it needs agents.

This post covers exactly what Razorpay Agent Studio is, how each agent works, what Google's search data tells us about who is asking about this and why, and what it means for anyone building on or competing with Razorpay.

Why RTO Is Destroying Your D2C Margins (And What AI Can Do About It)

Razorpay Agent Studio is a B2B AI agent marketplace and builder platform, launched March 12, 2026, that allows businesses to deploy autonomous AI agents for payment and post-payment operations. It is built on Anthropic's Claude Agent SDK and runs natively inside Razorpay's payment infrastructure, giving each agent direct access to transaction data, settlement records, customer activity signals, and third-party business tools like Shopify, Tally, QuickBooks, WhatsApp, Slack, and Shiprocket.

Unlike traditional payment automation that triggers fixed rules, Razorpay agents observe financial signals continuously, reason over context, and take action on their own. They do not wait to be told. They detect the abandoned cart and initiate outreach. They receive the chargeback and file the response. They see the failed subscription and apply a smarter retry. They spot the cash shortfall coming in 5 days and send an alert before it becomes a crisis.

Why this matters:

Payments are only the execution layer of commerce. Everything around the transaction - disputes, reconciliation, recovery, forecasting - still requires manual teams. Agent Studio is Razorpay's attempt to eliminate that manual overhead entirely.

The 8 AI Agents That Automate Payment Operations for Indian Businesses

Razorpay debuted eight production-ready agents at FTX 2026. Each is designed to address one specific, high-friction operation that previously required manual effort. Here is the complete breakdown:

How to automatically win chargeback disputes (without a team)

Chargebacks are a real problem for Indian merchants. When a customer disputes a transaction, the merchant has a tight window to respond with evidence, and most small businesses miss it simply because no one is monitoring. The Dispute Responder agent automatically collects transaction evidence (payment logs, delivery confirmation, customer activity), compiles an optimised response, and submits it before the deadline. Higher win rates. Zero manual effort.

How to recover failed subscription payments and reduce involuntary churn

Failed subscription payments are the silent killer of SaaS and D2C subscription revenue. Card expiry, insufficient balance, bank declines - these happen constantly. The Subscription Recovery Agent analyses the reason for failure, applies intelligent retry logic (not just 'try again in 24 hours'), and when retries are insufficient, triggers a voice call to the customer using ElevenLabs voice synthesis. That is a real person-quality voice call, not a robocall. I think this is the most technically impressive agent in the launch set.

How to reduce cart abandonment in India with AI-powered WhatsApp recovery

Razorpay is launching two variants of this agent, both targeting the same problem: someone starts checkout, then leaves. The SuperU-powered variant re-engages via WhatsApp or email with personalised offers. The Nugget by Zomato variant does the same for Zomato-integrated merchants. Both send a payment link to complete the purchase. The key innovation here is that this is not a generic reminder email - it is contextual outreach based on the specific transaction, the customer's loyalty status, and available discounts.

How small businesses in India can forecast cashflow without a CFO

This one is specifically for the 10 million small and medium businesses on Razorpay that do not have a CFO. The Cashflow Forecaster analyses transaction patterns and predicts the merchant's cash position 3-7 days ahead, with specific alerts for payroll risk, payout failures, and balance shortfalls. Getting a WhatsApp message on Monday that says 'you will be below minimum balance for payroll on Thursday - here are three options' is genuinely transformative for a small business owner.

How to reduce RTO on COD orders using AI address validation and risk scoring

Return-to-origin is one of the biggest margin killers for Indian D2C brands. Cash on delivery orders that get returned from bad pincodes or invalid addresses eat into shipping costs with no revenue. RTO Shield uses LLM-based address validation and historical bad-pincode intelligence to block high-risk COD orders before they ship. RTO Insights provides analytics across pincodes, products, and customer segments to identify what is driving returns systematically.

How to get your daily settlement summary on WhatsApp automatically

The simplest agent in the set, and maybe the one that will have the highest daily active usage. Settlement Insights sends a WhatsApp message every morning with a summary of yesterday's settlements. No dashboard login. No manual checking. Just the number that matters, delivered where you already are.

How to Cut Merchant Onboarding, Integration, and Reconciliation Time With AI

Alongside Agent Studio, Razorpay launched the Agentic Experience Platform - a complete reimagining of how merchants interact with Razorpay itself. It has three distinct capabilities, all powered by the same Claude Agent SDK foundation.

How to onboard a merchant in 5 minutes instead of 45

Merchant onboarding used to take 30-45 minutes. Provide PAN and a website URL. The platform auto-validates identity against CKYC and government infrastructure in real time, auto-detects business category from the website, and eliminates manual form-filling. Result: onboarding in approximately 5 minutes. That is a 6-9x improvement in activation speed, which matters enormously for merchant conversion rates.

How to query your payment data in plain English (no dashboard login needed)

The Agentic Dashboard replaces static data tables with a natural language interface. You can upload a screenshot of your bank statement and ask 'reconcile this with my Razorpay settlements' - the agent extracts UTR numbers, cross-references them against Razorpay records, and flags discrepancies. You can say 'why did this customer's payment fail?' and get an actual answer. This is genuinely new. Most payment dashboards show you the data. This one reasons over it.

How to integrate Razorpay payments in under 2 minutes with AI

Harshil Mathur demonstrated live at FTX 2026 that a developer can complete full payment integration in under two minutes using the Agentic Integration layer. The system auto-detects the tech stack (Claude Code, Replit, Emergent, custom frameworks), generates ready-to-paste code, and handles the setup. The old gold standard was 5-hour integration. Two minutes is a category shift.

Why Razorpay Built on Claude: The AI Engine Behind Every Agent

The choice to build on Anthropic's Claude Agent SDK is not a minor detail. It is the foundational technical decision that explains why Razorpay Agent Studio works the way it does.

Claude was renamed from the Claude Code SDK to the Claude Agent SDK in late 2025, reflecting that it had evolved far beyond coding assistance into a general-purpose agentic runtime. Razorpay's CPO Khilan Haria stated the company evaluated multiple AI providers and chose Claude for its advanced reasoning capabilities, safety-first design philosophy, and suitability for high-stakes financial workflows where errors are costly.

Each Razorpay agent runs inside a Claude reasoning loop: it observes signals from Razorpay's payment data, reasons over what action to take, executes that action via Razorpay's 400+ APIs and integrated third-party tools, and reports results. Agents operate within consent guardrails - Harshil Mathur was specific about this: the agent never sees raw financial data beyond what is necessary for the task, and all actions occur within the merchant's defined permissions.

Irina Ghose, Managing Director of Anthropic India:

"Razorpay's work with Claude shows how AI agents can address real commerce challenges - recovering revenue, resolving disputes, and predicting cash flow. It's a great example of what AI can do when it's embedded into the operating fabric of business."

The no-code agent builder, currently in beta, uses Claude's natural language understanding to let non-technical users define agent behaviour in plain English. Describe the task, select the systems the agent can access, set the guardrails, and deploy. No engineering dependency.

What Is Agentic Commerce and Why It Will Replace the Checkout Page in India

Beyond Agent Studio, Razorpay is building what they call agentic commerce - the ability to complete a purchase entirely through a conversational interface inside an existing app, without navigating menus or checkout pages.

Harshil Mathur described it simply at FTX 2026: 'You can open the Zomato app, chat with it and say, hey, I want samosa from this, I want chai from this, and the Zomato app can buy it for you. Completely autonomous just by chatting on it.'

Razorpay is piloting this with Zomato, Swiggy, PVR Inox, Vodafone Idea, Bluestone, and Honasa (The Derma Co). Each pilot embeds Razorpay's payment infrastructure into the conversational layer of these apps, so when the AI assistant recommends a product, the payment happens in the same flow. Discovery, decision, and payment - all inside one conversation.

This is not a feature. This is a redefinition of what checkout means. The implications for conversion rates, average order values, and the entire checkout abandonment problem are significant. I think agentic commerce will become the dominant commerce model for mobile-first markets like India within 3 years.

Razorpay also announced that developers can sell through ChatGPT with zero code using a Razorpay integration - enabling merchants to monetise their products inside the ChatGPT interface from day one.

Which Indian Businesses Benefit Most From AI Payment Agents (And How to Start)

Agent Studio is relevant to any business that processes payments on Razorpay and has operational overhead around managing those payments. Specifically:

•       E-commerce and D2C brands - deploy the Abandoned Cart Conversion Agent, RTO Shield, RTO Insights, and Settlement Insights immediately

•       SaaS and subscription businesses - the Subscription Recovery Agent is the highest-impact agent for reducing involuntary churn

•       Any business receiving international or premium card payments - the Dispute Responder Agent pays for itself after the first successful chargeback win

•       SMEs managing cash flow manually - the Cashflow Forecaster Agent is genuinely life-changing for founders who are managing payroll from a single checking account

•       Developers and technical teams - the MCP server, llms.txt in the developer docs, and Agentic Integration make Razorpay the most AI-developer-friendly payment gateway in India

Access is via early access signup at razorpay.typeform.com/to/hGkU4Jpb. The platform is currently free during the beta phase. Razorpay has indicated a future token-based pricing model based on agent task volume and complexity.

One honest caveat: Agent Studio is days old as of this writing. The agents are production-ready but the overall ecosystem is early. The no-code builder is in beta. The open third-party marketplace for developers has not launched yet. If you are evaluating whether to rely on specific agents for critical operations, request a demo before committing.

The Future of AI Payment Automation in India: What Changes in the Next 24 Months

I want to be direct about what I think is actually happening here, because the media coverage has been mostly descriptive and not analytical enough.

Razorpay is not just adding AI features to a payment gateway. They are attempting a category redefinition. A payment gateway moves money. A financial operating system manages the entire commercial operation around money. Agent Studio is the first product layer of that operating system. The agents are the staff.

The global agentic payments movement is accelerating simultaneously. PayPal launched its Agent Toolkit for developers. Visa announced Intelligent Commerce. AWS published its x402 agentic payment protocol. Coinbase's x402 enables AI agents to make micro-payments between machines. Within fintech, a consensus is forming that the next era of commerce will be AI-mediated, not human-navigated.

India is uniquely positioned for this shift. UPI processes 17+ billion transactions per month. Digital payment adoption is mainstream. And 90%+ of businesses are SMEs without dedicated finance teams - exactly the segment that benefits most from agents doing the work of a team.

The risk I see: the quality of agents at launch is promising but unproven at scale. Agent reliability in financial contexts is not the same as agent reliability in writing tasks. A hallucinated chargeback response that loses a dispute costs real money. Razorpay has addressed this with consent guardrails and human-in-the-loop options, but merchant trust will need to be earned through demonstrated performance, not announced through launch events.

That said - the direction is right. The foundation (Claude Agent SDK) is the strongest available. The distribution (10 million merchants on existing Razorpay) is exceptional. If execution matches ambition, Agent Studio will reshape how Indian businesses run their financial operations within 24 months.

Frequently Asked Questions

How do I reduce RTO on Razorpay?

Razorpay Agent Studio is the world's first AI agent platform built natively on payment infrastructure, launched March 12, 2026 at FTX 2026 in Bengaluru. Built on Anthropic's Claude Agent SDK, it is a B2B marketplace where merchants can deploy pre-built AI agents for dispute management, cart recovery, subscription retry, cashflow forecasting, and RTO reduction - or create custom agents using a no-code builder. Access is via early signup at Razorpay's website; it is currently free in beta.

Can AI automatically recover failed subscription payments?

Razorpay AI is the company's umbrella strategy for embedding artificial intelligence across its entire product suite. It includes Agent Studio (autonomous payment agents), the Agentic Experience Platform (AI-native merchant interactions), biometric card authentication with Mastercard, voice-first payments with Gnani.ai and SuperU, and agentic commerce integrations with Zomato, Swiggy, PVR Inox, and Vodafone Idea. All launched at FTX 2026 on March 12, 2026.

What AI model powers Razorpay Agent Studio?

Razorpay Agent Studio is built on Anthropic's Claude Agent SDK (formerly the Claude Code SDK, renamed in late 2025). Claude powers the reasoning, context understanding, and action execution capabilities of every agent on the platform. Razorpay chose Claude over other options specifically for its advanced reasoning and suitability for high-stakes financial workflows where decisions have real monetary consequences.

How many agents does Razorpay Agent Studio have at launch?

Razorpay launched eight agents at FTX 2026: Dispute Responder, Subscription Recovery (with ElevenLabs voice), two variants of Abandoned Cart Conversion (SuperU and Nugget by Zomato), Cashflow Forecaster, RTO Shield, RTO Insights, and Settlement Insights. A No-Code Agent Builder is also available in beta for creating custom agents. An open third-party developer marketplace is planned for a future release.

Is Razorpay Agent Studio available for small businesses?

Yes - small businesses are the primary target. Harshil Mathur's core pitch at FTX 2026 was that small businesses lack the teams to manage post-payment operations that large companies handle automatically. Agent Studio is designed to give a 5-person team the operational capacity of a 100-person finance department. The no-code builder means no developer is needed to create or deploy agents.

Is Razorpay Agent Studio free?

Yes, during the current beta phase. Razorpay has not announced a paid pricing date, but has indicated that a token-based model will be introduced where merchants pay based on the volume and complexity of tasks agents perform. Get on the early access list now to lock in beta access before pricing is introduced.

What is the difference between Razorpay Agent Studio and the Agentic Experience Platform?

Agent Studio is the marketplace and builder for deploying autonomous agents that handle payment operations (disputes, cart recovery, subscriptions, cashflow). The Agentic Experience Platform is a redesign of the merchant experience itself - covering how merchants onboard (5-minute KYC), integrate payments (under 10 minutes), and interact with their dashboard (natural language). They are complementary products launched together at FTX 2026.

What is agentic commerce and how is Razorpay enabling it?

Agentic commerce is a shopping experience where a user can express intent in natural language inside an existing app - no menus, no search, no checkout form - and an AI agent completes the purchase. Razorpay is enabling this with Zomato, Swiggy, PVR Inox, Vodafone Idea, Bluestone, and Honasa by embedding its payment stack into conversational AI interfaces, so payment is a natural part of the conversation rather than a separate step.

Does Razorpay Agent Studio work with Shopify?

Yes. Razorpay Agent Studio integrates with Shopify, WhatsApp, Shiprocket, Slack, Tally, and QuickBooks, giving agents access to cross-platform business data. For e-commerce merchants on Shopify, the Abandoned Cart Conversion Agent, RTO Shield, and Settlement Insights are immediately deployable. Developer integrations also support Claude Code, Replit, and Emergent.

How does Razorpay use AI to prevent payment fraud?

Every transaction on Razorpay is now monitored by an AI security agent that analyses whether a transaction's pattern matches known fraud signatures and blocks suspicious activity before it completes. Harshil Mathur confirmed at FTX 2026 that this agent never sees raw financial data beyond what is required, and all actions occur within the guardrails of the merchant's consent settings.

How does Razorpay for developers work with AI?

Razorpay provides 400+ documented API endpoints, a Model Context Protocol (MCP) server for LLM-agent integration, and an llms.txt in the developer docs for AI coding tools. The Agentic Integration layer auto-detects a developer's tech stack and completes payment setup in under 10 minutes across Claude Code, Replit, Emergent, and standard frameworks.

Who is the CEO of Razorpay?

Harshil Mathur is the co-founder and CEO of Razorpay. He is an IIT Roorkee alumnus who co-founded Razorpay in 2014 with Shashank Kumar. As of 2025, his net worth is approximately $1.04 billion (Hurun India Rich List 2025). He personally announced Agent Studio at FTX 2026.

What is the commission of Razorpay?

Razorpay charges 2% per successful domestic transaction plus 18% GST, making the effective rate approximately 2.36%. International cards, AMEX, Diners, EMI, and corporate cards are charged 3% plus GST. There is no setup fee, no annual maintenance charge, and no minimum transaction commitment. Agent Studio is currently priced separately (free in beta).

Is Razorpay good for freelancers?

Yes. Razorpay supports freelancers and unregistered businesses with payment links, QR codes, no-code payment pages, UPI acceptance, and PAN-only registration with no setup fees. The new Agentic Onboarding reduces account activation to under 5 minutes. Freelancers do not need Agent Studio's operational agents but benefit significantly from the payment link infrastructure and fast onboarding.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•         Top 11 AI-Powered Developer Tools Transforming Workflows in 2025

•         AI in 2026: Your Survival Guide to the Fourth Year of Generative AI

•         7 AI Tools That Changed Development — December 2025 Guide

Want to build AI payment agents and automation systems like Razorpay?

Join Build Fast with AI's Gen AI Launchpad - an 8-week hands-on program that takes you from zero to shipping real AI agents, apps, and automation workflows.

Register here: buildfastwithai.com/genai-course

References

1. Agent Studio: AI Agents by Razorpay (official launch post) - Razorpay Blog - March 12, 2026

2. Reimagining Merchant Experience with the Razorpay Agentic Platform - Razorpay Blog - March 12, 2026

3. Agentic Payments: The Future of In-App Commerce in 2026 - Razorpay Blog -March 12, 2026

4. Razorpay unveils world's first Agent Studio to automate payments - ANI News / The Tribune - March 12, 2026

5. Razorpay rolls out AI Agent Studio for payments - The Paypers - March 2026

6. Razorpay Launches World's First AI-Native Agent Studio - Enterprise IT World - March 2026

7. Razorpay Launches AI Agent Studio to Automate Business Payments - BankersAdda - March 2026

8. Building agents with the Claude Agent SDK - Anthropic / Claude -September 2025

9. Deep Dive: Agentic AI in Payments and Commerce- Fintech Wrap Up - June 2025

10. Razorpay CEO quote: 'A single person can operate like a team of 100 agents' - NewKerala / ANI - March 12, 2026

Your Google Workspace subscription already includes one of the most capable AI assistants on the planet. And I'd bet most of your team hasn't touched it.

In January 2025, Google made a move that still doesn't get enough credit: they stopped selling Gemini as an expensive add-on and folded it directly into every Business and Enterprise Workspace plan. The same AI that previously added $18 per user per month to your bill? It's now included for roughly $2 more than your old plan without AI. That's a remarkable value shift, and it changes the math entirely for teams sitting on the fence.

I've been tracking these updates closely, and what Google has shipped into Workspace through early 2026 is genuinely impressive. This isn't surface-level autocomplete. Gemini is now embedded in Gmail, Docs, Sheets, Slides, Drive, Meet, Chat, and even a new video app called Vids. Every app. Every flow. Already there.

This guide covers every Gemini feature currently live in Google Workspace, app by app, with real data, the latest 2026 updates, and honest takes on what's actually worth using. 

What Is Gemini in Google Workspace?

Gemini is Google's flagship AI model, now integrated natively across the entire Google Workspace ecosystem. It is not a chatbot in a separate tab. It lives inside your existing apps and has direct context access to your emails, documents, calendars, and meetings.

Think of it as the difference between a consultant you have to brief from scratch every time versus a team member who was in every meeting, read every document, and is already up to speed. The Gemini side panel in Gmail, Docs, Sheets, Slides, Drive, and Chat is the clearest expression of this philosophy: one click, instant AI assistance, full context from wherever you're working.

As of March 2026, Gemini 3 Flash is the default model powering Workspace AI features for most interactions, with Gemini 3 Pro available for complex reasoning tasks through the AI Expanded Access add-on. The combination of model quality and deep product integration is what separates Workspace Gemini from any standalone AI tool.

Gemini in Gmail: Smarter Inbox, Less Time Drafting

Email is where most knowledge workers lose 2 to 3 hours every day. Gemini in Gmail attacks this problem from four angles simultaneously.

Help me write

You give Gemini a subject line, a few bullet points, or a rough sentence, and it produces a fully drafted, tone-appropriate email. It adjusts formality based on context. Write to a vendor? Professional and clear. Reply to a colleague about a lunch plan? Casual and quick. The drafts aren't perfect on the first pass, but they get you to 80% in 10 seconds, which is the entire point.

Thread summarization

Open any 40-reply thread, click Summarize, and Gemini gives you the key decisions, action items, and unresolved questions in three to five sentences. I've watched teams cut email review time by half just from using this feature on client chains.

AI Overviews in Gmail Search

When you search your inbox, Gemini now generates an immediate plain-English answer based on your email content, not just a list of matching threads. Ask "What did the vendor say about the shipping delay?" and you get the answer, not 47 threads to dig through.

Help me schedule (Now Supports Groups)

Introduced in October 2025 and expanded to group meetings in February 2026, this feature detects when you're trying to coordinate a time in an email thread and surfaces a "Help me schedule" button. It then proposes time slots that work across all recipients whose calendars you can see. No more back-and-forth chains just to find a 30-minute window.

Honest take: "Help me write" is the only Gemini feature I've seen near-universal adoption on across different teams. It's the fastest path to productivity gains, and it requires zero learning curve. Start here.

Gemini in Google Docs: Your AI Writing Partner

Docs is where Gemini gets serious for knowledge workers. The March 2026 update was the biggest improvement to Docs AI since launch, so a lot of what you'll read online is already outdated.

Help me create

Provide a prompt in the side panel or the new bottom bar and Gemini generates a first draft instantly, drawing from your files and emails as context sources. The March 2026 update made this much more personalized: you can say "draft a newsletter for our neighborhood association using the meeting minutes from my January HOA meeting and the list of upcoming events," and it pulls both documents automatically.

Match writing style and format

This is an underrated feature. "Match writing style" unifies voice and tone across a document so it sounds like one author wrote the whole thing. "Match doc format" aligns your document to the structure of a reference doc you provide. For teams with multiple contributors writing different sections, this alone is worth the plan upgrade.

Summarize and ask questions

Drop a 50-page report into Docs and ask Gemini to give you the executive summary, the three biggest risks, or what the author recommends for Q3. It reads the document and answers directly. Legal review, investor reports, policy documents: the use cases here are enormous.

The 95-participant study Google ran showed Fill with Gemini dramatically outperforming manual data entry on a 100-cell Sheets task. The same principle applies in Docs: Gemini does the tedious structured work faster and with fewer errors than humans doing it manually.

Gemini in Google Sheets: Spreadsheets Without the Headache

Spreadsheets have always had a brutal learning curve. Gemini flattens it.

Help me organize

Describe your data goal in plain language and Gemini builds the sheet structure for you. "Create a monthly budget tracker with columns for marketing, operations, HR, planned vs. actual, and a variance column" produces exactly that in seconds. No template hunting, no manual column setup.

Fill with Gemini

This is the standout feature in Sheets. Gemini intelligently populates cells based on patterns, existing data, and context. In a controlled study across 95 participants, it significantly outperformed manual entry on a 100-cell task in both speed and accuracy. For data-heavy workflows, the time savings compound fast.

Formula assistance and data analysis

Don't know which formula calculates a 90-day rolling average? Ask in natural language. Gemini writes the formula, explains what it does, and inserts it in the right cell. For analysis, you can ask "Which product category had the highest quarter-over-quarter growth?" and get a plain-English answer without building a pivot table.

I think Sheets AI is underrated compared to the Gmail and Docs features. The ceiling is much higher. Once you start asking analytical questions against real operational data, the productivity gains are substantial.

Gemini in Google Slides: From Blank Deck to Done

Creating a polished deck has always been time-consuming because it's two jobs: writing the content and making it look good. Gemini attacks both.

Help me visualize

Describe a concept - a customer journey, a system architecture, a product roadmap - and Gemini generates a slide with suggested layout, placeholder content, and design elements. You refine rather than build from zero.

Generate entire decks from a prompt

Give Gemini a topic, an audience, and a target length and it produces a full slide deck outline with content suggestions for each slide. The quality varies, but as a starting point for a 12-slide investor deck or a training presentation, it cuts hours off the initial creation time.

Advanced image generation with Nano Banana Pro

On higher-tier plans, Gemini generates custom images using Nano Banana Pro directly inside Slides. You describe the visual you need and it appears. No stock photo subscription, no designer request, no waiting. This feature is available with standard limits on most Business plans and with higher limits through the AI Expanded Access add-on introduced in early 2026.

Gemini in Google Meet: Meetings That Stop Wasting Hours

This is the highest-ROI Gemini feature for most teams, and it's the one with the most visible before-and-after.

Take notes for me

Gemini listens to your meeting, transcribes it in real time, and delivers a structured Google Doc after the call with a summary, key decisions, and action items, all organized and labeled. The admin can configure whether this runs automatically for all meetings or only when users opt in.

Catch me up

Join a meeting 10 minutes late? Click "Catch me up" and Gemini gives you a concise summary of everything discussed so far. You can re-enter the conversation without interrupting the flow to ask what you missed.

Audio and video enhancement

Gemini improves audio clarity and video quality in real time during Meet calls. For remote team members with inconsistent setups, noisy environments, or older webcams, this makes a real difference in meeting quality.

Speech translation (rolling out in 2026)

Live speech translation in Meet is currently rolling out in 2026, enabling real-time translation across languages during calls. For international teams, this is a significant capability that previously required third-party tools.

Gemini in Google Drive and Chat: Your AI File Brain

Drive: Ask Gemini about your files

The "Ask Gemini" feature in Drive lets you query across your entire file library in natural language. Compare two vendor contracts and highlight the cost differences. Find everything related to a specific client project. Get a summary of a document you've never opened. The March 2026 update made this available in beta for Drive in the US for Google AI Ultra and Pro subscribers, with broader rollout planned.

Chat: Thread summaries and smart replies

In busy team channels, Gemini summarizes long conversation threads so you can catch up without scrolling through hundreds of messages. Smart replies in Chat go beyond generic suggestions - Gemini reads the actual conversation and generates replies that match the content and context of what's being discussed.

Google Vids and Workspace Studio: The New Power Apps

Google Vids

Google Vids is an AI-native video creation app built directly into Workspace. It's designed for business presentation-style videos: product demos, training content, team announcements, marketing explainers. With Gemini integrated, you describe a video concept, and Vids generates a script, visual suggestions, and a structured storyboard. Video generation using Veo 3.1, including AI avatars, is available through the AI Expanded Access add-on announced in early 2026.

Workspace Studio

Workspace Studio is the biggest new Gemini capability for power users. It's an agentic automation hub built into Workspace that lets you create workflows in plain English, no code required. Automate email labeling. Set up a workflow that delivers pre-meeting briefings automatically. Create triggers that generate follow-up task docs after every call. The feature is rolling out through early 2026 with standard access included in most Business and Enterprise plans.

Workspace Studio is where I see the most under-explored potential. Most teams are still using Gemini feature by feature. Studio lets you chain them into persistent, automated workflows. That's the real multiplier.

Google Workspace Gemini Pricing: What Do You Actually Get?

In January 2025, Google restructured Workspace pricing to include Gemini AI features without requiring a separate add-on purchase. A Business Standard customer who was previously paying $32 per user per month (Workspace + Gemini Business add-on) now pays $14 per user per month. That's the same AI for less than half the previous cost.

Here's how Gemini features map to Workspace editions:

The AI Expanded Access Add-On (New in 2026)

Starting March 1, 2026, teams that need higher usage limits on advanced AI capabilities can purchase the AI Expanded Access add-on. This unlocks higher limits on Nano Banana Pro image generation, Veo 3.1 video generation with AI avatars, deeper Gemini 3 Pro reasoning in the Gemini app, larger NotebookLM source libraries, and more Workspace Studio automation runs.

Standard access to all core features remains included in Business and Enterprise plans at no additional cost. The add-on is for teams pushing the limits of daily AI usage at scale.

Privacy, Security, and Enterprise Compliance

Every enterprise AI conversation eventually comes back to data. Google's position on Workspace data and Gemini is clear: your data, prompts, and AI-generated responses are never used to train Gemini models outside your organization's domain without explicit permission. Your data is not sold and is not used for ad targeting.

Gemini for Workspace holds a comprehensive set of certifications: SOC 1/2/3, ISO 27001, ISO 27017, ISO 27018, ISO 42001 (the international AI management standard), and it supports HIPAA compliance configurations for healthcare organizations. Gemini only retrieves data that the requesting user has permission to access. Your existing Workspace data security controls apply automatically to all AI features.

For Enterprise editions, admins can manage Gemini feature access granularly across the organization - turning specific features on or off, controlling AI note-taking in meetings, and blocking Workspace Studio from specific API controls.

How to Enable Gemini in Your Google Workspace

Getting started is straightforward for most organizations. Here's the practical path:

14.   Check your plan: Log into the Google Admin Console (admin.google.com). Your Workspace edition determines which Gemini features are available.

15.   Admin feature access: In the Admin Console, navigate to Apps > Google Workspace > Gemini. Enterprise admins can manage access to individual features. All admins can control whether the Gemini app itself is on or off.

16.   Enable NotebookLM and Google Vids: These are additional services that must be turned on separately in the Admin Console under Apps > Additional Google Services.

17.   Workspace Studio: Enable or disable through Apps > Google Workspace > Workspace Studio. API controls allow blocking Studio from specific integrations if needed.

18.   End user access: Once enabled at the admin level, users see the Gemini icon in Gmail, Docs, Sheets, Slides, Drive, and Chat. Click to open the side panel and start. No additional setup required.

For individual Google AI Pro or Ultra subscribers not on a Workspace plan: Gemini at gemini.google.com gives you access to the Gemini app and personal features, but the deep Workspace integration (side panels, context-aware features, Meet AI) is only available through Workspace Business and Enterprise plans.

Frequently Asked Questions

What can Gemini do in Google Workspace?

Gemini is integrated across Gmail, Docs, Sheets, Slides, Drive, Meet, Chat, Vids, and Workspace Studio. It drafts emails, summarizes documents and threads, generates spreadsheet formulas, creates slide decks, takes meeting notes, automates multi-step workflows, and answers questions about your files. The Gemini side panel provides contextual AI assistance in every major app.

Do you get Gemini free with Google Workspace?

Yes. Since January 2025, Gemini AI features are included in Google Workspace Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, and Enterprise Plus plans at no additional cost. Business Starter includes a limited version with restricted daily prompts. The AI Expanded Access add-on (available from March 2026) unlocks higher usage limits for advanced features.

Is Gemini Business better than Gemini Enterprise?

'Gemini Business' and 'Gemini Enterprise' were the names of the old Workspace add-ons, which were discontinued in January 2025. Today, the distinction is between Workspace Business and Enterprise editions. Enterprise plans add admin controls for managing Gemini feature access across the organization, which is the primary additional capability over Business plans.

How do I enable Gemini in Gmail on Workspace?

If your organization is on a Workspace Business Standard or higher plan, the Gemini side panel in Gmail is enabled by default. If you don't see the Gemini icon in Gmail, ask your Workspace admin to verify that Gemini features are enabled in the Admin Console under Apps > Google Workspace. Individual users cannot enable Workspace AI features independently.

What is Google Workspace Studio?

Workspace Studio is a new agentic automation feature in Google Workspace that lets users create multi-step AI workflows in plain English, without coding. Examples include automatically labeling emails, generating pre-meeting briefing documents, and creating follow-up task docs after calls. It began rolling out in late 2025 and is available to Business and Enterprise customers in 2026.

Do I need Google Workspace to use Gemini?

No. Gemini is also available as a standalone consumer product through gemini.google.com and as Google AI Pro ($19.99/month) or AI Ultra. However, the Workspace-integrated features - side panels in Gmail and Docs, Meet AI note-taking, Drive search, Workspace Studio - are only available through Workspace Business and Enterprise plans.

How does Google protect my data when I use Gemini in Workspace?

Google states that prompts, responses, and Workspace data used with Gemini are not used to train models outside your organization without permission and are not sold or used for ad targeting. Workspace Gemini holds SOC 1/2/3, ISO 27001/17/18, and ISO 42001 certifications, and can be configured for HIPAA compliance. Gemini only accesses data the requesting user already has permission to view.

What is the AI Expanded Access add-on?

Announced in early 2026, the AI Expanded Access add-on is a paid upgrade for Workspace Business and Enterprise customers who need higher usage limits on advanced AI capabilities. It covers more generations with Nano Banana Pro in Slides, more video generation with Veo 3.1 in Vids (including AI avatars), deeper Gemini 3 Pro reasoning access, larger NotebookLM source libraries, and more Workspace Studio automation capacity. Standard access to all core AI features remains included in base plans.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

• Top 11 AI-Powered Developer Tools Transforming Workflows in 2025

• 7 AI Tools That Changed Development — December 2025 Guide

• AI in 2026: Your Survival Guide to the Fourth Year of Generative AI

References

1. The future of AI-powered work for every business -Google Workspace Blog

2. Gemini AI features now included in Google Workspace subscriptions - Google Workspace Help

3. Get higher access to advanced AI in Google Workspace - Google Workspace Updates Blog

4. Google shares Gemini updates to Docs, Sheets, Slides and Drive - Google Blog (March 2026)

5. Expanding Google AI to more of Google Workspace - Google Workspace Updates Blog

6. Help me schedule expanded to group meetings - Google Workspace Updates Blog (February 2026)

7. Gemini for Google Workspace: Your Complete Guide in 2026 - Refractiv

Want to build AI-powered tools on Google Workspace and beyond?

Join Build Fast with AI's Gen AI Launchpad - an 8-week structured program to go from 0 to 1 in Generative AI. Hands-on projects, live sessions, and a community of 30,000+ builders.

Register here: buildfastwithai.com/genai-course

Open-source AI just made a decision that closed-source labs should be genuinely worried about.

On March 11, 2026, NVIDIA dropped Nemotron 3 Super at GTC. A 120-billion-parameter model. Open weights. Free to self-host. And it just hit 60.47% on SWE-Bench Verified, leading every open-weight model on the planet for real-world software engineering tasks. That same week, GPT-5.3-Codex and Claude Opus 4.6 were sitting at 80% on the same benchmark, confident in their proprietary moats. But here's the thing nobody is talking about: Nemotron runs on 64GB of RAM. You can deploy it today. For free.

I've been watching the gap between open and closed AI narrow month by month. In 2023 it was years. In 2024 it was months. Today? For coding specifically, you are choosing between "20 points better and costs money" versus "free forever, getting better every quarter, and already good enough for most production work." That choice is going to define a lot of engineering budgets in 2026.

This piece breaks down the three most important coding AI releases of the year: NVIDIA Nemotron 3 Super, GPT-5.3-Codex, and Claude Opus 4.6. Real benchmarks, real cost math, real deployment scenarios.

What Is NVIDIA Nemotron 3 Super?

Nemotron 3 Super is NVIDIA's open-weight flagship for agentic coding, released March 11, 2026. The headline architecture is unusual: a hybrid that combines Mamba-2 state space model layers, Transformer attention layers, and a new mixture-of-experts design called LatentMoE, all in one 120-billion-parameter model with only 12 billion active parameters per token.

That 12B active parameter number is what makes Nemotron competitive. You get the reasoning depth of a 120B model at the compute cost of something far smaller. NVIDIA's LatentMoE compresses tokens into a latent space before routing to experts, activating 4x more experts at the same compute cost as older MoE designs. The result is 2.2x higher inference throughput than GPT-OSS-120B and up to 7.5x faster than Qwen3.5-122B on comparable hardware.

The context window is 1 million tokens. Unlike most models that degrade badly past 256K, Nemotron 3 Super holds 91.75% accuracy at 1M tokens on the RULER benchmark versus GPT-OSS-120B's 22.30% at the same length. For agentic coding workflows involving large codebases, that retention difference is not trivial.

I think NVIDIA is playing a long game here. They train the hardware most AI runs on, and now they are releasing the model that runs best on that hardware. Nemotron 3 Super was pre-trained for over 25 trillion tokens with a data cutoff of June 2025, trained natively in NVFP4 4-bit precision from the first gradient update. The entire training recipe is publicly released.

SWE-Bench Scores Side by Side

SWE-Bench Verified is still the best single proxy for real-world software engineering capability. It tests models on actual GitHub issues, measures whether they can generate patches that pass unit tests, and runs everything in an isolated environment. Here is where things stand as of March 2026:

The 20-point gap between Nemotron and the top proprietary models is real and meaningful for complex tasks. For multi-file refactors with intricate dependencies or obscure bug traces, Opus 4.6 and GPT-5.3-Codex will outperform.

But here is the contrarian read: the benchmark gap looks bigger than the real-world gap. SWE-Bench Verified is Python-only. The harness (the agent scaffolding around the model) explains enormous variance, sometimes more than 22 points on SWE-Bench Pro. Nemotron's 45.78% on SWE-Bench Multilingual versus GPT-OSS-120B's 30.80% suggests that on non-Python tasks, the gap narrows considerably.

GPT-5.3-Codex has a meaningful edge on Terminal-Bench 2.0, scoring 77.3% versus Opus 4.6's 65.4%, an 11.9-point lead for CLI-heavy workflows. If your work is infrastructure-as-code, DevOps automation, or terminal-based debugging loops, Codex is the specialist for that job.

Open Source vs Paid: When Does Free Win?

The honest answer is: free wins more often than the benchmark leaderboard suggests.

The reason is economics. A team running 50 coding tasks per day on Claude Opus 4.6 at $5 per million input tokens and $25 per million output tokens accumulates real costs fast. GPT-5.3-Codex pricing is in a similar range for paid users. Nemotron 3 Super via DeepInfra API runs at $0.10 per million input and $0.50 per million output tokens. That is roughly 10-50x cheaper per token before you even consider self-hosting.

Self-hosting is where the economics flip entirely. Nemotron 3 Super can run on a machine with 64GB of RAM or VRAM at GGUF quantized precision. The NVIDIA Open Model License is commercially usable, grants perpetual royalty-free rights, and allows derivative fine-tuned models as long as attribution is included.

Three scenarios where free clearly wins:

•       High-volume automation: Batch coding agents, automated code review at CI/CD scale, or test generation pipelines. The cost difference at 10M+ tokens per month dwarfs the accuracy gap.

•       Data privacy requirements: Many enterprises cannot send proprietary code to any external API. For these teams, Nemotron 3 Super is not just cheaper, it is the only viable frontier option.

•       Budget teams and solo devs: For an indie developer or a small startup, $100-500 per month on API costs for AI coding assistance has real budget impact. Nemotron removes that constraint.

Where proprietary wins:

•       Single-turn tasks where accuracy is binary and debugging wasted time costs more than API fees

•       Terminal-heavy DevOps workflows where GPT-5.3-Codex's 77.3% Terminal-Bench is best available

•       Deep scientific reasoning tasks requiring Opus 4.6's 91.3% GPQA Diamond performance

Local Deployment Cost Analysis

Let me make this concrete with numbers.

Self-Hosting (BF16 Full Precision)

•       Hardware requirement: 8x H100-80GB GPUs

•       Cloud rental estimate: ~$20-25/hour per node

•       For 8 hours of daily batch workloads: ~$160-200/day

•       Monthly cost: ~$4,800-6,000 for dedicated capacity

•       Best for: Enterprise teams doing high-volume automated code review

Self-Hosting via GGUF Quantization

•       Hardware requirement: 64GB RAM/VRAM (single A100 80GB or Mac Studio Ultra)

•       Comparable cloud instance: ~$2-4/hour

•       For 8 hours/day: $16-32/day, or run locally at near-zero marginal cost

•       Best for: Solo developers, small teams, or anyone with existing GPU hardware

API Cost Comparison

The honest conclusion: for teams spending more than $500/month on AI coding APIs, it is worth running a two-week pilot of Nemotron 3 Super on your actual tasks and measuring acceptance rate, not benchmark score. Generic benchmarks do not predict your specific repo.

What Each Model Does Best

These three models have genuinely different personalities, not just different scores.

NVIDIA Nemotron 3 Super: The Agentic Workhorse

Its PinchBench score of 85.6%, making it the best open model as the brain of a multi-step coding agent, is more indicative of its real strengths than SWE-Bench alone. The built-in Multi-Token Prediction achieves a 3.45 average acceptance length per verification step (versus DeepSeek-R1's 2.70), giving 2-3x wall-clock speedup in structured code generation without a separate draft model. For long-running autonomous agents that need to maintain context across hours of work, Nemotron is the open-source answer.

GPT-5.3-Codex: The Terminal Specialist

The 77.3% Terminal-Bench 2.0 score is not noise. OpenAI trained this model specifically for the pattern of execute command, read output, decide next action, repeat. It is 25% faster than its predecessor. If your primary use case is CLI automation, SRE tooling, or CI/CD pipeline management, GPT-5.3-Codex is the most purpose-built option available.

Claude Opus 4.6: The Deep Reasoner

The 80.8% SWE-Bench Verified plus 72.7% OSWorld-Verified plus 91.3% GPQA Diamond forms a combination no other model matches across the full stack. The 1M-token context window with 76% accuracy at that length (versus GPT-5.2's 18.5%) makes it the only model suited to actually reading an entire enterprise codebase. Anthropic's Agent Teams feature enables parallel multi-agent coordination for complex, multi-step engineering projects. For large architectural refactors, security audits, or anything requiring sustained reasoning over massive context, Opus is still the clear choice.

Best For: Solo Devs, Enterprise, and Budget Teams

Solo Developers

Start with Nemotron 3 Super via DeepInfra at $0.10/$0.50 per million tokens for the bulk of your work. For the 10-20% of tasks requiring deep multi-file reasoning, escalate to Claude Sonnet 4.6 at $3/$15, which sits at 79.6% on SWE-Bench and is five times cheaper than Opus. You will have a two-tier system that covers 90% of use cases at minimal cost.

Enterprise Teams With Data Privacy Requirements

Self-host Nemotron 3 Super. The NVIDIA Open Model License explicitly permits commercial use, grants ownership of all outputs, and allows fine-tuned derivatives. A single A100 80GB running quantized Nemotron can serve a small engineering team effectively.

Budget Teams (Startups, Early-Stage Companies)

The math is simple. Nemotron 3 Super API costs are 25x lower than Claude Opus 4.6. At 20M tokens per month, that is $12 versus $300. Use the savings to buy human engineering time.

AI Agent Developers Building Production Pipelines

Multi-agent systems running in parallel are exactly the use case where Nemotron's 2.2x throughput advantage compounds. More agents per dollar, longer context retention, and open-source means full customization of the serving layer.

Enterprise Teams Needing Maximum Output Quality

Claude Opus 4.6 remains the benchmark leader for complex, multi-file software engineering. The $5/$25 pricing is premium, but for tasks where one error costs $50,000 in debugging time, the accuracy premium pays for itself.

What's Coming Next

NVIDIA has stated that Nemotron 3 Super is one model in a continuing family. The RL training infrastructure (NeMo Gym) and the full recipe are public, meaning the research community can build on them. I expect SWE-Bench Verified scores for open-weight models to breach 70% before the end of 2026.

GPT-5.4 (already released as of March 2026) consolidates Codex's coding strengths with broader reasoning in a single model. The coding specialist category may consolidate into general-purpose frontier models rather than remaining separate.

My honest prediction: in 18 months, the open-source vs. proprietary coding debate looks completely different. The gap at the frontier will probably stay. But the "good enough for 80% of tasks" threshold will be well within open-source territory for anyone willing to self-host.

Recommended Reads

If you found this useful, these posts from Build Fast with AI go deeper on related topics:

•       GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5 (2026)

•       General Purpose LLM Agent: Architecture and Setup

•       Building Smart AI Agents with ReAct Patterns

•       Atomic Agents: Modular AI for Scalable Applications

•       OpenAI Agents: Automate AI Workflows

Want to learn how to build AI coding agents and production apps using models like these?

Join Build Fast with AI's Gen AI Launchpad, an 8-week structured program to go from 0 to 1 in Generative AI.

Register here: buildfastwithai.com/genai-course

Frequently Asked Questions

What is NVIDIA Nemotron 3 Super?

NVIDIA Nemotron 3 Super is a 120-billion-parameter open-weight AI model released at GTC on March 11, 2026. It uses a hybrid Mamba-Transformer MoE architecture with only 12 billion active parameters per token. It scores 60.47% on SWE-Bench Verified, leading all open-weight models, and runs on hardware with 64GB of RAM or VRAM.

How does Nemotron 3 Super compare to GPT-5.3-Codex on coding benchmarks?

GPT-5.3-Codex scores approximately 80% on SWE-Bench Verified versus Nemotron's 60.47%, roughly a 20-point lead on Python coding tasks. However, GPT-5.3-Codex costs significantly more per token and cannot be self-hosted. On multi-language tasks, the gap narrows: Nemotron scores 45.78% on SWE-Bench Multilingual versus GPT-OSS-120B's 30.80%.

Can I self-host NVIDIA Nemotron 3 Super for free?

Yes. The model weights are available on Hugging Face under the NVIDIA Open Model License, which permits commercial use. Full-precision deployment requires 8x H100-80GB GPUs. Quantized GGUF versions run on a single device with 64GB of RAM or VRAM.

What is Claude Opus 4.6's pricing in 2026?

Claude Opus 4.6 is priced at $5 per million input tokens and $25 per million output tokens for prompts under 200K tokens. For prompts exceeding 200K tokens, input pricing doubles to $10 per million and output increases to $37.50 per million.

Which AI model is best for solo developers in 2026?

For solo developers, the most cost-effective setup is Nemotron 3 Super via DeepInfra ($0.10/$0.50 per million tokens) for high-volume tasks, with Claude Sonnet 4.6 ($3/$15) for complex reasoning. This two-tier system delivers excellent coverage at a fraction of the cost of Opus 4.6 or GPT-5.3-Codex.

Is NVIDIA Nemotron 3 Super good enough for production coding work?

For most production use cases, yes. A 60.47% SWE-Bench Verified score means successful resolution on over 60% of real GitHub issues. Combined with its 85.6% PinchBench score (best open model for agentic tasks) and 1M-token context retention at 91.75% accuracy, it handles long-horizon agent workflows at reasonable cost.

What is SWE-Bench Verified and why does it matter?

SWE-Bench Verified tests AI models on 500 real-world GitHub issues from open-source repositories. Models must generate code patches that pass the original test suites, all within isolated Docker containers. It is considered the most realistic proxy for actual software engineering capability because it uses real bugs and real tests rather than synthetic problems.

References

1.      NVIDIA Nemotron 3 Super Technical Report — NVIDIA Research

2.      Introducing NVIDIA Nemotron 3 Super (Developer Blog) — NVIDIA Developer Blog

3.      Introducing GPT-5.3-Codex — OpenAI

4.      Claude Opus 4.6 Benchmarks and Features — Digital Applied

5.      Nemotron 3 Super Benchmarks and Architecture — LLM Stats

6.      Best AI for Coding 2026: Every Model Ranked — Morph LLM

7.      GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5 — Build Fast with AI

GLM-5-Turbo: Zhipu AI Just Launched the First AI Model Purpose-Built for Agent Workflows

Zhipu AI didn't just fine-tune a general model for agents and call it a day. They built GLM-5-Turbo from the training phase up, specifically for OpenClaw scenarios - and that's a more interesting product decision than most people realize.

Most labs release a flagship model, then add agent capabilities on top as an afterthought. GLM-5-Turbo is the opposite. It starts with the agent workflow and works backward. Today, March 16, 2026, Z.ai officially unveiled it, and I think it's worth paying close attention to what they've actually done here.

What Is GLM-5-Turbo and Why Does It Exist

GLM-5-Turbo is a specialized large language model developed by Zhipu AI (Z.ai), launched on March 16, 2026. Unlike GLM-5, which is a general-purpose frontier model, GLM-5-Turbo was built specifically for one thing: running complex, automated agent workflows inside the OpenClaw ecosystem.

The core idea is that general language models, even excellent ones, are not optimized for agentic use cases out of the box. They handle single-turn conversations well. They handle code generation well. But long-horizon multi-step tasks with tool calls, time-triggered triggers, and continuous execution across agents? That's where generalist models start struggling.

Zhipu AI saw the growing demand for specialized agent infrastructure, and GLM-5-Turbo is their answer.

Key fact: The share of skills in OpenClaw workflows has risen from 26% to 45% in recent months - exactly the data point that made a specialized model worth building.

What Is OpenClaw and Why Does It Need Its Own Model

OpenClaw is a personal AI assistant platform that runs locally on your own devices and connects to external services like messaging apps, APIs, and developer tools. Think of it as a self-hosted AI agent runner designed for developers who want to automate complex workflows without relying on centralized cloud orchestration.

In a typical OpenClaw workflow, you're not just asking a model one question. You're asking it to:

•        Set up an environment

•        Write and execute code

•        Retrieve information from external tools

•        Process the output

•        Trigger follow-up actions at a scheduled time or based on conditions

•        Coordinate with other agents running in parallel

That kind of multi-step, stateful execution is fundamentally different from a chatbot conversation. Most models handle it okay. GLM-5-Turbo was aligned to handle it well.

What makes OpenClaw different from other agent frameworks: It supports time-triggered and continuous tasks natively. A GLM-5-Turbo-powered workflow can kick off a job at 3am, monitor its own execution, handle errors, and retry - without human input. That's a real capability gap most LLMs still aren't great at.

I personally find this approach more interesting than the 'add tools to a chatbot' pattern you see from most providers. The question isn't 'can this model call a function?' It's 'can this model reliably run a job for an hour without losing the thread?' GLM-5-Turbo is trying to answer that second question.

GLM-5-Turbo Technical Specs and Context Window

Here are the core technical details from Z.ai's official documentation:

The 200K context window is important for agent use. Long-horizon tasks accumulate context fast. Conversation history, tool outputs, intermediate reasoning, and task state all pile up inside the context window. At 200K tokens, GLM-5-Turbo can hold extended multi-step workflows in memory without having to prune and summarize - which introduces errors.

The 128K max output is also notable. Most models cap outputs at 4K or 8K tokens. Generating 128,000 tokens in a single response means the model can write entire codebases, produce long-form analysis, or output structured data at scale without requiring multiple API calls.

The model supports reasoning natively. For agent tasks specifically, this matters. A model that shows its reasoning steps is easier to debug and audit than one that jumps straight to a final output.

Benchmarks: ZClawBench and How It Stacks Up

Zhipu AI built a custom benchmark called ZClawBench specifically for end-to-end agent tasks in the OpenClaw ecosystem. It covers: environment setup and configuration, software development and code execution, information retrieval from external sources, data analysis and processing, and content creation workflows.

I appreciate the decision to create a domain-specific benchmark rather than just pointing at SWE-bench. General coding benchmarks don't tell you much about whether a model can run a complex scheduled workflow reliably. ZClawBench is a more honest evaluation for this use case.

Zhipu AI reports that GLM-5-Turbo delivers significant improvements compared to GLM-5 in OpenClaw scenarios and outperforms several leading models in various important task categories. That's manufacturer-reported data, so treat it as directional. Independent evaluations will tell a more complete story.

GLM-5 Base Model Benchmarks (verified):

 One thing worth noting: the GLM-5 base model's hallucination rate dropped from 90% on GLM-4.7 to 34% using a reinforcement learning technique called Slime. For agent workflows specifically, a lower hallucination rate matters enormously. A model that makes up a file path or invents an API response mid-workflow can break an entire pipeline.

GLM-5-Turbo vs GLM-5: What's the Actual Difference

Both share the same foundation. The difference is the optimization target.

GLM-5 is Zhipu's frontier general-purpose model. It's designed to compete with GPT-5 and Claude Opus on breadth: creative writing, reasoning, coding across all domains, multimodal tasks, and long-context processing. It's the model you'd use when you don't know exactly what you're going to throw at it.

GLM-5-Turbo is purpose-trained for the agent pipeline. From the training phase itself, it was aligned with the specific patterns that appear in OpenClaw workflows: instruction decomposition, tool invocation precision, multi-agent coordination, and long-running task stability.

In practical terms:

•        For a one-off coding task? Use GLM-5.

•        For running an autonomous agent that executes a 60-step workflow across 3 hours? Use GLM-5-Turbo.

•        For integrating directly with OpenClaw's scheduler and tool ecosystem? GLM-5-Turbo is the native choice.

The stealth model 'Pony Alpha' that appeared on OpenRouter earlier this year and crushed coding benchmarks has now been confirmed as an early version of the GLM-5 family. GLM-5-Turbo appears to follow in that lineage - high performance in a focused domain, not a generalist that tries to do everything.

Pricing: GLM-5-Turbo vs Claude Opus vs GPT-5

Here's where GLM-5-Turbo makes a genuinely strong commercial argument:

At $1.20/M input tokens, GLM-5-Turbo costs roughly 4x less than Claude Opus on input and over 6x less on output. For agent workflows that generate substantial context and multi-step outputs, that pricing difference adds up quickly. A workflow that costs $50 in Claude Opus tokens might cost under $10 with GLM-5-Turbo.

Agent use cases tend to be high-volume. You're not paying for a few clever responses. You're paying for thousands of tool calls, intermediate reasoning steps, and output tokens across long-running jobs. The pricing model matters a lot more here than it does for a simple chatbot.

That said, cost alone isn't the argument. The argument is: specialized performance at a low price point, from a company that built GLM-5 on Huawei Ascend hardware and still managed to reach frontier-level benchmark scores.

Who Should Actually Use GLM-5-Turbo

Not everyone. This model has a clear target user.

GLM-5-Turbo makes sense for:

•        Developers building on OpenClaw who want a model natively optimized for that environment

•        Teams running high-volume agentic workflows where per-token cost matters at scale

•        Projects requiring long continuous execution - scheduled tasks, monitoring agents, overnight pipelines

•        Developers in markets where data sovereignty matters (Chinese-built model trained on Huawei infrastructure)

GLM-5-Turbo probably isn't the right call for:

•        General-purpose assistant applications where broad capability breadth matters more than agent depth

•        Users who want the widest possible benchmark coverage across diverse tasks

•        Workflows that don't involve multi-step agentic execution

My honest take: if you're not using OpenClaw or running agent workloads specifically, you probably want GLM-5 (the base model) instead. GLM-5-Turbo is a precision tool.

My Take: What This Means for the Agent AI Market

The interesting thing about GLM-5-Turbo isn't the model itself. It's the strategy behind it.

Most labs are still playing the 'one model to rule them all' game. They release a flagship, apply it to everything, and optimize horizontally. Zhipu AI is making a different bet: that as AI workflows get more sophisticated, the market will want models optimized for specific execution environments. General-purpose isn't always better. Fit matters.

This is a reasonable bet. Agent workflows have fundamentally different failure modes than conversational AI. A model that hallucinates in a chatbot is annoying. A model that hallucinates in an agent pipeline corrupts downstream state, triggers wrong tool calls, and can fail silently for minutes before a human notices. The requirements are different. Building a model specifically for that problem space is defensible product logic.

The contrarian point worth making: domain-specific model optimization only holds value as long as OpenClaw remains a significant platform. If the agent tooling ecosystem consolidates around something else, GLM-5-Turbo becomes a narrowly scoped model without a home. Zhipu AI is betting on OpenClaw's growth. That's not a guaranteed bet.

Still, the combination of a $34.5 billion market cap, a successful Hong Kong IPO, frontier-level benchmark performance, and now purpose-built agent infrastructure puts Zhipu AI in a different tier than most Chinese AI labs. I wouldn't dismiss this as just another model release.

FAQ: GLM-5-Turbo Questions Answered

What is GLM-5-Turbo?

GLM-5-Turbo is a large language model developed by Zhipu AI (Z.ai), launched on March 16, 2026. It is a specialized variant of the GLM-5 foundation model, purpose-built for agent workflows in the OpenClaw ecosystem. It supports a 200,000-token context window and outputs up to 128,000 tokens per response.

What is OpenClaw and how does GLM-5-Turbo work with it?

OpenClaw is a personal AI assistant platform that runs on local devices and connects to external services and APIs. It supports automated multi-step workflows, time-triggered tasks, and multi-agent coordination. GLM-5-Turbo was aligned during training specifically for OpenClaw task patterns, making it the native model choice for that environment.

How much does GLM-5-Turbo cost?

Via Z.ai's API, GLM-5-Turbo costs $1.20 per million input tokens and $4.00 per million output tokens. On OpenRouter, it is priced at $0.96 per million input tokens and $3.20 per million output tokens. This is approximately 4 to 6 times cheaper than Claude Opus 4.6, which is priced at $5.00 input and $25.00 output per million tokens.

What is ZClawBench?

ZClawBench is a custom benchmark developed by Zhipu AI specifically for evaluating end-to-end agent task performance in the OpenClaw ecosystem. It covers environment setup, software development, information retrieval, data analysis, and content creation workflows - unlike general benchmarks such as SWE-bench, which focus on code editing tasks alone.

How is GLM-5-Turbo different from GLM-5?

GLM-5 is a 744-billion-parameter general-purpose frontier model competing against GPT-5 and Claude Opus on broad capability. GLM-5-Turbo is a specialized variant trained specifically for OpenClaw agent scenarios, optimized for tool invocation accuracy, multi-step instruction decomposition, and long-running task stability rather than general breadth.

Is GLM-5-Turbo open source?

The base GLM-5 model is available under the MIT license on HuggingFace at zai-org/GLM-5, making it freely available for commercial use and self-hosting. GLM-5-Turbo is currently available via API on Z.ai and OpenRouter. Open-weight availability for GLM-5-Turbo specifically has not been confirmed as of this writing.

What is GLM in AI and who makes it?

GLM stands for General Language Model. It is developed by Zhipu AI, a Chinese AI company founded in 2019 as a spin-off from Tsinghua University. The company rebranded internationally as Z.ai in 2025 and completed a Hong Kong IPO in January 2026, raising approximately USD $558 million. As of March 2026, Zhipu AI is valued at approximately $34.5 billion.

What are GLM-5's benchmark scores compared to Claude?

GLM-5 scores 77.8% on SWE-bench Verified. On BrowseComp, GLM-5 scores 62.0 against Claude Opus 4.5's 37.0. On AIME 2026, GLM-5 scores 92.7%. The hallucination rate for GLM-5 is 34%, lower than Claude Sonnet 4.5 at 42% and GPT-5.2 at 48%, per Zhipu's own evaluations pending independent verification.

Recommended Blogs

These are real posts from buildfastwithai.com relevant to this article:

12+ AI Models in March 2026: The Week That Changed AI

Grok 4.20 Beta Explained: Non-Reasoning vs Reasoning vs Multi-Agent (2026)

GPT-5.4 Review: Features, Benchmarks & Access (2026)

GPT-5.4 vs Gemini 3.1 Pro (2026): Which AI Wins?

Sarvam-105B: India's Open-Source LLM for 22 Indian Languages (2026)

References

Z.ai Official Developer Docs — OpenClaw Overview

GLM-5 on HuggingFace (zai-org/GLM-5) — Official Model Card

VentureBeat — Z.ai's GLM-5 Achieves Record Low Hallucination Rate

OpenRouter — GLM-5-Turbo Pricing & Specs

OpenRouter — GLM-5 Pricing & Specs

Trending Topics EU — Zhipu AI Launches GLM-5-Turbo for OpenClaw

Digital Applied — Zhipu AI GLM-5 Release: 744B MoE Model Analysis

Awesome Agents — China's GLM-5 Rivals GPT-5.2 on Zero Nvidia Silicon

Let's Data Science — How China's GLM-5 Works: 744B Model on Huawei Chips

GLM-5 arXiv Paper — From Vibe Coding to Agentic Engineering

I've been covering AI releases for a while now, and even I had to double-check the calendar. OpenAI dropped GPT-5.4 with a 1-million-token context window. Alibaba's Qwen 3.5 9B outperformed a model 13 times its size on graduate-level reasoning. Lightricks shipped LTX 2.3, generating native 4K video with synchronized audio in a single open-source pass. ByteDance, Peking University, and Canva combined to release Helios, a model that creates full 60-second videos at real-time speed on a single GPU. And NVIDIA quietly dropped Nemotron 3 Super at GTC, an 120B-parameter enterprise coding model that scored 60.47% on SWE-Bench Verified.

This is not a normal week in AI. This is a realignment.

I'm going to break down every model that matters, what the benchmarks actually say, and what developers and builders should do about it. Skip the hype. Here's what's real.

1. What Just Happened: The March 2026 AI Avalanche

The first week of March 2026 produced more significant AI releases than most entire quarters in 2024. Over seven days, organizations across the US, China, and Europe announced at least 12 major models and tools spanning language, video generation, 3D spatial reasoning, GPU kernel automation, and diffusion acceleration.

The release list, catalogued by AI Search (@aisearchio) on March 8, included: GPT-5.4, LTX 2.3, FireRed Edit 1.1, Kiwi Edit, HY WU, Qwen 3.5 Small Series, CUDA Agent, CubeComposer, Helios, Spatial T2I, Spectrum, Utonia, and more. NVIDIA added Nemotron 3 Super at GTC on March 11, making the full count across the first two weeks even higher.

What makes this week different is not just the quantity. The quality gap between open-source and proprietary closed rapidly. Alibaba's 9B open model matched OpenAI's 120B parameter model on GPQA Diamond. Lightricks shipped a 4K video generator that was unthinkable six months ago. ByteDance and Peking University built real-time minute-long video generation without KV-cache, quantization, or sparse attention tricks.

The frontier is no longer the exclusive domain of trillion-dollar companies. That's the real story here.

2. GPT-5.4: OpenAI's Million-Token Frontier Model

GPT-5.4 is OpenAI's most capable and efficient model released to date, launched on March 5, 2026. It comes in three variants: GPT-5.4 Standard, GPT-5.4 Thinking (reasoning-first), and GPT-5.4 Pro (maximum capability). The API supports context windows up to 1.05 million tokens, the largest OpenAI has ever offered commercially.

On factual accuracy, GPT-5.4 reduces individual claim errors by 33% and full-response errors by 18% compared to GPT-5.2. It scored 83% on OpenAI's GDPval benchmark for knowledge work. For coding specifically, it hits 57.7% on SWE-Bench Pro, just above GPT-5.3-Codex's 56.8%, with lower latency.

The new Tool Search feature is genuinely clever. Instead of loading all tool definitions into the prompt (which gets expensive fast when you have 50+ tools), the model dynamically looks up relevant tool definitions as needed. For developers building complex agentic systems, that's a real cost and latency reduction, not a marketing feature.

Pricing: $2.50 per 1M input tokens and $15.00 per 1M output tokens for standard context. There's a 2x surcharge beyond 272K tokens. That surcharge is going to matter for anyone running large-document workflows.

My honest take: GPT-5.4 is incrementally better than GPT-5.2/5.3, not a generational leap. The Tool Search architecture is the most interesting genuine innovation here. The Thinking variant competes directly with Grok 4.20's reasoning mode. If you're already in the OpenAI ecosystem, this is a solid upgrade. If you're choosing a model fresh, the comparison table in section 6 tells a more complete story.

3. Qwen 3.5 Small: The 9B Model That Shocked Everyone

Qwen 3.5 Small is Alibaba's latest open-source family, released March 1, 2026, delivering four dense models at 0.8B, 2B, 4B, and 9B parameters. Every model is natively multimodal, supporting text, images, and video through the same set of weights without a separate vision adapter. All four are licensed under Apache 2.0.

The 9B is the headline. On GPQA Diamond (graduate-level reasoning in biology, physics, and chemistry), it scores 81.7 versus GPT-OSS-120B's 71.5. On HMMT Feb 2025 (a Harvard-MIT math competition benchmark), it hits 83.2 versus GPT-OSS-120B's 76.7. On MMLU-Pro, it reaches 82.5 versus 80.8. On video understanding (Video-MME with subtitles), the 9B scores 84.5, significantly ahead of Gemini 2.5 Flash-Lite at 74.6.

The architecture is the real story. Alibaba moved to a Gated DeltaNet hybrid architecture, combining linear attention (Gated Delta Networks) with sparse Mixture-of-Experts. Linear attention maintains constant memory complexity, which is why a 9B model can support a 262K native context window (extensible to 1M via YaRN) without blowing up on RAM. The 2B model runs on an iPhone in airplane mode, processing text and images on just 4 GB of RAM.

The cost comparison is staggering. Qwen 3.5 via API costs approximately $0.10 per 1M input tokens, versus Claude Opus 4.6 at roughly 13x that price. For startups running high-volume inference, that's the difference between a product being viable and not.

I'll say the contrarian thing here: the benchmark results are real, but benchmarks like GPQA Diamond test academic multiple-choice questions. They do not test what happens when you ask the model to debug a multi-service production outage at 2am with partial logs and five misleading stack traces. That's where the frontier closed models still have an edge. Use the benchmarks as a starting point, not a verdict.

4. LTX 2.3 and Helios: Open-Source Video's Big Moment

Two open-source video models released this week fundamentally change what independent creators and small studios can build without enterprise licensing.

LTX 2.3 (Lightricks)

LTX 2.3 is a 22-billion-parameter Diffusion Transformer model released by Lightricks in the first week of March 2026. It generates synchronized video and audio in a single forward pass, supports resolutions up to 4K at 50 FPS, and runs up to 20 seconds of video. Portrait-mode generation at 1080x1920 is native, not a post-processing crop.

Four checkpoint variants ship: dev, distilled, fast, and pro. The distilled variant runs in just 8 denoising steps. A rebuilt VAE delivers sharper textures and edge detail compared to LTX 2. A new gated attention text connector improves prompt adherence significantly. Audio is cleaner via filtered training data and a new vocoder.

Six months ago, synchronized audio-video generation at 4K in an open-source package was science fiction. Today it costs zero in licensing fees.

Helios (Peking University, ByteDance, Canva)

Helios is a 14-billion-parameter autoregressive diffusion model generating videos up to 1,440 frames (approximately 60 seconds at 24 FPS) at 19.5 FPS on a single NVIDIA H100 GPU. Released under Apache 2.0.

What makes Helios architecturally interesting is what it does NOT use. No KV-cache. No quantization. No sparse attention. No anti-drifting heuristics. The team introduced Deep Compression Flow and Easy Anti-Drifting strategies during training to handle long-horizon video generation natively. The model supports text-to-video, image-to-video, and video-to-video through a unified input representation.

Real-time speed on a single H100 for 60-second videos is the number that matters here. That enables workflows that were previously only possible with multi-GPU clusters and enterprise contracts. Keep your eye on this one.

5. NVIDIA Nemotron 3 Super: The Enterprise Dark Horse

NVIDIA announced Nemotron 3 Super at GTC on March 11, 2026. It is a 120-billion-total-parameter hybrid Mixture-of-Experts model with only 12 billion active parameters per forward pass, designed for complex multi-agent applications including software development, cybersecurity triaging, and agentic workflows.

The benchmark numbers are serious. Nemotron 3 Super scores 60.47% on SWE-Bench Verified (OpenHands scaffold), versus GPT-OSS's 41.90%. On RULER at 1M tokens, it scores 91.75% versus GPT-OSS's 22.30%. It delivers 2.2x higher throughput than GPT-OSS-120B and 7.5x higher throughput than Qwen3.5-122B. That 5x throughput improvement versus the previous Nemotron Super generation is significant for production deployments.

Three genuine architectural innovations ship here. LatentMoE introduces a new expert routing mechanism. Native NVFP4 pretraining means the model was trained in 4-bit precision from the first gradient update, not post-hoc quantized. Multi-Token Prediction is built in for speculative decoding gains.

Already deployed by Perplexity (as one of 20 orchestrated models in their Computer platform), CodeRabbit, Factory, Greptile, Palantir, Cadence, Dassault Systemes, and Siemens.

I think Nemotron 3 Super is being underreported. The SWE-Bench score of 60.47% is higher than anything else in the open-weight category right now. For enterprise teams building coding agents and needing to run models on-prem (regulated industries, defense, healthcare), this is the most important model of the week. It ships with open weights and the full training recipe under the NVIDIA Nemotron Open Model License.

6. Benchmark Breakdown: How These Models Actually Compare

Here is how the major March 2026 models stack up across the benchmarks that matter most. All data is from independent measurement or official lab disclosures.

A few things jump out at me from this table. First, Nemotron 3 Super's 60.47% on SWE-Bench Verified is the highest open-weight score I've seen, period. Second, the Qwen 3.5 9B's GPQA score of 81.7% being competitive with models many times its size confirms the efficiency gains are real, not marketing. Third, GPT-5.4's 33% reduction in factual errors is the reliability improvement that matters most for production enterprise use cases.

Grok 4.20's ranking second on ForecastBench (ahead of GPT-5, Gemini 3 Pro, and Claude Opus 4.6) is the result I'd want to verify independently before building anything on top of it. Real-time reasoning on probabilistic forecasting is a genuinely hard task, and if Grok 4.20 delivers there consistently, that's a meaningful differentiator.

7. What This Means for Developers and Builders in 2026

The practical implications of this week's releases are significant. Here's what I think actually matters for people building products right now.

The on-device opportunity just got real. Qwen 3.5's 2B model runs on an iPhone with 4 GB of RAM, offline, processing text and images natively. The 4B model handles lightweight agentic tasks on consumer GPUs. The 9B matches cloud models from last year. If you're building an app and avoided local inference because the models were too weak, that excuse is gone.

Open-source video is production-ready. LTX 2.3 at 4K with synchronized audio is not a toy. Helios generating 60-second videos in real time on one H100 is not a toy. If you're paying enterprise licensing for AI video tools, the math just changed.

The coding agent race is NVIDIA's to lose. Nemotron 3 Super at 60.47% on SWE-Bench Verified, open-weight, running at 2.2x the throughput of GPT-OSS, with full training recipe transparency, is the most compelling foundation for enterprise coding agents I've seen. Teams at regulated companies that can't use cloud APIs should be benchmarking this now.

Tool calling architecture matters more than raw capability. GPT-5.4's Tool Search, which dynamically loads tool definitions rather than stuffing them all into the prompt, is the kind of infrastructure improvement that compounds. If you're building a system with many tools, the cost and latency savings are real.

The wider trend I see: the gap between proprietary frontier models and open-weight models is narrowing from years to months. The winners in 2026 are not the companies with the biggest models. They're the companies that build the best products on top of these efficient, open, edge-deployable foundations.

Frequently Asked Questions

What is the best AI model released in March 2026?

For enterprise coding tasks, NVIDIA Nemotron 3 Super scores 60.47% on SWE-Bench Verified, the highest open-weight score currently available. For general-purpose frontier performance, GPT-5.4 scores 83% on GDPval and reduces factual errors by 33% versus GPT-5.2. For on-device or budget-constrained deployment, Qwen 3.5 9B at $0.10 per 1M tokens matches models 13x its size on GPQA Diamond.

What is GPT-5.4 and when did it release?

GPT-5.4 is OpenAI's latest frontier language model, released on March 5, 2026. It offers a 1.05 million-token context window, three variants (Standard, Thinking, and Pro), 33% fewer individual factual errors than GPT-5.2, and a new Tool Search architecture for dynamic tool calling. API pricing starts at $2.50 per 1 million input tokens.

How does Qwen 3.5 9B beat a 120B model?

Qwen 3.5 9B uses a Gated DeltaNet hybrid architecture combining linear attention with sparse Mixture-of-Experts. Linear attention maintains constant memory complexity rather than quadratic scaling, enabling the model to allocate more of its parameters toward task-specific reasoning rather than memory management. On GPQA Diamond (81.7 vs 71.5) and HMMU Feb 2025 (83.2 vs 76.7), the architecture advantage is visible in the benchmark scores.

What is LTX 2.3 and is it free to use?

LTX 2.3 is a 22-billion-parameter open-source video generation model from Lightricks, released in the first week of March 2026. It generates 4K video at 50 FPS with synchronized audio in a single pass, supports portrait mode at 1080x1920, and runs in 8 denoising steps on the distilled variant. The model ships with open weights and is free to use for commercial purposes.

What is NVIDIA Nemotron 3 Super?

Nemotron 3 Super is a 120B-total-parameter, 12B-active-parameter hybrid MoE model from NVIDIA, announced at GTC on March 11, 2026. It scores 60.47% on SWE-Bench Verified, delivers 2.2x higher throughput than GPT-OSS-120B, and supports a 1M-token context window. It ships with open weights, datasets, and the full training recipe under the NVIDIA Nemotron Open Model License.

What is Helios and who made it?

Helios is a 14-billion-parameter autoregressive diffusion model built jointly by Peking University, ByteDance, and Canva. Released under Apache 2.0 in March 2026, it generates videos up to 1,440 frames (approximately 60 seconds at 24 FPS) at 19.5 frames per second on a single NVIDIA H100 GPU, supporting text-to-video, image-to-video, and video-to-video tasks through a unified architecture.

How does March 2026 AI compare to earlier generations?

March 2026 marks the point where open-source models became genuinely competitive with proprietary frontier models on specific critical benchmarks. A 9B open-weight model now matches a 120B closed model on graduate reasoning. A free video model generates 4K output. The efficiency frontier collapsed in one week: models are achieving more capability with less compute than at any previous point in the field's history.

Which AI model is best for coding in 2026?

NVIDIA Nemotron 3 Super leads on SWE-Bench Verified at 60.47%, making it the top open-weight model for real coding tasks. GPT-5.4 scores 57.7% on SWE-Bench Pro with integrated Codex capabilities and lower latency than previous coding-specialized variants. For teams needing local deployment with no API costs, Nemotron 3 Super's open weights and full training transparency make it the strongest enterprise option.

Recommended Blogs

These posts are live on buildfastwithai.com and directly related to what we covered above:

•        GPT-5.4 vs Gemini 3.1 Pro (2026): Which AI Wins?

•        GPT-5.4 Review: Features, Benchmarks & Access (2026) 

•        Gemini 3.1 Flash Lite vs 2.5 Flash: Speed, Cost & Benchmarks (2026) 

•        6 Biggest AI Releases This Week: Feb 2026 Roundup 

•        Sarvam-105B: India's Open-Source LLM for 22 Indian Languages (2026) 

References

•        1. OpenAI GPT-5.4 Release  |  sci-tech-today.com/news/march-2026-ai-models-avalanche

•        2. Alibaba Qwen 3.5 Small Series 

•        3. Qwen 3.5 9B Benchmarks 

•        4. NVIDIA Nemotron 3 Super SWE-Bench 

•        5. Qwen3.5 Complete Guide  | 

•        6. xda-developers.com/qwen-3-5-9b-tops-ai-benchmarks-not-how-pick-model  | 

•        7. AI Search (@aisearchio) March 8 Recap  | 

I checked LinkedIn at 7 AM this week and counted 47 new AI job postings in India - before my coffee was ready.

That's the market you're living in right now. India's AI job demand grew over 40% year-on-year according to NASSCOM's 2024 report. Over 450,000 AI job listings exist on major platforms right now. And freshers are landing 8-12 LPA packages without a single year of corporate experience.

But here's what nobody tells you: AI jobs in India salary varies wildly. A data annotation contractor earns 3 LPA. A senior LLM engineer at a product company earns 70 LPA. Both get called "AI jobs." That gap is what this guide untangles.

Below is every number that matters: role-by-role salary, city-by-city comparison, what generative AI pays vs. traditional ML, and exactly how you get from zero to your first AI paycheck in India.

Why AI Jobs in India Pay So Well in 2026

The honest answer: supply-demand mismatch. India produces 1.5 million engineering graduates a year. Fewer than 3% have real AI/ML skills. Companies desperate to ship AI products are competing for that small pool - and salary is the primary weapon.

Three forces are running the salaries up right now:

•        The GenAI wave pushed every major company (banks, hospitals, logistics firms, e-commerce) into building AI teams overnight. Most had no existing talent pipeline.

•        Global firms opened GCCs (Global Capability Centres) in Bengaluru and Hyderabad specifically to hire Indian AI talent at below-US cost but above-Indian-average salaries.

•        Remote work normalized premium pay for Indian engineers serving US and EU product teams - no relocation required.

By 2026, India is projected to host over 1 million active AI and ML job roles, with 15-20% year-on-year salary growth expected to continue. If you have depth in Python, PyTorch, or LLMs right now, you are a scarce resource. Act like one.

My read: The window where freshers can get into AI without being vastly underpaid is still open. But it is closing. The longer you wait, the more competition floods in from people who started learning 6 months earlier than you.

AI Jobs in India Salary: Role-by-Role Breakdown

Not all AI roles are built equal. The title "AI Engineer" can mean anything from running a Jupyter notebook to deploying multi-billion parameter models at scale. Here's what each specific role actually pays:

The standout: Generative AI Engineers and LLM Engineers now command the same salary bands. Both roles require mastery of transformer architectures, RAG systems, and production deployment of large language models. At senior levels, both hit 70 LPA in Indian product companies - and north of $280,000 for global remote roles.

The one role I'd push back on for freshers: "Prompt Engineer" as a standalone title. The salary ceiling without adjacent coding skills is painfully low. Build prompting combined with Python and RAG, and that title transforms into Applied AI Engineer - a completely different pay grade.

AI Salary in India Per Month: Fresher vs Senior

Most salary data in India gets published as annual figures. But since a lot of people searching this are trying to understand monthly take-home realities, here is the full breakdown:

The fresher-to-mid-level salary jump is the steepest in any tech career I've tracked. A 3-year AI engineer who moved from a service company to a product startup during this period routinely sees 40-70% salary hikes in a single switch. That's not unusual - I've seen profiles go from 9 LPA to 22 LPA in one job change with 3 years experience.

One thing the table doesn't capture: stock options. At startups and some BigTech GCCs, ESOPs can add 20-50% on top of base salary. If you join early-stage at the right company, those options matter more than your base.

City-Wise AI Jobs Salary in India

Geography still moves the needle on AI salaries in India - significantly. Bengaluru leads by a wide margin, but tier-2 cities are catching up as companies decentralize talent hubs.

Bengaluru still leads in both volume and top-end salary. The city hosts Google, Amazon, Flipkart, Swiggy, and hundreds of AI startups that routinely pay 15-40 LPA for mid-senior roles. The trade-off: cost of living.

Hyderabad is the fastest-growing hub right now. The Telangana government's AI Mission, combined with Microsoft and Amazon presence, is driving aggressive hiring at GCCs. Salaries are 10-15% below Bengaluru - but rent is 30-40% cheaper. Do the math.

Remote work changes everything here. Senior AI engineers working for US-based companies remotely from Tier-2 cities like Coimbatore or Indore earn 60-80 LPA equivalent - while paying Tier-2 cost of living. That arbitrage is real and I think it's underused.

Generative AI Jobs Salary in India: The New Gold Rush

Generative AI is where the real salary acceleration is happening. GenAI engineers in India earn 20-70 LPA - compared to 10-40 LPA for traditional ML engineers. That premium exists because the field is young, skilled talent is scarcer, and business impact is immediate.

City-specific GenAI salary data for 2026:

•        Bengaluru: 15 LPA to 45 LPA for GenAI engineers (mid to senior)

•        Hyderabad: 13 LPA to 35 LPA, driven by enterprise AI and GCC demand

•        Mumbai: 12 LPA to 38 LPA, strong in FinTech and retail AI applications

•        Delhi-NCR: 10 LPA to 32 LPA, growing startup and enterprise mix

The fastest-growing GenAI roles in India right now:

•        GenAI Developer: builds LLM-powered applications using GPT, Llama, LangChain, HuggingFace

•        LLM Engineer: fine-tunes foundation models, builds RAG pipelines, handles production deployment

•        MLOps Engineer: manages AI model infrastructure - salaries 12-35 LPA, growing 20% YoY

•        AI Product Manager: bridges AI capability with business strategy - 18-55 LPA at senior levels

Gartner predicted that four out of five engineers will need to upskill by 2027 to stay relevant in GenAI-shaped roles. India needs at least 1 million skilled AI professionals by 2026 according to Economic Times reporting. The gap between demand and supply is why these salaries keep climbing.

My honest prediction: GenAI salaries plateau at the top end by 2027 as more engineers enter the field. The opportunity to ride the scarcity premium is a 2026 window. If you are sitting on the fence about learning LLMs - this is your signal.

Prompt Engineer Jobs Salary in India

Prompt engineering salaries in India range from 6 LPA at entry level to 40 LPA for senior and lead roles at product companies and MNCs. The market is maturing fast.

City-wise prompt engineering salary in India (2026):

•        Bengaluru: 15-20 LPA+ per annum. Top employers include Google, Flipkart, OpenAI India, Microsoft Research, Accenture AI

•        Hyderabad: 13-18 LPA per annum. Employers: Microsoft, Amazon, Tech Mahindra, TCS, Deloitte Digital

•        Mumbai: 12-15 LPA for most roles, with FinTech companies paying 15-25 LPA for senior positions

One thing to understand about prompt engineering salaries: the title itself is in flux. Most standalone "Prompt Engineer" roles at large companies will likely evolve into "AI Systems Engineer" or "Applied AI Engineer" by 2027-2028. The prompting skill stays valuable - it just gets bundled with broader requirements.

The real play is building prompting knowledge combined with Python, RAG system design, and LLM evaluation frameworks. That combination moves your salary ceiling from 12 LPA to 25-40 LPA even at 2 years experience.

Agentic AI Jobs Salary in India

Agentic AI is the next wave after GenAI, and salary premiums are already forming. Agentic systems involve AI agents that plan, reason, use tools, and execute multi-step tasks autonomously. Companies building these systems are willing to pay significantly above-market to find engineers who understand them.

Agentic AI roles are primarily hybrid - they require knowledge of LLMs, multi-agent orchestration frameworks (LangGraph, CrewAI, AutoGen), vector databases, and production deployment. Because the field is so new, most companies are promoting GenAI engineers into agentic roles rather than hiring fresh.

Estimated salary ranges for agentic AI roles in India in 2026:

•        Junior Agentic AI Developer: 12-20 LPA (requires strong GenAI foundation)

•        Mid-Level Agentic Systems Engineer: 25-45 LPA

•        Senior Agentic AI Architect: 50-80 LPA at product companies

These are still early-stage estimates because the job category itself is less than 2 years old. What I'd say with confidence: if you understand LangGraph, multi-agent orchestration, and can demonstrate a deployed agentic system, you're in the top 1% of what companies can find right now. Price yourself accordingly.

How to Get Your First AI Job in India Without a Fancy Degree

Freshers typically earn 5-12 LPA to start in AI/ML roles in India in 2026. Strong candidates with real projects start at 15 LPA. Here is the fastest path to your first AI paycheck:

Build These Skills First

•        Python (non-negotiable - every AI job in India lists it)

•        SQL (every AI role touches data; SQL is the baseline)

•        Machine Learning fundamentals: Scikit-Learn, basic neural networks

•        At least one deep learning framework: PyTorch is now preferred over TensorFlow by a wide margin

•        Basic GenAI: Learn to work with OpenAI API, HuggingFace transformers, LangChain

Build a Portfolio That Companies Can Actually Verify

Companies like TCS, Infosys, and Wipro offer extensive training programs for freshers and compensate for relatively lower starting salaries. But product companies and startups want proof of capability:

•        Maintain an active GitHub with at least 3 complete AI projects

•        Build one end-to-end LLM application (not a tutorial - your own idea)

•        Contribute to open-source projects on HuggingFace or LangChain

•        Write about your projects on LinkedIn - visibility compounds over time

Certifications That Actually Move the Needle

•        Google Professional Machine Learning Engineer

•        DeepLearning.AI specializations (Andrew Ng's courses still carry weight)

•        AWS Certified Machine Learning Specialty

•        Microsoft Azure AI Engineer

Platforms like LinkedIn show 70% more AI jobs for freshers year-over-year. The demand is there. What most freshers lack is a visible portfolio that demonstrates real-world problem-solving - not course completion badges.

One thing I'd push back on: non-CS students can absolutely enter AI roles. Hands-on experience with generative AI models tops recruiter lists in 2026, according to OdinSchool's 2025 report. Domain expertise in healthcare, finance, or logistics combined with AI skills is actually more valuable than pure CS backgrounds for many specialized roles.

Which 3 Jobs Will Survive AI (And 5 That Won't)

This is the question people keep Googling - and understandably so. AI is eliminating tasks faster than it's eliminating jobs. The real answer is more nuanced than the headlines suggest.

Jobs Most Likely to Survive AI

5 Jobs Facing Serious AI Displacement by 2030

•        Data Entry Operators: AI handles structured data extraction at near-perfect accuracy, faster and cheaper

•        Basic Copywriters: Content generation AI handles templated writing at scale - this tier is already largely displaced

•        Junior Data Analysts: Automated insight generation tools are replacing entry-level analysis work

•        Call Centre Agents (routine): Voice AI and LLM-powered chatbots handle most tier-1 support queries

•        Basic Graphic Designers (template work): Text-to-image AI handles volume templated design - premium creative work is safe

The 30% rule that circulates online: McKinsey Global Institute estimated roughly 30% of current work tasks could be automated by 2030. That's tasks, not jobs. Most jobs will change; far fewer will fully disappear.

Bill Gates' view (paraphrased): the three jobs most likely to persist are energy, biology, and AI itself -because they're either too physically complex, too creatively human, or are literally the tools doing the automating.

My honest read: the jobs that survive aren't a fixed list. It's a mindset. People who can adapt, use AI tools, and bring human judgment to AI outputs will keep working. People waiting for AI to stop advancing before they engage with it will not.

Can an AI Engineer Earn 1 Crore in India?

Yes. And it's less rare than it was two years ago. Senior AI leaders and principal engineers at BigTech, FinTech, and AI-first startups earn 1 Cr+ in India - especially when you factor in bonuses and ESOPs.

The specific pathways to 1 Crore in India as an AI professional:

•        Senior AI Engineer at Google, Meta, or Microsoft India: base salary of 60-80 LPA plus RSUs and performance bonuses can reach 1 Cr+ total compensation

•        AI/ML Lead at a funded Indian unicorn: Swiggy, Meesho, and other late-stage startups offer aggressive packages at leadership level

•        Remote senior AI engineer working for US firms: 60-80 LPA equivalent for Indian engineers in senior roles at US product companies, remotely

•        AI Startup Founder or Co-Founder: equity-driven path - not salary, but potentially far more

•        Independent AI Consultant: principal-level engineers consulting for global firms earn 8-15 LPA per client on retainer

The top 1% salary in India's tech sector is approximately 1-2 Crore annually. AI engineering is one of the few non-executive paths that reaches this level on technical merits alone - no management track required.

The realistic timeline: Freshers who start at 8-12 LPA in 2026, specialize in LLMs or GenAI systems, switch companies twice in 5 years, and contribute to a recognized open-source project can realistically hit 40-60 LPA in 5 years. The 1 Crore mark typically requires 10+ years, a leadership role, or a BigTech offer.

FAQ: AI Jobs in India Salary

Is AI a high paying job in India?

AI is among the highest-paying technical careers in India in 2026. The average AI engineer salary in India ranges from 10 LPA to 40 LPA, with specialists in Generative AI, LLMs, and MLOps earning 40-70 LPA at senior levels. Freshers start at 5-12 LPA, which is significantly higher than most other engineering roles.

What is the AI jobs salary per month in India for freshers?

Freshers in AI jobs in India earn 40,000 to 1,00,000 per month (5-12 LPA annually) in 2026. Most freshers in the 50,000 to 70,000 per month range land at mid-tier IT companies like TCS, Infosys, and Wipro. Product companies and startups offer 80,000 to 1,25,000 per month for freshers with strong portfolios and GenAI skills.

What is the generative AI jobs salary in India per month?

Generative AI engineers in India earn 1.7 to 5.8 lakh per month (20-70 LPA annually) at mid to senior levels. Entry-level GenAI roles start at 8-15 LPA for freshers with relevant project experience. Bengaluru-based GenAI engineers at product companies average 15-45 LPA for mid-senior roles.

What is AI prompt engineer jobs salary in India?

Prompt engineering salaries in India range from 6 LPA at entry level to 40-60 LPA for senior and lead roles at product companies. In Bengaluru, senior prompt engineers earn 15-20 LPA+. Pure prompt engineering roles without adjacent coding skills cap lower; combining prompting with Python and RAG skills pushes the ceiling to 25-40 LPA at 2-3 years experience.

What is the AI ML jobs salary in India for freshers?

AI and ML jobs for freshers in India pay 5-9 LPA on average in 2026, depending on technical skills, project experience, and location. Strong freshers with Python, PyTorch, and a real project portfolio can negotiate 10-15 LPA at product companies. NASSCOM data shows fresher hiring in AI/ML grew 22% year-on-year, signaling sustained demand.

Are AI jobs in demand in India?

AI jobs in India are in very high demand in 2026. Over 450,000 AI job listings exist on major platforms. India's AI job market grew over 40% year-on-year according to NASSCOM. By 2026, India is expected to host over 1 million active AI and ML job roles, with 15-20% projected year-on-year salary growth continuing through 2030.

Which 3 jobs will survive AI?

Based on current trajectory, the three broad categories most likely to survive AI displacement are: AI engineers themselves (who build the tools), healthcare professionals who combine AI tools with human accountability and empathy, and AI ethics and policy experts who provide human governance of AI systems. The unifying factor across all three is that human judgment, creativity, or accountability is irreplaceable in the core function.

Can an AI engineer earn 1 crore per month in India?

No AI engineer currently earns 1 crore per month as a regular salary in India. However, senior AI engineers at Google, Meta, and Microsoft India can earn 1 crore per year (approximately 8.3 lakh per month) in total compensation including base salary, RSUs, and bonuses. Principal AI scientists and AI startup co-founders with equity can exceed this in favorable market conditions.

Can I get an AI job in India with no experience?

Yes. Entry-level AI roles in India - including ML intern, AI research assistant, and junior data analyst positions - are accessible with no corporate experience if you have relevant skills and a portfolio. Freshers should focus on building 3 real AI projects on GitHub, completing recognized certifications from Google or DeepLearning.AI, and targeting smaller product companies and AI startups where portfolio matters more than work history.

Which AI is in high demand in India?

Generative AI skills are in highest demand in India in 2026. Specifically, LLM engineering, RAG pipeline development, MLOps, and agentic AI system design are the most sought-after specializations. Python with PyTorch outnumbers TensorFlow job listings significantly. Cloud AI skills (AWS SageMaker, Google Vertex AI, Azure ML) boost salary by 30-40% for any AI role.

Recommended Blogs

If you found this useful, these posts from BuildFastWithAI cover related ground:

•        Prompt Engineering Salary 2026: US, India, Freshers Pay Guide

•        How to Build AI Agents for Under 250 USD a Month

•        GLM-5 vs Claude Opus: Open Source Benchmarks Compared

References

•        NASSCOM AI/ML Talent Report 2024 -- nasscom.in

•        Scaler: AI Engineer Salary in India 2026

•        upGrad: Artificial Intelligence Salary India

•        Testleaf: AI & ML Engineer Salary in India 2026

•        Futurense: AI Engineer Salary India

•        IGM Guru: Generative AI Engineer Salary Trends 2026

•        BuildFastWithAI: Prompt Engineering Salary 2026

•   

Start Building Real AI Skills (Free Tools & Prompts)

If you're serious about getting an AI job in India or increasing your AI salary, the most important thing is building real AI projects and practical skills.

To help you move faster, we created a free prompt library and AI tools collection used by builders, developers, and AI learners.

You can explore it here:

👉 AI Prompt Library & Tools

Inside you'll find ready-to-use prompts for:

• AI development

• automation workflows

• building AI agents

• productivity and research

• coding with AI tools

These prompts can help you build projects faster and learn how AI systems actually work.

🎓 Learn Generative AI the Practical Way

If you want to go beyond theory and learn how to actually build with Generative AI, you can explore our complete GenAI course.

The course focuses on real skills used in AI jobs today, including:

• Generative AI fundamentals

• LLM applications

• building AI tools and agents

• prompt engineering

• real-world AI projects

Explore the course here:

👉 Generative AI Course

This is designed especially for:

• developers

• students

• AI beginners

• professionals transitioning into AI careers

💡 Final Advice

The AI job market is moving extremely fast. The engineers getting 15–40 LPA AI jobs in India today are the ones who:

• build real projects

• understand AI tools deeply

• continuously learn new AI technologies

Start small, build consistently, and stay curious.

The AI opportunity window is open right now - but the people who act early benefit the most.

Four AI agents - Grok, Harper, Benjamin, and Lucas - now argue with each other inside every query you send. They cross-check, debate, fact-check, and refuse to hand you a final answer until they've reached internal consensus. One of them, Lucas, exists purely to disagree with the others.

That's Grok 4.20 Beta. And I've been testing all three variants - Non-Reasoning, Reasoning Preview, and Multi-Agent Beta - since launch. Here's what actually matters and what the hype is missing.

1. What Is Grok 4.20 Beta? (And Why the Name Matters)

Grok 4.20 Beta is xAI's latest AI model, publicly launched on February 17, 2026, across grok.com, iOS, and Android simultaneously - no staged rollouts, no waitlists. It's the fastest iteration xAI has shipped, arriving just three months after Grok 4.1's November 2025 release.

The version number, 4.20, is classic Elon Musk. It's a deliberate internet culture wink. But the engineering underneath it is dead serious.

The headline changes from Grok 4.1 are two-fold:

•        Rapid Learning Architecture - Unlike every previous Grok version, 4.20 updates its own capabilities weekly based on real-world usage. You don't download an update. The model you use today will be meaningfully different from the one you used a month ago. Automatically.

•        Native Multi-Agent Collaboration - This is the architecture shift. Instead of a single model chain-of-thought, four specialized AI agents work in parallel, debate each other's outputs, and only synthesize a final answer after internal peer review.

Three API variants shipped with it: Non-Reasoning, Reasoning Preview, and Multi-Agent Beta. The distinctions between them are not cosmetic - they serve entirely different use cases and come with meaningfully different performance profiles.

My honest take: the Rapid Learning Architecture is the underrated feature. A model that compounds improvements weekly in production is a fundamentally different product than a static one. Everyone's talking about the agents. I'd watch the learning loop.

2. The Three Grok 4.20 Variants Explained

Grok 4.20 isn't a single model. It's a family of three variants, each designed for a different kind of task. Here's the clean breakdown:

Grok 4.20 Beta Non-Reasoning

Released as a stable beta on March 9, 2026 (build 0309), this is the speed-first variant. It gives you direct answers without chain-of-thought reasoning tokens - no internal "thinking" step before the response.

What that means in practice: fast outputs, lower cost per call, and still capable of handling most tasks you'd throw at a frontier model. It scores 30 on the Artificial Analysis Intelligence Index - above average for non-reasoning models in its price tier (the median is 21). It generates output at 232.5 tokens per second, compared to the category median of 54.8 t/s. Time-to-first-token is 0.54 seconds (category median: 1.49 seconds).

One honest warning: this variant is verbose. When evaluated on the Intelligence Index, it generated 30 million output tokens against a category median of 4 million. If you're paying per output token, that verbosity adds up fast.

Grok 4.20 Beta Reasoning Preview

This is the deep-thinker variant. With reasoning enabled, Grok 4.20 scores 48 on the Artificial Analysis Intelligence Index - a meaningful 6-point jump over Grok 4. It's not at the top of the leaderboard (Gemini 3.1 Pro Preview and GPT-5.4 both score 57), but the gap is narrowing.

The reasoning mode processes extended chain-of-thought before responding. That means slower outputs but notably stronger performance on complex logic, multi-step math, scientific reasoning, and anything where getting the first answer wrong is expensive. One important xAI note: there is no non-reasoning fallback when Reasoning mode is active - it's always on for this variant.

Grok 4.20 Multi-Agent Beta

This is the architectural flagship. Four specialized agents - Grok (Captain/coordinator), Harper (research and fact-checking via real-time X data), Benjamin (logic, math, and coding), and Lucas (creative synthesis and built-in contrarianism) - run in parallel on every query.

The workflow has four phases: task decomposition by Grok, parallel analysis by all four agents, internal debate and peer review, and finally aggregated output. The internal debate phase is where the hallucination reduction happens. Cross-agent verification drops the hallucination rate from approximately 12% down to roughly 4.2% - a 65% improvement over single-model baselines.

For tougher tasks, a "Heavy" mode scales this to 16 agents. Elon Musk confirmed on March 12, 2026 that Grok 4.20 Heavy (Beta 2) is "extremely fast for deep analysis" - the first direct performance characterization from xAI's CEO since launch.

The comparison that helps most: Non-Reasoning is your fast, cost-efficient everyday driver. Reasoning Preview is for problems where depth matters more than speed. Multi-Agent Beta is for complex multi-perspective work - research, strategy, scientific writing - where a single model's blind spots are a liability.

3. How the 4-Agent Multi-Agent System Actually Works

The four-agent architecture isn't a marketing frame on top of a single model. The agents are distinct specialized sub-models running on a shared Mixture-of-Experts (MoE) backbone. Here's the actual workflow:

Phase 1: Task Decomposition

When your query arrives, Grok the Captain analyzes its structure and breaks it into parallel sub-tasks. Research questions go to Harper. Logic and calculation goes to Benjamin. Creative framing and contrarian pressure goes to Lucas.

Phase 2: Parallel Analysis

All four agents work simultaneously. Harper pulls real-time data from X (formerly Twitter) and the web. Benjamin constructs and verifies logical chains. Lucas actively looks for flaws in the other agents' emerging conclusions. Grok maintains overall context.

Phase 3: Internal Debate and Peer Review

This is the key innovation. If Benjamin's mathematical conclusion contradicts a fact Harper found, they surface the conflict explicitly. The agents iterate, challenge, and correct each other before anything reaches you. Lucas's contrarian role means there's always at least one agent whose job is to poke holes in the consensus - which is how the hallucination rate gets forced down.

Phase 4: Aggregated Output

Grok synthesizes a final response only after internal consensus is reached. The output is typically more structured and better-reasoned than what a single model would produce on the same query.

A real example of what this enables: a user on X tasked 16 Grok 4.20 Heavy agents with building a complete, library-free HTML page featuring a full-screen WebGL GLSL shader. The result worked on the first try. Single-model systems typically require multiple iterations to get to the same place.

The numbers that back this up: the AA Omniscience test measures factual accuracy under uncertainty - specifically, how often a model admits it doesn't know versus hallucinating an answer. Grok 4.20 hit a 78% non-hallucination rate on this benchmark. That's a record, according to Artificial Analysis. No other model tested has hit it. It's the clearest quantitative signal that the multi-agent peer-review approach is working.

The Four Agents at a Glance

4. Grok 4.20 Beta Benchmarks vs GPT-5, Claude Opus 4.6, and Gemini 3.1 Pro

The benchmark picture for Grok 4.20 is nuanced, and I'd be misleading you if I pretended it was simpler than it is. Here's the honest summary:

On overall intelligence scores, Grok 4.20 is competitive but not leading. With reasoning enabled, it scores 48 on the Artificial Analysis Intelligence Index. Gemini 3.1 Pro Preview and GPT-5.4 both score 57. That's a real gap. On raw benchmark performance across most test suites, Grok 4.20 is third or fourth in the current frontier tier.

On factual reliability, Grok 4.20 is currently best in class. The 78% AA Omniscience non-hallucination rate is a record. This is the benchmark that matters most for real-world production use - a model that's slightly less "intelligent" but significantly less likely to confidently fabricate an answer is often more useful.

For context, here's how the major current models compare on the benchmarks that matter for most developers and researchers:

Note: Intelligence Index scores from Artificial Analysis (March 2026). Omniscience estimates for competitors based on published partial data. Prices reflect median API provider rates.

On coding specifically - SWE-bench Verified is the benchmark most developers care about - Grok 4 (the base model underlying 4.20) scored 75%, GPT-5 hit 74.9%, Claude Opus 4.6 reached 72.5% on SWE-bench tasks. Gemini 3.1 Pro trails at 67.2%. For coding workflows, the gap between the top three (Grok, GPT-5, Claude) is small enough that API pricing and integration convenience often make a bigger practical difference than raw score differences.

My read: Grok 4.20 is not the most intelligent model on the market right now. But it might be the most reliable one. In a world where AI gets embedded into production systems - where a wrong answer doesn't just look bad but causes real downstream damage - hallucination rate is the benchmark that actually matters. Grok 4.20 has a real, measurable advantage there.

5. Grok 4.20 API Pricing Breakdown (2026)

Grok 4.20 is the cheapest Western frontier model by input token cost right now. Here's the full picture:

API Pricing (Per 1 Million Tokens)

Consumer Subscription Plans

At $2.00 per million input tokens, Grok 4.20 is priced identically to Gemini 3.1 Pro on inputs but significantly cheaper on outputs ($6.00 vs $12.00 per million). Claude Opus 4.6 at $5.00/$25.00 is the premium option - you're paying for coding depth and reliability, not raw speed.

One important caveat: API access for Grok 4.20 Multi-Agent Beta is still listed as "coming soon" as of March 2026. The agent architecture is currently consumer-facing only. Developers building on the API are working with the Non-Reasoning and Reasoning variants for now.

Bottom line on pricing: if you're cost-sensitive and running high volumes, Grok 4.20 Non-Reasoning at $2/$6 is the best bang-per-token among frontier Western models right now. If you need the highest reliability for production, the 78% Omniscience score makes the $2 input price look very reasonable.

6. Grok 4.20 vs Claude Opus 4.6 vs GPT-5.4 vs Gemini 3.1 Pro - Full Comparison

No single model dominates across all tasks in 2026. The current frontier is genuinely competitive, and the right choice depends entirely on what you're actually building. Here's where each model actually wins:

The developer community's own verdict is interesting. Reddit threads from early 2026 consistently show Claude (particularly Opus 4.6 and Claude Code) as the leading choice for software engineering, specifically for production-grade Next.js applications, full-stack workflows, and anything requiring well-organized, maintainable code. Grok 4.20 is getting cited as the daily driver for research and analysis tasks, where its lower hallucination rate and real-time X data access create a real edge. GPT-5.4 holds its position as the most versatile generalist.

The honest take nobody says out loud: Claude is 2–3x more expensive than Grok per token. For coding workflows where the quality difference is real but marginal, the economics will push more developers toward Grok over time - especially once Multi-Agent API access opens up.

7. Who Should Use Which Grok 4.20 Variant?

The variant you choose should match the nature of the task, not just your preference. Here's how I'd route different use cases:

Use Grok 4.20 Non-Reasoning When:

•        You need fast responses at scale (232+ tokens/second output)

•        The task is straightforward: summarization, classification, content generation, basic Q&A

•        Cost per call matters - $2/$6 per million tokens is one of the best rates at frontier quality

•        You're building a high-volume API integration and latency is a constraint (0.54s TTFT)

•        You want to prototype quickly before committing to a heavier reasoning pipeline

Use Grok 4.20 Reasoning Preview When:

•        The problem involves multi-step logic, complex math, or scientific reasoning

•        Getting the first answer right matters more than getting it fast

•        You're working on tasks that require extended chain-of-thought - competitive math, advanced coding problems, strategic planning

•        You need the hallucination resistance of 4.20 with deeper analytical depth

Use Grok 4.20 Multi-Agent Beta When:

•        The task has multiple dimensions that benefit from parallel expert analysis - research reports, comprehensive market analysis, technical white papers

•        You need built-in fact-checking and peer review as part of the output process

•        Real-time X / web data matters for accuracy (Harper's specialization)

•        You're building or generating outputs where one model's blind spots could cause downstream problems

•        You have a SuperGrok or X Premium+ subscription and want to push what's possible today

And if you're not sure which to use: start with Non-Reasoning for any task under 5 minutes of human effort. If the output quality isn't meeting your standard, step up to Reasoning. Reserve Multi-Agent for the 20% of tasks where comprehensive accuracy actually justifies the extra processing time.

8. What's Coming Next: Grok 4.20 Beta 3 and Beyond

xAI is moving fast. As of March 12, 2026, Elon Musk confirmed that Beta 3 is already in active development, with "many fixes and functionality gains" promised. No specific timeline was given, but the Beta 1 to Beta 2 gap was 14 days (Feb 17 to Mar 3). Expect Beta 3 within similar range.

Beta 2 (March 3, 2026) already addressed five specific reliability issues from the initial launch:

•        Improved instruction following on multi-step prompts

•        Reduced capability hallucination (where the model claims it can do something it can't)

•        Better LaTeX and scientific text rendering

•        More reliable image search integration

•        Improved multi-image display handling

The outstanding bottleneck is API access for the Multi-Agent Beta. As of mid-March 2026, the 4-agent system is consumer-facing only. xAI hasn't published a timeline for developer API access, but it's the feature the developer community is most waiting for. When that gate opens, expect a fast-moving wave of third-party integrations.

There's also the Grok 5 question. Reports from early 2026 have speculated about a model with up to 6 trillion parameters - though xAI hasn't confirmed timelines or architecture. The Rapid Learning Architecture of 4.20 suggests that whatever "Grok 5" becomes, the iteration approach is changing. xAI is building a model that improves in production, not just in training runs.

What I'm watching: The Rapid Learning Architecture is the real long-term play here. Every week of real-world usage compounds into a better model without a version update. Six months from now, the Grok 4.20 you're using will be meaningfully smarter than the one that launched in February - and that's a fundamentally different product philosophy than any of its competitors are running.

9. FAQ: Everything People Are Asking About Grok 4.20

What is Grok 4.20 Beta?

Grok 4.20 Beta is xAI's latest AI model family, launched in public beta on February 17, 2026. It introduces a native 4-agent multi-agent architecture where specialized AI agents named Grok, Harper, Benjamin, and Lucas work simultaneously on complex queries. It also introduces a Rapid Learning Architecture that updates the model's capabilities weekly based on real-world usage, without requiring a manual version update.

What is the difference between Grok 4.20 Non-Reasoning and Reasoning?

Non-Reasoning gives direct, fast answers without chain-of-thought processing -output speed is 232 tokens/second with 0.54-second time-to-first-token. Reasoning Preview adds an extended internal thinking phase before responding, producing more accurate answers on complex logic, math, and multi-step problems. Non-Reasoning scores 30 on the Artificial Analysis Intelligence Index; Reasoning scores 48. Non-Reasoning is cheaper per call due to fewer tokens generated on the reasoning step.

How does Grok 4.20's Multi-Agent Beta work?

Grok 4.20 Multi-Agent Beta uses four specialized AI agents running in parallel on a shared MoE backbone. Grok the Captain decomposes the query, Harper researches with real-time X and web data, Benjamin handles logic and math, and Lucas provides contrarian analysis to catch errors. They debate internally before synthesizing a final answer. This peer-review mechanism reduces hallucinations from approximately 12% to roughly 4.2%, according to benchmark data.

What is Grok 4.20 Heavy mode?

Grok 4.20 Heavy mode scales the multi-agent system from 4 agents to 16 agents for more demanding tasks. Available to SuperGrok and Heavy subscribers, it applies the same parallel processing and peer-review workflow at greater depth and breadth. Elon Musk described Grok 4.20 Heavy (Beta 2) as "extremely fast for deep analysis" on March 12, 2026.

How does Grok 4.20 compare to Claude Opus 4.6?

Grok 4.20 Reasoning scores 48 on the Artificial Analysis Intelligence Index vs Claude Opus 4.6's estimated 55. Claude leads on coding quality, documentation, and production-ready software engineering tasks. Grok 4.20 leads on hallucination resistance (78% vs ~63% Omniscience score) and is significantly cheaper - $2/$6 per million tokens vs $5/$25 for Claude Opus 4.6. For high-volume use cases where reliability matters, Grok's price-to-reliability ratio is currently the strongest in the frontier tier.

How does Grok 4.20 compare to GPT-5.4?

GPT-5.4 and Gemini 3.1 Pro Preview both outscore Grok 4.20 Reasoning on the Intelligence Index (57 vs 48). However, Grok 4.20 leads on hallucination resistance, is cheaper on input tokens ($2 vs $2.50) and significantly cheaper on output tokens ($6 vs $14 per million). GPT-5.4 has a much smaller context window (128K vs Grok 4.20's 2M tokens). For real-time data needs, Grok's X integration is a capability GPT-5.4 doesn't match natively.

What is the Grok 4.20 API price?

Grok 4.20 Beta Non-Reasoning and Reasoning Preview are both priced at $2.00 per million input tokens and $6.00 per million output tokens, based on median rates across API providers as of March 2026. A 50% batch API discount is available. API access for the Multi-Agent Beta variant is still listed as "coming soon." Consumer access requires SuperGrok ($30/month or $300/year) or X Premium+ subscription.

Is Grok 4.20 available for free?

Grok 4.20 Beta requires either a SuperGrok subscription ($30/month) or X Premium+ membership for consumer access. There is no confirmed free tier for Grok 4.20 at this time. API access is billed per token. Previous Grok models had limited free usage through X - xAI has not confirmed whether that will extend to 4.20 beyond the beta period.

What is the Grok 4.20 context window?

Grok 4.20 maintains the same 2-million token context window as Grok 4.1. This is the largest context window among Western frontier AI models, exceeding Gemini 3.1 Pro (1M+ tokens), Claude Opus 4.6 (200K tokens), and GPT-5.4 (128K tokens). In Multi-Agent mode, the 2M token limit is shared across all four agents.

When will Grok 4.20 API access for Multi-Agent Beta open?

As of March 14, 2026, xAI has not published a specific timeline for Multi-Agent Beta API access. The current developer API offers Non-Reasoning and Reasoning Preview variants. Grok 4.20 Beta 3 is confirmed to be in development, with Elon Musk citing it on March 12, 2026 - API access may arrive alongside or shortly after that release.

Does Grok 4.20 support image input?

Yes. Grok 4.20 Beta 0309 (Non-Reasoning) supports both text and image input, with text output. Accepted image formats are JPG/JPEG and PNG. The model can analyze, describe, and answer questions about images. Multi-image display was specifically improved in Beta 2 (March 3, 2026), addressing stability issues from the initial launch.

Recommended Blogs:

1. GPT-5.4 vs Gemini 3.1 Pro 

2. GPT-5.4 Review 2026 

3. GPT-5.3-Codex vs Claude vs Kimi 

4. Cheap Claude Alternative for AI Agents 

5. 6 AI Launches Feb 2026 

6. Grok AI Image Safety Crisis Jan 2026 

References & Sources:

1. Artificial Analysis Leaderboard  → 

2. xAI Models Documentation  → 

3. xAI API Pricing  → 

4. SWE-bench Leaderboard  → 

I've been building RAG systems for two years. And every single time, the messiest part wasn't the LLM - it was the embedding pipeline. One model for text. Another for images. A separate transcription step before you could even touch audio. It was duct tape all the way down.

On March 10, 2026, Google changed that. Gemini Embedding 2 is the first natively multimodal embedding model from Google - one model that maps text, images, video, audio, and PDFs into a single unified vector space. No separate pipelines. No translation overhead. One API call, one embedding space, five modalities.

Early adopters are already reporting 70% latency reductions. Legal discovery teams saw a 20% improvement in recall. These aren't lab numbers - they're production results from companies that replaced 3-model pipelines with one endpoint.

Here's everything you need to know: what it is, how it compares, how to use it, and honestly - when it's worth the price and when it isn't.

1. What Is Gemini Embedding 2?

Gemini Embedding 2 is Google's first natively multimodal embedding model, available since March 10, 2026 via the Gemini API and Vertex AI under the model ID gemini-embedding-2-preview.

An embedding model converts raw content - a paragraph of text, a product photo, a customer support call recording - into a numerical vector. Once everything lives in the same vector space, you can run similarity searches across modalities. Ask a text question, get back a relevant video. Match an image to a product description. Search a PDF knowledge base by speaking into a microphone. That's the promise of unified multimodal embeddings.

Previous embedding models, including Google's own gemini-embedding-001, handled text only. If you wanted to embed images, you needed a separate model - CLIP, Voyage Multimodal, or similar. If you needed audio, you'd transcribe it first with Whisper, then embed the transcript. Each step added latency, cost, and potential information loss.

Gemini Embedding 2 collapses that entire pipeline into a single model. Logan Kilpatrick, Google DeepMind's Developer Relations lead, described the goal at launch: bring text, images, video, audio, and documents into the same embedding space without any intermediate translation.

Key Fact

Gemini Embedding 2 launched on March 10, 2026 as Google's first natively multimodal embedding model. Model ID: gemini-embedding-2-preview. Available on both the Gemini API and Vertex AI.

2. Key Features and Technical Specs

The spec sheet is where things get interesting. Gemini Embedding 2 packs a lot into a single API endpoint. Here's what matters:

Supported Input Modalities

•        Text - standard text passages, queries, code snippets

•        Images - up to 6 images per request

•        Video - up to 128 seconds per request

•        Audio -up to 80 seconds per request

•        PDFs - up to 6 pages per request

Core Specs

•        Input token limit: 8,192 tokens (4x more than embedding-001's 2,048)

•        Output dimensions: Flexible, 128 to 3,072 (Matryoshka Representation Learning)

•        Default output: 3,072-dimensional float vector

•        Recommended dimensions: 768 (sweet spot), 1,536, or 3,072

•        Language support: 100+ languages; top MTEB Multilingual leaderboard ranking

•        Custom task instructions: Specify task:code_retrieval, task:search_result, etc. to tune embeddings

What Makes It Different

Two things stand out to me. First, the 8,192 token context window - that's four times what embedding-001 offered, and it matters enormously for embedding long documents without chunking them into tiny fragments. Second, the Matryoshka dimension flexibility: you can truncate output vectors to any size from 128 to 3,072 without retraining. Smaller vectors = cheaper storage + faster search, with minimal quality loss at 768 dimensions.

Pro Tip

Google explicitly recommends 768 dimensions as the sweet spot - 'near-peak quality at roughly one-quarter the storage footprint of 3,072 dimensions.' For most production use cases, 768 is the right default.

3. Benchmark Performance: How Good Is It Really?

Google published benchmark results across text, image, video, and multilingual tasks. The headline numbers:

•        MTEB Multilingual: 69.9 - top of the leaderboard across 100+ languages

•        MTEB Code: 84.0 - strongest open-API result for code retrieval

•        Video retrieval (Vatex, MSR-VTT, Youcook2): outperforms all competing models by a wide margin

•        Image benchmarks (TextCaps, Docci): competitive with Voyage Multimodal 3.5

The text-only MTEB gap between Gemini and competitors is real but not enormous. Where Gemini Embedding 2 has a genuine and significant lead is in the multimodal columns - especially video retrieval. No other commercial model currently handles video natively in an embedding endpoint.

I want to be honest here: for pure text RAG, OpenAI's text-embedding-3-large scores well and costs 35% less. If your pipeline is text-only with no plans to go multimodal, Gemini Embedding 2 isn't an obvious upgrade on benchmark quality alone. The story changes completely if you need cross-modal search.

Real-world production results are even more compelling. Sparkonomy (a creator platform) reported 70% latency reduction after replacing a 3-model pipeline with Gemini Embedding 2. Legal discovery platform Everlaw saw a 20% lift in recall for searching across heterogeneous legal documents. The gains aren't from faster hardware - they're from removing intermediate processing stages entirely.

4. Gemini Embedding 2 vs Competitors

Here's how Gemini Embedding 2 stacks up against the main alternatives:

The comparison table tells you most of what you need to know. Gemini Embedding 2 is the only model covering all five modalities (text, image, video, audio, PDF) in a single vector space. OpenAI covers text only. Cohere Embed 4 handles text + images. Nobody else touches video or audio natively.

The pricing is fair for what you get. At $0.20/M tokens, it's more expensive than OpenAI's text-embedding-3-small ($0.02/M) - but that comparison is apples-to-oranges. Compare it against building an equivalent pipeline yourself (text model + CLIP for images + Whisper + audio embedding) and Gemini Embedding 2 almost certainly wins on both cost and complexity.

For more on Google's recent model releases, see our deep-dives on GPT-5.4 vs Gemini 3.1 Pro and Gemini 3.1 Flash Lite vs 2.5 Flash.

5. Pricing Breakdown: Is It Worth It?

$0.20 per million text tokens -that's the standard rate. The batch API cuts that to $0.10/M (50% off) for workloads that don't need real-time responses. Image, audio, and video inputs follow Gemini API's standard media token rates.

Quick math on the batch pricing: embed 1 million documents at 500 tokens each (375 words average), that's 500 billion tokens... wait, no - that's 500 million tokens total. At $0.10/M via batch, you're looking at $50 for 1 million documents. That's reasonable for most production workloads.

When It's Worth It

•        You're building cross-modal search (text queries over image/video/audio libraries)

•        Your pipeline currently chains 3+ specialized models together

•        You need 100+ language support with high multilingual recall

•        You want to embed meeting recordings, product images, and docs in the same search index

When It's Not Worth It

•        Text-only RAG pipeline with no multimodal plans - OpenAI text-embedding-3-small at $0.02/M is 10x cheaper

•        You need vectors compatible with existing gemini-embedding-001 indexes (embedding spaces are incompatible - you'd need to re-embed your entire dataset)

•        Very long document context required - Voyage voyage-3.5 offers 32K token context vs Gemini's 8,192

Important Note

The embedding spaces between gemini-embedding-001 and gemini-embedding-2-preview are incompatible. If you're upgrading from embedding-001, you must re-embed your entire dataset. There is no migration path that preserves existing vectors.

6. Matryoshka Dimensions: Choose the Right Size

Matryoshka Representation Learning (MRL) lets you truncate the output vector to any size between 128 and 3,072 dimensions without retraining the model. Smaller vectors trade a little quality for significantly cheaper storage and faster similarity search.

Google's own guidance: 768 dimensions delivers near-peak quality at one-quarter the storage cost of 3,072. I'd agree with that as a default starting point. If you're running high-stakes retrieval (legal discovery, medical records, financial documents), go 3,072. For everything else, start at 768 and run A/B tests before committing.

Storage perspective: 1 million vectors at 3,072 dimensions (float32) uses approximately 12 GB. At 768 dimensions, that's about 3 GB. If you're indexing tens of millions of items, that difference becomes very real in your infrastructure costs.

7. How to Use It: Python Tutorial (Step by Step)

Here's a complete walkthrough, from API key to embedding your first multimodal content.

Step 1: Install the SDK

pip install google-genai

Step 2: Basic Text Embedding

from google import genai

client = genai.Client(api_key='YOUR_API_KEY')

result = client.models.embed_content(
    model='gemini-embedding-2-preview',
    contents='What is the best embedding model in 2026?'
)

print(result.embeddings[0].values[:5])  # Preview first 5 dimensions
# Output: [0.023, -0.041, 0.087, 0.012, -0.065, ...]

Step 3: Multimodal Embedding (Text + Image)

from google import genai
from google.genai import types

import base64
client = genai.Client(api_key='YOUR_API_KEY')
# Load and encode your image

with open('product_image.jpg', 'rb') as f:
    image_data = base64.b64encode(f.read()).decode('utf-8')

# Embed text and image together
result = client.models.embed_content(
    model='gemini-embedding-2-preview',
    contents=[
        'Blue wireless headphones with noise cancellation',
        types.Part.from_bytes(data=base64.b64decode(image_data),
                              mime_type='image/jpeg')

    ],

    config=types.EmbedContentConfig(
        task_type='RETRIEVAL_DOCUMENT',
        output_dimensionality=768  # Use Google's recommended size
    )
)

print(len(result.embeddings[0].values))  # 768

Step 4: Semantic Search with Cosine Similarity

from sklearn.metrics.pairwise import cosine_similarity
import numpy as np

# Assume you have a list of pre-computed document embeddings
query = 'wireless headphones for travel'
query_result = client.models.embed_content(
    model='gemini-embedding-2-preview',
    contents=query,
    config=types.EmbedContentConfig(
        task_type='RETRIEVAL_QUERY',
        output_dimensionality=768
    )

)

query_vec = np.array(query_result.embeddings[0].values).reshape(1, -1)

# Compare against stored document vectors
scores = cosine_similarity(query_vec, document_vectors)[0]
top_k = scores.argsort()[-5:][::-1]  # Top 5 results
print('Top matches:', [documents[i] for i in top_k])

Notice the task_type parameter - use RETRIEVAL_QUERY for search queries and RETRIEVAL_DOCUMENT for documents being indexed. This is one of the improvements in Gemini Embedding 2 over older models: specifying intent directly improves embedding quality for your actual use case.

For a broader look at building AI pipelines, see our guide on How to Build No-Code Automation with Make.com + ChatGPT.

8. Real-World Use Cases

Where does Gemini Embedding 2 actually shine? Here are the use cases that become significantly easier when you have a single multimodal embedding space:

Multimodal E-commerce Search

Embed product titles, descriptions, and product images into the same vector space. Let customers search with text ("blue running shoes under $100") and return results ranked by similarity across both text AND visual features. Previously this required aligning CLIP vectors with text embeddings - a messy reconciliation problem Gemini Embedding 2 eliminates.

Audio Knowledge Base Search

Embed meeting recordings, podcast episodes, or support calls directly - no transcription step required. A support agent can type a customer's complaint and instantly surface similar past calls from the knowledge base, even if no one ever transcribed them.

Legal and Document Discovery

This is where the 20% recall improvement Everlaw reported comes from. Legal discovery requires searching across scanned PDFs, image attachments, video depositions, and text documents simultaneously. A unified embedding space means one query covers all of them. That's not a minor improvement - missing a relevant document in discovery has real consequences.

RAG Systems with Richer Context

Standard text-only RAG misses context that lives in charts, diagrams, and images embedded in documents. With Gemini Embedding 2, your RAG pipeline can retrieve based on visual content inside PDFs, not just the surrounding text. For technical documentation, research papers, and financial reports, this is a meaningful quality upgrade.

If you're building AI-powered tools, check out what's possible with Google Pomelli AI and NotebookLM Cinematic Video Overview - Google's broader AI tooling ecosystem is getting serious.

9. Limitations and When NOT to Use It

I'd be doing you a disservice if I didn't flag the real limitations here.

•        Still in preview: The model ID is gemini-embedding-2-preview. Google could change pricing or behavior before GA. They've done this with previous models, though the GA pricing typically matches preview pricing.

•        Per-request media caps: 6 images, 80s audio, 128s video, 6 PDF pages per request. Fine for indexing individual items, but you'll hit limits trying to embed large documents in a single call.

•        Incompatible vector spaces: Cannot migrate from gemini-embedding-001. A full re-embedding of your dataset is required. For large production indexes, this is a significant operational cost.

•        Text-only use cases pay a price premium: OpenAI text-embedding-3-small at $0.02/M is 10x cheaper for text-only workloads. Unless you need cross-modal search, the premium may not be justified.

•        Context window ceiling: 8,192 tokens is good, but Voyage voyage-3.5 offers 32K. For very long document embedding without chunking, Voyage still wins on context.

•        No vector compatibility with older Gemini embeddings: Each generation produces fundamentally different representations. Plan for re-indexing costs in your migration budget.

My honest take: if you're building a new system from scratch with any multimodal requirements - start here. If you're migrating a large text-only production system - do the cost math carefully before committing to the re-embedding cost.

FAQ: Gemini Embedding 2

What is the Gemini Embedding 2 model?

Gemini Embedding 2 (model ID: gemini-embedding-2-preview) is Google's first natively multimodal embedding model, launched March 10, 2026. It maps text, images, video, audio, and PDFs into a single unified 3,072-dimensional vector space, eliminating the need for separate embedding models per modality.

What embedding model does Gemini use?

As of March 2026, Google offers two main embedding models: gemini-embedding-001 (text-only, generally available, GA) and gemini-embedding-2-preview (multimodal, in public preview). For new projects requiring cross-modal search, gemini-embedding-2-preview is the recommended option.

Can I use Gemini for embeddings?

Yes. Gemini Embedding 2 is accessible via the Gemini API (google-genai Python SDK) and Vertex AI. A free tier is included. Paid usage is $0.20 per million text tokens, or $0.10/M via the batch API. A Google AI Studio API key is all you need to get started.

What is the use of the Gemini Embedding model?

Embedding models convert content into numerical vectors for semantic similarity tasks. Common applications include RAG (Retrieval Augmented Generation) systems, semantic search, document clustering, recommendation systems, and content deduplication. Gemini Embedding 2 extends all of these to work across text, images, video, audio, and documents simultaneously.

What is the best Gemini model for embeddings in 2026?

For multimodal use cases: gemini-embedding-2-preview. For text-only production workloads already using embedding-001: stick with embedding-001 (generally available, no re-embedding required). For text-only workloads starting fresh and cost-sensitive: OpenAI text-embedding-3-small at $0.02/M is 10x cheaper.

How much does Gemini Embedding 2 cost?

$0.20 per million text tokens (standard), $0.10 per million tokens via the batch API (50% discount). Image, audio, and video inputs are billed at Gemini API media token rates. A free tier is available for testing and development.

What are the output dimensions for Gemini Embedding 2?

Gemini Embedding 2 uses Matryoshka Representation Learning, supporting flexible output dimensions from 128 to 3,072. The default is 3,072. Google recommends 768 as the sweet spot for production use - near-peak quality at one-quarter the storage cost.

Is Gemini Embedding 2 compatible with gemini-embedding-001?

No. The embedding spaces are incompatible. If you're migrating from gemini-embedding-001 to gemini-embedding-2-preview, you must re-embed your entire dataset. There is no migration path that preserves existing vectors.

References & Further Reading

•        Gemini Embedding 2 Official Model Docs — Google AI for Developers

•        Embeddings Guide — Gemini API Documentation

•        Gemini Embedding 2 on Vertex AI — Google Cloud Docs

•        Gemini Embedding 2 Pricing Analysis — TokenCost

•        Embedding Models Pricing — Awesome Agents

I woke up Tuesday to one of the most genuinely interesting funding announcements in years. Not another LLM wrapper. Not yet another "we're building AGI" pitch deck. A Turing Award winner who spent 12 years building Meta's AI research lab, publicly called the entire industry wrong, then left to prove it - just raised $1.03 billion from Jeff Bezos, NVIDIA, and Mark Cuban at a $3.5 billion valuation.

Less than three months old. About a dozen employees. Zero revenue. Zero product.

And investors handed him a billion dollars.

Here's everything you need to know about Yann LeCun, AMI Labs, and why this moment could matter more than any GPT update this year.

1. Who Is Yann LeCun and Why Did He Leave Meta?

Yann LeCun is one of three people who built the mathematical foundation for modern AI. In 2018, he shared the Turing Award - computing's Nobel Prize - with Geoffrey Hinton and Yoshua Bengio for their work on deep learning and neural networks. Without that work, there is no ChatGPT, no Gemini, no Claude. The entire industry is built on what they figured out decades ago.

He joined Facebook in 2013 to build what became FAIR - Meta's Fundamental AI Research lab. For 12 years, FAIR produced some of the most cited research in the world, including early open-source models that the entire industry built on top of.

So why leave?

In November 2025, LeCun walked into Mark Zuckerberg's office and told him he was done.

Multiple reports cite a series of disagreements. Meta's AI efforts had shifted hard toward commercial LLM products under Meta Superintelligence Labs, led by former Scale AI CEO Alexandr Wang - a 29-year-old executive LeCun had publicly described as inexperienced. The Llama 4 benchmark controversy didn't help. And LeCun had been saying for years, loudly and publicly, that LLMs were architecturally incapable of producing true intelligence.

The disagreement wasn't small. It was philosophical. LeCun believed the entire direction of the industry was wrong. And Meta was doubling down on it.

So he left to build something different.

2. What Is AMI Labs and Who Is Funding It?

Advanced Machine Intelligence Labs - AMI, pronounced like the French word for "friend," was announced on March 10, 2026, just four months after its founding in late 2025.

Here are the numbers that matter:

The round was co-led by Cathay Innovation, Greycroft, Hiro Capital, HV Capital, and Bezos Expeditions. Strategic investors include NVIDIA, Samsung, Temasek, Toyota Ventures, SBVA, Sea, and Alpha Intelligence Capital. Notable individual backers include Jeff Bezos, Mark Cuban, and former Google CEO Eric Schmidt.

For context: this is the largest seed round in European startup history. The only larger seed globally was Thinking Machines Lab's $2 billion raise in June 2025.

The leadership team is drawn almost entirely from Meta's FAIR research organization. Alexandre LeBrun - former CEO of Nabla, a clinical AI startup serves as CEO. LeCun is Executive Chairman. Saining Xie is Chief Science Officer, Pascale Fung is Chief Research and Innovation Officer, and Michael Rabbat leads World Models research.

One thing I'll say: this team is unusually research-heavy for a company at seed stage. That's either brilliant or a very expensive experiment. Probably both.

3. What Are World Models - and How Are They Different From LLMs?

World models are AI systems that learn how physical reality works, not just how language works.

Here's the simplest way to think about it:

A large language model like GPT-5 or Claude Sonnet is trained on text. It learns statistical patterns in language - what word is likely to follow another, what a coherent paragraph looks like, how to reason through a coding problem by predicting one token at a time. It's extraordinarily good at this. And extraordinarily limited by it.

Ask an LLM to help you write an email and it's excellent. Ask it to predict what happens if you push a glass off a table and it can only reason from text descriptions of physics - not from any actual understanding of how gravity or mass or surface friction works.

A world model learns from video, spatial data, and real-world interaction. It builds an internal model of how the physical world operates: cause and effect, physics, time, consequences.

The implications are significant. A world model can:

•        Plan sequences of actions because it can predict what those actions will cause

•        Reason about 3D space, not just 2D text

•        Maintain persistent memory across time

•        Operate in environments - factories, hospitals, robots - where hallucinating is dangerous

LLMs hallucinate because they're pattern-matching machines, not reasoning machines. In a medical setting, that's a liability. In a factory, it's a safety risk. World models, in theory, address this at the architectural level.

That's the bet.

4. What Is JEPA? The Architecture Behind the Billion-Dollar Bet

JEPA stands for Joint Embedding Predictive Architecture. LeCun proposed it in 2022, before the GPT-4 wave hit.

The key difference from a Transformer model comes down to what gets stored and what gets predicted.

In a standard Transformer, every piece of input - every pixel, every token - gets stored in a mathematical representation. Then the model predicts the next token. This works well for language, which is discrete and sequential. It works poorly for video and real-world data, which is continuous, high-dimensional, and full of irrelevant noise.

JEPA works differently: instead of predicting exact outputs at the pixel or token level, it predicts abstract representations of data - high-level patterns - while ignoring unpredictable details.

Think of it this way: if you watch a video of a ball rolling across a table, you don't need to predict every pixel. You need to predict the concept - ball, motion, trajectory, outcome. JEPA learns to work at that conceptual level.

The practical result is a model that can:

•        Learn from video data without being overwhelmed by irrelevant visual noise

•        Build compressed, abstract representations of environments

•        Predict the consequences of actions in those environments

•        Plan based on those predictions

LeCun proposed JEPA three years before AMI Labs existed. The fact that he immediately secured $1.03 billion to commercialize it tells you something about how seriously the research community takes this direction - even if the commercial applications are years away.

5. World Models vs LLMs: The Case LeCun Is Making

LeCun has been making this argument publicly for years. Let me lay out the strongest version of it alongside the strongest counterarguments.

The LeCun Case Against LLMs

His core claim: LLMs predict tokens. Token prediction, no matter how good, cannot produce systems that understand causality, reason about physical reality, or plan meaningful action sequences. "Generative architecture trained by self-supervised learning mimic intelligence; they don't genuinely understand the world," LeBrun wrote in the funding announcement.

Hallucinations are a symptom, not a bug. When a model generates confident nonsense, it's because the system doesn't have a grounded model of reality - only statistical patterns. No amount of RLHF fixes that at the architectural level.

The Counterargument

OpenAI, Anthropic, and Google would all push back here. Reasoning models like o3 and Claude Opus have shown that chain-of-thought processes can produce genuinely impressive planning and causal reasoning - from language. The "dead end" claim is contested.

And there's a practical reality: LLMs are already in production at scale, generating billions in revenue, improving rapidly. World models are theoretical. AMI Labs has no product and no revenue timeline.

My Take

Both can be right. LLMs may be approaching their ceiling on certain classes of problems - particularly anything requiring true physical understanding, long-horizon planning, or operation in dangerous real-world environments. World models may genuinely address those gaps. But "LLMs are a dead end" overstates the case. They're not a dead end. They're a different road.

What LeCun is building isn't a replacement for GPT-5. It's a parallel bet on a different paradigm for a different class of problems.

6. What Will AMI Labs Actually Build?

Short answer: not much immediately. And the team is honest about it.

"AMI Labs is a very ambitious project, because it starts with fundamental research. It's not your typical applied AI startup that can release a product in three months," CEO LeBrun told TechCrunch. The company expects it could take years for world models to move from theory to commercial applications.

What they are doing now:

•        Building the foundational world model architecture using JEPA

•        Publishing research papers openly (LeCun is committed to open science)

•        Open-sourcing portions of the code

•        Partnering with Nabla (a clinical AI startup used by 85,000 clinicians across 130+ US health systems) as the first real-world deployment partner

The longer-term applications being discussed include healthcare, industrial robotics, and - potentially - Meta's Ray-Ban smart glasses. LeCun mentioned discussions with Meta about deploying AMI's technology in the glasses as "one of the shorter-term potential applications."

The $1.03 billion funds two things: compute and talent. Four offices. A small team of elite researchers. And time. Lots of time.

I'll be honest: this is either the most patient bet in AI history or the most expensive research grant ever written. The difference depends entirely on whether JEPA works at scale.

7. Why This Could Change Everything (Or Nothing)

Let me give you the two scenarios.

Scenario A: LeCun Is Right

In three to five years, AMI Labs produces world models capable of persistent memory, physical reasoning, and multi-step planning in real environments. Robotics companies integrate the technology. Healthcare AI moves beyond documentation to actual clinical reasoning. Industrial automation becomes viable in unstructured environments.

The LLM paradigm doesn't disappear - but it gets bounded to language-native tasks. A new ecosystem emerges. AMI Labs is at the center of it, with a $3.5 billion valuation that looks cheap in retrospect.

Scenario B: The Timing Is Wrong

LLMs continue improving faster than expected. Reasoning models close the planning gap. Physical world understanding gets grafted onto transformer architectures through multimodal training. AMI Labs produces interesting research but no commercially viable product. The $1.03 billion funds five years of academic papers and a pivot.

The honest answer: nobody knows. But the combination of LeCun's research credibility, the JEPA architecture, the quality of the founding team, and the fact that Fei-Fei Li's World Labs raised $1 billion at roughly the same time suggests the smart money sees something real here.

And I'd rather watch this bet play out than pretend it doesn't exist.

Frequently Asked Questions

Why did Yann LeCun leave Meta?

Yann LeCun left Meta in November 2025 after 12 years as Chief AI Scientist. Reports cite disagreements with leadership over the direction of AI research, including frustration with Meta's shift toward commercial LLM development under Meta Superintelligence Labs and tensions with CEO Mark Zuckerberg. LeCun had publicly argued for years that LLMs were architecturally limited and that the industry needed a different approach.

What is AMI Labs and what does AMI stand for?

AMI Labs stands for Advanced Machine Intelligence Labs. It is an AI research startup co-founded by Yann LeCun and Alexandre LeBrun in late 2025. AMI is pronounced like the French word for "friend." The company is building world models - AI systems that learn from physical reality - and is headquartered in Paris with offices in New York, Montreal, and Singapore.

How much did AMI Labs raise and who invested?

AMI Labs raised $1.03 billion (approximately €890 million) in a seed round at a $3.5 billion pre-money valuation, announced on March 10, 2026. The round was co-led by Cathay Innovation, Greycroft, Hiro Capital, HV Capital, and Bezos Expeditions. Additional backers include NVIDIA, Samsung, Temasek, Toyota Ventures, Mark Cuban, and Eric Schmidt.

What is JEPA architecture?

JEPA, or Joint Embedding Predictive Architecture, is an AI model architecture proposed by Yann LeCun in 2022. Unlike standard transformer models that predict the next token or pixel, JEPA learns abstract representations of data - predicting high-level patterns while ignoring irrelevant details. This makes it theoretically better suited for learning from video and real-world data, which is the foundation of AMI Labs' world model research.

What are world models in AI?

World models are AI systems designed to learn how the physical world works - including physics, cause and effect, spatial relationships, and temporal dynamics - rather than learning from text alone. World models can theoretically reason about the consequences of actions, plan action sequences, and operate in real-world environments like factories and hospitals where hallucinations could be dangerous.

Are world models better than large language models?

World models and LLMs are optimized for different tasks. LLMs like GPT-5 and Claude excel at language-native tasks including writing, coding, summarization, and reasoning. World models are theoretically better suited for physical reasoning, robotics, long-horizon planning, and environments requiring grounded understanding. Whether AMI Labs' approach will outperform LLMs on key benchmarks remains to be seen - the technology is still in early research stage as of 2026.

When will AMI Labs release a product?

AMI Labs has not announced a product release timeline. CEO Alexandre LeBrun told TechCrunch that this is "not your typical applied AI startup" and that it could take years for world models to move from theory to commercial applications. The company's first disclosed partner is Nabla, a clinical AI startup, which will gain early access to AMI's models once available.

Is AMI Labs open source?

AMI Labs has committed to publishing research papers openly and open-sourcing portions of its code. CEO Alexandre LeBrun confirmed this, stating that "things move faster when they're open." However, not all code or model weights will be open source the company will selectively release components to build a research community.

Reference

1. TechCrunch — AMI Labs $1.03B raise

2. Yann LeCun's original JEPA paper — "A Path Towards Autonomous Machine Intelligence" (2022)

3. The Next Web — "Yann LeCun just raised $1bn to prove the AI industry has got it wrong"

4. Satvik's viral LinkedIn post

Recommended blogs

These are real posts that exist on buildfastwithai.com right now:

"LLMs" explainer

Meta AI / DeepConf — closest you have to a Meta AI research post:

AI Weekly Recap Feb 2026

GPT-5 Reality Behind the Hype

Could AI Replace You at Work?

I spent half of last Tuesday switching between Google Docs, Canva, and a spreadsheet to get three Instagram posts out the door for a single campaign. Three tools. One campaign. That is not a workflow - that is a tax on your time.

Google noticed. On October 28, 2025, Google Labs and Google DeepMind quietly dropped Pomelli: a free AI marketing tool that scans your website, builds a brand profile it calls Business DNA, and generates social media campaigns, ad creatives, product photography, and even animated videos - all in one place.

As of March 9, 2026, Pomelli just expanded from 4 countries to over 170. That includes India. So if you have been staring at the "not available in your region" error, that is over now.

Here is my honest breakdown of what Pomelli actually does, where it wins, where it falls flat, and how it stacks up against Canva, Jasper, and Adobe Express.

1. What Is Google Pomelli AI?

Google Pomelli is a free AI-powered marketing tool from Google Labs, built in partnership with Google DeepMind, that analyzes your website and automatically generates on-brand social media campaigns, ad creatives, and product photography.

Launched on October 28, 2025, Pomelli targets small and medium-sized businesses (SMBs) that do not have in-house design teams or marketing agencies. The core idea is simple: instead of manually uploading brand assets and selecting templates, you give Pomelli your website URL. It scans your site and builds what Google calls a Business DNA profile - your brand colors, fonts, tone of voice, and visual style - automatically. Then it generates content grounded in that profile.

Think of it as Canva meets ChatGPT, but trained specifically on your brand rather than on generic templates.

I want to be clear about one thing right away: Pomelli is NOT a Google Ads tool. It does not push content directly to Instagram, Facebook, or LinkedIn. You download the assets and post them manually. That is a real gap, and I will come back to it.

Quotable stat: 73% of small businesses struggle with consistent brand messaging across digital channels, according to the Small Business Digital Alliance. Pomelli was built to fix exactly that.

2. How Google Pomelli Works (3 Steps)

Pomelli's workflow is refreshingly simple. You do not need design experience. You do not need to upload a brand kit. The entire setup takes under five minutes.

Step 1: Enter Your Website URL

Go to labs.google.com/pomelli and sign in with your Google account. Enter your business website URL. Pomelli scans your public pages - homepage, blog posts, product pages, existing images - and extracts your brand identity.

The system works best with websites that have substantial text content and a consistent visual style. If your site is mostly stock images or has no clear color scheme, the output quality will drop. You can also supplement the scan with additional brand images if you have them.

Step 2: Get Your Business DNA Profile

After the scan (usually takes a few minutes), Pomelli generates your Business DNA profile. This includes:

•        Your primary, secondary, and accent color palette

•        Your brand fonts and typography preferences

•        Your tone of voice - formal, casual, technical, accessible

•        Visual style extracted from your existing imagery

Every piece of content Pomelli generates is anchored to this profile. In testing, users reported that the system picked up subtle word choices and color preferences that even they had not explicitly defined. That is the DeepMind language understanding doing the heavy lifting.

Step 3: Generate and Edit Your Campaign Assets

Pomelli suggests campaign ideas based on your Business DNA. You can pick from those suggestions or type your own prompt - something like "summer sale for running shoes" or "new product launch post for Instagram." The tool then generates multiple variations in roughly 30 to 90 seconds.

You can edit outputs using natural language commands directly in the tool. Tell it to make the text larger, change the background, or restyle to match a different image. You then download the assets and post them manually on your platforms of choice.

3. Google Pomelli Features in 2026

Pomelli launched with solid core functionality in October 2025, but Google has moved fast with updates. Here is where the product stands as of March 2026.

Business DNA (Core Feature)

The automatic brand extraction is Pomelli's biggest differentiator. No other tool in this category scans your website and builds a complete brand profile without manual input. Canva requires you to upload logos and set colors yourself. Jasper requires manual brand training. Pomelli does it in minutes from your URL alone.

Social Media Content Generation

Pomelli generates platform-ready content for Instagram, Facebook, X/Twitter, LinkedIn, YouTube thumbnails, Google Ads, and email banners. You can generate roughly 10 post variations in about 60 seconds - approximately 30 to 40 percent faster than typical Canva workflows, based on user-reported test data.

Pomelli Animate (Launched January 2026)

Animate, launched in January 2026, is powered by Veo 3.1 - Google DeepMind's advanced video generation model. It transforms your static marketing visuals into on-brand animated videos with one click. This is the feature that separates Pomelli from tools that handle static graphics only.

Pomelli Photoshoot (Launched February 19, 2026)

This is the feature that went viral. Photoshoot uses Nano Banana - Google's image generation model - to transform ordinary product photos taken with a smartphone into professional-grade studio and lifestyle images in seconds. The announcement hit 23 million views on X within days of launch.

You upload your product photo, select a template (studio or lifestyle), add a prompt, and Pomelli generates studio-quality imagery that matches your brand aesthetic. For a small jewelry brand or a local cafe, this replaces a photography budget that could easily run into the thousands.

The output is grounded in your Business DNA, so generated product images stay visually consistent with everything else you create in Pomelli.

Natural Language Editing (February 2026 Update)

Since the February 2026 update, you can edit generated content using plain English commands. Tell the tool to change your background to a forest scene, transfer the style of one image to another, or adjust prompt accuracy. These additions close the gap with Canva's editing capabilities, though Pomelli still lacks Canva's depth of template library and drag-and-drop precision.

4. Is Google Pomelli Available in India?

Yes. As of March 9, 2026, Google Pomelli is available in India and over 170 countries and territories worldwide.

Google Labs made the official announcement on March 9, 2026, expanding from the original four-country beta (US, Canada, Australia, New Zealand) to a global rollout. India is included in this expansion.

Important caveat: Pomelli currently supports English only. If your target audience is Hindi, Tamil, Bengali, or any other Indian language, you will need to use the tool in English for now. Google has not announced a timeline for multilingual support.

To access Pomelli from India: visit labs.google.com/pomelli, sign in with your Google account (must be 18 or older), and start with your website URL. No waitlist, no invitation required, no credit card.

5. Google Pomelli vs Canva vs Jasper vs Adobe Express

This is the question everyone is asking, so here is the honest breakdown. I am not going to tell you Pomelli wins everywhere - it does not. But the pricing gap alone makes the comparison interesting.

Pomelli vs Canva

Canva is more comprehensive. It massive template library, direct social media posting, video editing, and a proven design interface. For presentations, one-off posters, and professional design work, Canva wins.

Pomelli's edge is automation. You do not pick a template and fill it in. Pomelli extracts your brand and generates content already tailored to it. In a test of a 5-asset campaign (3 social posts, 1 ad, 1 email banner), a Pomelli-first workflow completed in 1 hour 23 minutes versus 2 hours 5 minutes with Canva alone - a 33% time saving, with the biggest gains coming from automated copy consistency rather than design speed.

My take: Use both. Pomelli for fast, brand-consistent first drafts. Canva for precise visual refinement. The tools are complementary, not competitive.

Pomelli vs Jasper

Jasper is a long-form copywriting tool. It excels at blog posts, email sequences, and detailed brand narratives. Pomelli focuses on social media campaigns and visual assets. Jasper starts at $49 per month. Pomelli is free.

If you need blog content, email marketing copy, or long sales pages, Jasper is the better choice. If you need brand-consistent social posts and product imagery at speed, Pomelli does it for nothing - and does it in a fraction of the time.

Pomelli vs Adobe Express

Adobe Express costs roughly $100 per year and gives you serious design tools, Creative Cloud integration, and a professional editing experience. It is built for people with design skills or teams with design resources.

Pomelli is built for business owners who hate design. No design experience needed. No Creative Cloud subscription. Just your website URL and an idea.

6. Google Pomelli Pricing: Is It Really Free?

Yes - Pomelli is completely free during the public beta phase. No credit card. No usage limits on generations. No waitlist. You access it at labs.google.com/pomelli with your Google account.

As of March 2026, Google has not announced any monetization plan or post-beta pricing. The smart money says Google will eventually move to a freemium model - possibly integrating Pomelli into Google Workspace or bundling it with Google Ads. But right now, you get unlimited generations, Business DNA profiling, Animate, and Photoshoot for zero cost.

To put this in dollar terms: Pomelli saves you $120 to $180 per year compared to Canva Pro or Adobe Express - and includes studio-quality product photography that neither competitor offers at any price tier.

My contrarian point: Free betas do not last forever. Google has a long history of building experimental tools and then sunsetting them (Google+, Stadia, Inbox). I would use Pomelli aggressively while it is free and build a plan for what happens if pricing arrives or the experiment ends.

7. Honest Limitations: What Pomelli Cannot Do Yet

No tool is perfect, and Pomelli has real gaps you should know about before you build your workflow around it.

•        No direct publishing:No direct publishing.

You cannot post directly to Instagram, Facebook, LinkedIn, or anywhere else from Pomelli. Every asset requires a manual download and upload. If you are managing 20+ posts per week, this gets tedious fast. Pair Pomelli with Buffer or Hootsuite to handle scheduling.

•        English only:English only.

The Business DNA extraction and all content generation work in English only. If you serve a non-English speaking audience, Pomelli is not yet useful for your primary content.

•        Weak-website problem:Weak-website problem.

If your website has minimal text, random stock photos, inconsistent fonts, or no clear brand identity, Pomelli's Business DNA extraction will produce mediocre results. The tool is only as good as the brand signals it can extract. Fix your website first, then run it through Pomelli.

•        No content calendar:No content calendar or scheduling.

Pomelli is a creation tool, not a management platform. There is no calendar view, no approval workflow, no team collaboration features. It is a starting point, not an end-to-end content operation.

•        Beta quality:Beta quality inconsistencies.

This is still an experimental product. Output quality can be inconsistent. Some generations will feel template-influenced rather than genuinely brand-specific, particularly in early testing. The February 2026 update improved this significantly, but it still happens.

8. How to Use Google Pomelli Step by Step

Getting started takes about five minutes. Here is the exact process.

1.     Go to labs.google.com/pomelli in your browser.

2.     Sign in with your Google account. You must be 18 or older.

3.     Enter your business website URL. Pomelli will scan your site and build your Business DNA profile.

4.     Review your Business DNA. If something looks off - wrong colors, wrong tone - you can refine the profile manually before generating content.

5.     Choose a campaign idea from Pomelli's suggestions or type your own prompt.

6.     Browse generated variations. Use natural language commands to edit (change background, resize text, alter style).

7.     Download your final assets and upload them to your platforms manually.

For Photoshoot: upload a product photo, select a template (studio or lifestyle), add a prompt describing the background or setting, and let Pomelli's Nano Banana model generate your studio-quality imagery.

9. Who Should (and Should Not) Use Pomelli

Pomelli is ideal for:

•        Solopreneurs and freelancers creating their own marketing content

•        Small businesses without in-house design or marketing teams

•        E-commerce brands launching products regularly and needing consistent imagery

•        Local businesses (cafes, salons, retail stores) that need professional social content fast

•        Agencies exploring AI tools for client content creation workflows

Pomelli is not the right fit for:

•        Large marketing teams with established creative processes and approval workflows

•        Brands needing video content beyond short social animations

•        Businesses whose primary audience speaks a non-English language

•        Anyone needing long-form copywriting - blogs, email sequences, sales pages

•        Teams that need direct social media scheduling and publishing baked in

My honest recommendation: if you are a small business owner spending more than 3 hours per week on social content creation, run your website through Pomelli today. The worst case is that it saves you 30 minutes. The best case is that it replaces half your content workflow.

Frequently Asked Questions About Google Pomelli AI

What is Google Pomelli AI?

Google Pomelli is a free experimental AI marketing tool from Google Labs and Google DeepMind, launched on October 28, 2025. It analyzes your website URL to build a Business DNA profile (brand colors, fonts, tone of voice) and then generates on-brand social media campaigns, ad creatives, product photography, and animated videos. Access it at labs.google.com/pomelli.

Is Google Pomelli free to use?

Yes, Pomelli is completely free during its public beta phase. There is no credit card required, no waitlist, and no usage limit on generations. Google has not announced post-beta pricing as of March 2026, but paid tiers are expected when the product exits beta.

Is Google Pomelli available in India?

Yes. On March 9, 2026, Google expanded Pomelli from its original four-country beta to over 170 countries and territories, including India. Access requires a Google account and users must be 18 or older. The tool currently supports English only, with no announced timeline for Hindi or other Indian language support.

What is Google Pomelli used for?

Pomelli is used to create on-brand social media marketing content without design experience. Specific use cases include generating Instagram posts, Facebook ads, YouTube thumbnails, Google Ads creatives, email banners, animated brand videos (Animate feature), and professional product photography from smartphone images (Photoshoot feature).

How does Google Pomelli work?

Pomelli works in three steps: (1) Enter your website URL and Pomelli scans your site to extract your brand identity into a Business DNA profile. (2) Pomelli suggests campaign ideas tailored to your brand, or you type your own prompt. (3) Pomelli generates multiple content variations in 30 to 90 seconds, which you can edit using natural language commands and then download.

What is Google Pomelli Photoshoot?

Pomelli Photoshoot, launched on February 19, 2026, uses Google's Nano Banana image generation model to transform ordinary product photos taken with a smartphone into professional-grade studio and lifestyle imagery. Users upload a product photo, select a template, add a prompt, and Pomelli generates studio-quality product images consistent with their Business DNA brand profile.

How is Pomelli different from Canva?

The key difference is automation. Canva requires users to manually set up brand kits, choose templates, and fill in content. Pomelli automatically extracts your brand identity from your website URL and generates complete, brand-consistent assets without manual template selection. Pomelli is also free in beta, while Canva Pro costs $120 per year. However, Canva has a larger template library, direct social media publishing, and more precise design controls.

Which countries is Google Pomelli available in?

As of March 9, 2026, Google Pomelli is available in over 170 countries and territories globally, including India, the United States, Canada, Australia, the United Kingdom, Japan, and most of Europe. The tool is English-only during the current beta phase, regardless of the user's country.

Does Pomelli post directly to social media platforms?

No. Pomelli generates and allows you to download marketing assets, but it does not have direct publishing integration with Instagram, Facebook, LinkedIn, X/Twitter, or any other platform. You download the assets and manually upload them to your platforms. For scheduling, pair Pomelli with a tool like Buffer or Hootsuite.

Ready to Stop Wasting Hours on Social Content?

Pomelli is live, free, and now available in India and 170+ countries. Go to labs.google.com/pomelli, drop in your website URL, and see what your Business DNA looks like. It takes five minutes. If the output surprises you, subscribe for more honest breakdowns of AI tools that are actually worth your time.

Stay Updated If this breakdown helped, subscribe to Build Fast With AI for weekly breakdowns of the latest AI tools, honest reviews, and practical guides for founders and marketers. New posts drop every week.

Internal References

• Nano Banana vs Nano Banana Pro vs Nano Banana 2: Which Google AI Image Model Wins?

• AI Prompts for Images: How Do I Write Good AI Art Prompts?

• India AI Summit 2026: 100M ChatGPT Users & What It Means

• AI in 2026: Your Survival Guide to the Fourth Year of Generative AI

References

• Google Labs: Pomelli Official Access

• Google Blog: Official Pomelli Announcement

• Google DeepMind: Veo 3.1 Video Generation Model

On March 5, 2026, two things happened at the same time. GPT-5.4 launched. And Gemini 3.1 Pro, already sitting at the top of the Artificial Analysis Intelligence Index with a score of 57, refused to budge. No new model on top. Just a tie. For the first time in recent memory, OpenAI dropped a flagship model and it did not take the crown outright.

I have been running both models through real work over the past week, reading every independent benchmark I could find, and building a picture of what each model is actually good at. What I found surprised me. These two are not competing on the same dimension anymore.

GPT-5.4 is betting on computer use and professional document work. Gemini 3.1 Pro is betting on scientific reasoning and cost. And the gap between them on their respective strengths is bigger than most comparison articles are letting on.

Here is the full breakdown.

The March 2026 Frontier AI Landscape

March 2026 is the most competitive moment in AI history, and I do not say that loosely. Within a span of 14 days, OpenAI and Google each released their best model ever, and both of them are scoring identically on the most respected independent intelligence benchmark on the market.

Here is the quick context before you get into the numbers. Gemini 3.1 Pro launched on February 19 as Google DeepMind's strongest model yet, featuring a 2-million-token context window and a 94.3% score on GPQA Diamond, the graduate-level science reasoning benchmark. Two weeks later, GPT-5.4 arrived on March 5 with native computer use, an 83% GDPval knowledge work score, and the distinction of being the first AI model to exceed human expert performance on autonomous desktop tasks.

Both models now sit at 57 on the Artificial Analysis Intelligence Index out of 285 models evaluated. That tie is not a coincidence. It reflects how tight the frontier has become and, more practically, why picking the "best" model in 2026 requires asking "best for what" before you evaluate anything else.

I have read our own GPT-5.4 review and the data is clear: these models split categories instead of one dominating the other. Let me show you exactly how.

Benchmark Comparison: Full Data Table

These numbers are pulled from independent benchmark sources, Artificial Analysis, digitalapplied.com, and awesomeagents.ai, as of March 2026. I am not citing model cards. Model cards are marketing.

My honest read: Gemini wins on reasoning. GPT-5.4 wins on productivity and automation. On coding, they are basically identical unless you bring Claude Opus 4.6 into the comparison, at which point Opus at 80.8% SWE-Bench takes the coding crown.

Speaking of Opus, if you want the full three-way view, I covered that in our post on GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5.

GPT-5.4 vs Gemini 3.1 Pro: Reasoning and Science

Gemini 3.1 Pro is the stronger reasoning model. Full stop. Its 94.3% on GPQA Diamond is 1.5 points ahead of GPT-5.4's 92.8%, and on ARC-AGI-2, the abstract reasoning benchmark that measures genuine problem-solving rather than memorized patterns, Gemini leads 77.1% to 73.3%.

What does GPQA Diamond actually measure? It tests PhD-level biology, chemistry, and physics questions, questions that require specialist knowledge to answer correctly, not just pattern matching from training data. Gemini's lead here is meaningful.

GPT-5.4 Pro at the $30/$180 per million token tier closes the GPQA gap to 94.4%, which is marginally ahead of Gemini. But that is a completely different pricing conversation. At standard rates, Gemini reasons better and costs less.

My take: if your work involves scientific literature review, medical research, complex legal analysis, or anything requiring PhD-level knowledge synthesis, Gemini 3.1 Pro is the better tool at the standard tier. Do not let the marketing around GPT-5.4 obscure that.

Computer Use and Agentic Tasks: Where GPT-5.4 Wins

This is GPT-5.4's defining capability, and it has no real competition from Gemini at this point. GPT-5.4 scores 75.0% on OSWorld-Verified, making it the first AI model in history to exceed human expert performance on desktop computer use, where the human baseline sits at 72.4%.

What this means in practice: GPT-5.4 can click buttons, fill forms, navigate applications, draft emails with attachments, and complete multi-step workflows across software tools, entirely without browser plugins or special integrations. Gemini 3.1 Pro has no equivalent capability published at this level.

On Terminal-Bench 2.0, GPT-5.4 leads Gemini 75.1% to 68.5%, a 6.6-point gap that matters for developers running CLI-heavy workflows. GPT-5.4 also hits 83% on GDPval, which benchmarks performance across 44 professional occupations.

For teams replacing RPA tools, building desktop automation agents, or running workflows that interact with real software interfaces, this is the deciding factor regardless of how the reasoning benchmarks compare. The computer use story is one-sided right now.

GPT-5.4 ships in three variants. The base model handles general tasks. The Thinking variant adds extended chain-of-thought reasoning. The Pro variant runs parallel reasoning threads at $30/$180 per million tokens.

Coding Performance: SWE-Bench and Real Dev Tasks

On SWE-Bench Verified, the main coding benchmark, GPT-5.4 and Gemini 3.1 Pro are essentially tied at around 80.6%. If pure coding performance is your primary use case, neither model beats the other here.

The real story is that Claude Opus 4.6 at 80.8% SWE-Bench is still the marginal leader for pure software engineering precision. I noted this in our GPT-5.4 review: if you are building production code, do not make your decision based on this comparison alone.

Where GPT-5.4 differentiates in the coding context is Terminal-Bench 2.0 at 75.1% and spreadsheet modeling at 87.5% with native Excel and Google Sheets plugins. For financial analysis, business reporting, and developer workflows that blend code with business tools, GPT-5.4 is stronger.

Gemini 3.1 Pro's coding advantage is architectural. Its mixture-of-experts design and thinking-level controls are tuned for stable, high-precision outputs in long-running workflows. For codebases that exceed 200K tokens, Gemini's 2M context window means you can load entire repositories where GPT-5.4's standard 272K context cannot.

Pricing Breakdown: What You Actually Pay Per 1M Tokens

The pricing comparison is more nuanced than most articles make it sound, and getting it wrong can wildly distort your cost projections.

The headlines about Gemini being 15x cheaper are technically accurate but practically misleading. They compare GPT-5.4 Pro at $30/M to Gemini Standard at $2/M. Standard vs Standard, the actual gap is about 20%. That is real money at scale but not a different category.

Where Gemini genuinely wins on cost: the Batch API at $1.00/$6.00 and context caching at $0.20/M make high-volume, non-realtime workloads significantly cheaper than anything GPT-5.4 offers right now.

One important caveat on Gemini: it is still in Preview. GA is expected in Q2 2026. Developers have reported capacity issues and quota bugs during the preview period. For production workloads where reliability matters more than cost, GPT-5.4's GA status is a real advantage.

Context Window and Latency: The Numbers Nobody Talks About

GPT-5.4 standard ships with a 272K token context window. With the Codex and developer platform integrations, it scales to 1 million tokens. Gemini 3.1 Pro offers up to 2 million tokens natively.

For most tasks, 272K is enough. A full novel is around 150K tokens. A large codebase with a few hundred files sits around 200-400K. But if you are working with entire legal case files, multi-source research corpora, or large enterprise codebases, Gemini's 2M window is a genuine operational advantage.

On latency, here is the number that surprises people: Gemini 3.1 Pro has a 44.5-second Time to First Token. That is real. For real-time chat applications or anything requiring fast responses, that latency makes Gemini the wrong choice regardless of its benchmark scores. GPT-5.4 is significantly faster to first token.

This is something I also noticed in our Gemini 3.1 Flash Lite vs 2.5 Flash comparison: Google's Pro-tier models prioritize depth over speed. If latency is a product requirement, Gemini Flash variants are a better fit than Gemini Pro.

Multimodal Capabilities: Text, Images, Audio, and Video

Gemini 3.1 Pro is the only model in this comparison with true four-modality native support: text, image, audio, and video in a single model. GPT-5.4 handles text and images natively at the API level. It does not handle audio or video natively.

For most enterprise and developer workflows, this difference does not matter. The majority of production AI use cases involve text, documents, and code. But if your product involves video analysis, podcast transcription, or audio-alongside-text reasoning, Gemini wins this category without a real competitor.

On visual reasoning, MMMU Pro scores are roughly tied. Both models handle image-heavy workflows at comparable quality. GPT-5.4's native Excel and Google Sheets plugins make it stronger for visual document work in a business context. Gemini's video and audio capabilities make it stronger for media and research workflows.

Which Model Should You Choose? Use-Case Guide

There is no universal answer, and anyone claiming otherwise is not working with both models seriously. Here is my honest routing guide based on the data.

Choose GPT-5.4 if you need:

•        Desktop automation and RPA replacement (75% OSWorld, first to beat human baseline)

•        Professional knowledge work (83% GDPval across 44 occupations)

•        Terminal and CLI-heavy developer workflows (75.1% Terminal-Bench 2.0)

•        Spreadsheet modeling and financial analysis (87.5% with native Excel/Sheets plugins)

•        Production-ready GA stability with broad benchmark coverage

Choose Gemini 3.1 Pro if you need:

•        Scientific and graduate-level reasoning (94.3% GPQA Diamond)

•        Abstract problem-solving (77.1% ARC-AGI-2)

•        Massive context windows (up to 2M tokens for full codebase or legal document analysis)

•        Audio and video processing alongside text in a single model call

•        High-volume batch workloads where $1.00/$6.00 Batch API pricing matters)

The honest recommendation:

I use both. GPT-5.4 for document-heavy professional tasks and anything involving computer use or automation. Gemini 3.1 Pro for research synthesis, scientific analysis, and any workload where I am sending large context and want to keep costs down.

If you are building a product and want to understand how to structure your AI model stack, our Best ChatGPT Prompts guide for 2026 walks through practical prompting strategies that work across both models.

The contrariant point I want to make: the benchmark convergence happening at the frontier is the actual story of 2026. These three models, GPT-5.4, Gemini 3.1 Pro, and Claude Opus 4.6, are all within 2-3 percentage points of each other on most evaluations. At some point, pricing, developer experience, and reliability start mattering more than raw benchmark position. Build your stack around that reality, not around loyalty to a single provider.

10. Frequently Asked Questions

Is GPT-5.4 better than Gemini 3.1 Pro?

Neither model wins outright. GPT-5.4 leads on computer use (75% OSWorld), professional knowledge work (83% GDPval), and terminal tasks. Gemini 3.1 Pro leads on abstract reasoning (94.3% GPQA Diamond, 77.1% ARC-AGI-2) and costs about 20% less at standard rates. Both score identically at 57 on the Artificial Analysis Intelligence Index as of March 2026.

Which is cheaper, GPT-5.4 or Gemini 3.1 Pro?

Gemini 3.1 Pro is cheaper at standard rates: $2.00/$12.00 per 1M tokens versus GPT-5.4's $2.50/$15.00. For high-volume batch workloads, Gemini's Batch API at $1.00/$6.00 and context caching at $0.20/M make it significantly more cost-effective. The 15x cost gap cited in some articles compares GPT-5.4 Pro ($30/M) to Gemini Standard ($2/M), which is not a fair production comparison.

Is Gemini 3.1 Pro available for production use right now?

Gemini 3.1 Pro is currently in Preview status as of March 2026, with General Availability expected in Q2 2026. Developers have reported capacity issues and quota bugs during the preview period. GPT-5.4 launched as Generally Available on March 5, 2026, making it the more stable production choice right now.

What is GPT-5.4's context window?

GPT-5.4 standard ships with a 272K token context window. Through the Codex and developer platform integrations, it scales to 1 million tokens. Gemini 3.1 Pro offers up to 2 million tokens natively at $4.00/$18.00 per 1M for requests exceeding 200K tokens.

Can Gemini 3.1 Pro do computer use like GPT-5.4?

No, not at the same level. GPT-5.4 introduced native computer use scoring 75.0% on OSWorld-Verified, the first AI to exceed the human baseline of 72.4%. Gemini 3.1 Pro does not have a published equivalent computer use capability at this benchmark level as of March 2026.

Which AI model is best for coding in 2026?

For pure SWE-Bench performance, GPT-5.4 and Gemini 3.1 Pro are tied at approximately 80.6%. Claude Opus 4.6 marginally leads at 80.8% SWE-Bench Verified for production coding precision. For large codebase analysis that requires 200K-plus tokens of context, Gemini 3.1 Pro's 2M window is a practical advantage over GPT-5.4's standard 272K.

How much does GPT-5.4 cost per month for a developer?

GPT-5.4 is available via ChatGPT Plus, Team, and Pro subscriptions and via the OpenAI API at $2.50 per 1M input tokens and $15.00 per 1M output tokens (standard tier). In ChatGPT, select GPT-5.4 Thinking from the model picker on Plus, Team, or Pro plans. API access uses model ID gpt-5.4 or the pinned snapshot gpt-5.4-2026-03-05.

Is Gemini 3.1 Pro smarter than GPT-5.4?

By the independent Artificial Analysis Intelligence Index, both score identically at 57 out of 285 models evaluated. Gemini leads on scientific reasoning and abstract problem-solving. GPT-5.4 leads on computer use and professional knowledge work. Raw "smartness" is not a useful framing. The practical question is which model performs better on your specific task category.

Stay Updated

If this comparison helped, subscribe to Build Fast With AI for weekly breakdowns of the frontier model race, practical AI build guides, and the benchmark analysis nobody else is doing. New posts drop every week.

Internal References

•        GPT-5.4 Review: Features, Benchmarks & Access (2026)

•        GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5 (2026)

•        Gemini 3.1 Flash Lite vs 2.5 Flash: Speed, Cost & Benchmarks (2026)

•        Best ChatGPT Prompts in 2026: 200+ Prompts for Work, Writing, and Coding

References

•        Artificial Analysis Intelligence Index

•        LaoZhang AI: GPT-5.4 vs Gemini 3.1 Pro Developer Comparison

•        AwesomeAgents: GPT-5.4 vs Gemini 3.1 Pro Full Benchmark Analysis

Google just quietly made every other AI research tool look like a PowerPoint from 2014.

On March 4, 2026, NotebookLM launched Cinematic Video Overviews - a feature that takes your uploaded PDFs, notes, and documents and turns them into fully animated, narrated video explainers. Not slideshows. Not bullet points with voiceover. Actual cinematic videos, built by a three-model AI stack that includes Gemini 3, Nano Banana Pro, and Veo 3.

I've been watching AI tools try to crack the "notes-to-video" problem for two years. Most of them produce something that looks like a Canva template had a bad day. This one is different - and the reason why tells you a lot about where AI content creation is actually headed.

Here's everything you need to know: what it does, how it works, what it costs, and whether the $249.99/month price tag is remotely worth it.

What Is NotebookLM Cinematic Video Overview?

NotebookLM's Cinematic Video Overview is a feature that converts your uploaded source materials - PDFs, Google Docs, research papers, meeting notes, web articles - into short, fully animated video explainers, complete with narration, dynamic visuals, and a coherent narrative structure.

The feature uses a combination of advanced AI models, including Gemini 3, Nano Banana Pro, and Veo 3, to generate fluid animations and rich, detailed visuals designed to help you learn and engage with the topics you care about.

This is not a slideshow generator. What NotebookLM builds is closer to a short documentary about your research - structured like one, paced like one, and visually coherent like one.

I've seen demos of people uploading a single PDF about theoretical physics and getting back a beautifully animated explainer that makes entropy gravity actually comprehensible. The kind of video a YouTube science channel would spend a week producing manually. NotebookLM does it in minutes.

That's either exciting or slightly terrifying, depending on how you feel about where this is all going.

How It Works: The Three-Model AI Stack

Three Google AI models work in sequence to produce each video. Understanding the division of labor explains why the output quality jumped so dramatically from the old slideshows.

Gemini 3 - The Creative Director

Gemini now acts as a creative director, making hundreds of structural and stylistic decisions to best tell the story with your sources. It determines the best narrative, visual style, and format - and even refines its own work to ensure consistency before handing off to Veo.

This is the part that separates Cinematic Video Overviews from a simple "attach Veo to a document" approach. Gemini isn't just summarizing your notes - it's making editorial decisions about what to emphasize, what to cut, how to sequence ideas for maximum comprehension.

Nano Banana Pro - The Illustrator

Nano Banana Pro handles image generation, translating abstract concepts from your documents into AI-generated visual representations. If your notes mention a historical event or a scientific process, Nano Banana generates imagery to illustrate it - rather than pulling generic stock photos.

Want the full breakdown of what Nano Banana Pro can do? Read our comparison: Nano Banana vs Nano Banana Pro vs Nano Banana 2 — Which Google AI Image Model Wins?

Veo 3 - The Film Crew

Veo 3 synthesizes motion and animation from what Gemini and Nano Banana Pro have planned. The result is fluid video rather than static images with transitions - the visual difference between a YouTube explainer and a slideshow is almost entirely about motion, and this is what provides it.

The intent is not just to summarize but to teach. NotebookLM identifies the most instructive path through dense content, trims redundancy, and highlights conceptual pivots.

How to Generate a Cinematic Video in NotebookLM

The workflow is surprisingly simple, even if the technology behind it is anything but.

Step 1: Build Your Notebook

Add your sources - PDFs, Google Docs, web articles, transcripts, meeting notes. The more structured and source-specific your materials, the better the video output. Each source can contain up to 500,000 words or 200MB for uploaded files.

Step 2: Open the Studio Panel

Look for the video option in your notebook where Audio Overviews typically appear. Cinematic Video Overviews sit alongside the older Audio Overview and Video Overview buttons in the Studio panel.

Step 3: Prompt It (Optional But Powerful)

You don't need to write anything - one click works. But if you want something specific, prompt NotebookLM with goals like:

•        "Create a three-minute explainer for a non-technical audience"

•        "Compare the two approaches and highlight the trade-offs"

•        "Summarize this research paper for a sales team briefing"

The system responds to directional prompts well. The more specific your intent, the more useful the output.

Step 4: Wait, Then Review

Generation takes a few minutes. The output will be a short video - typically 2-5 minutes - that you can watch directly in NotebookLM or download. Note: Ultra subscribers can generate a maximum of 20 cinematic video overviews per day.

Cinematic vs Old Video Overviews: What Actually Changed?

NotebookLM had Video Overviews before this - launched at Google I/O in July 2025. The gap between the old version and the Cinematic version is substantial enough to treat them as different products.

The original Video Overviews worked more like structured slideshows - if the sources within your notebook included visuals, NotebookLM would pull them in alongside text snippets to build the video.

The Cinematic version doesn't pull visuals from your sources - it generates them. Your documents don't need images for the output to be visual. That's the core difference.

My honest take: the old Video Overviews were a nice-to-have. The Cinematic version is the kind of thing that makes you stop and rethink what "studying" or "briefing" actually looks like.

NotebookLM Pricing & Limits: Free, Pro, and Ultra Explained

This is where a lot of people hit a wall. Cinematic Video Overviews are exclusive to the $249.99/month Google AI Ultra plan - at launch, at least. Here's the full breakdown:

The free plan is genuinely useful for light research: 100 notebooks, 50 sources each, 50 chat queries and 3 audio generations per day. That's enough to explore whether NotebookLM fits your workflow before spending anything.

The Ultra price will make most people flinch - $250/month is a significant commitment. But it bundles in Gemini 3 Deep Think, Veo 3 video generation, Flow video editor, and 30TB of storage alongside the NotebookLM Ultra access. If you're a heavy user across Google's AI stack, the math changes.

For a broader look at the Gemini model stack powering this: Gemini 3.1 Flash Lite vs 2.5 Flash: Speed, Cost & Benchmarks (2026)

Who Should Actually Pay for This?

Not everyone. Let's be real about the use cases where this is a genuine multiplier versus where it's an expensive novelty.

The Cinematic Video Feature Makes Sense If You:

•        Create educational content and currently spend significant time producing explainer videos

•        Work in research or policy and need dense materials consumed by non-experts quickly

•        Run a team and spend hours converting internal documentation into shareable summaries

•        Build e-learning courses and need to produce visual overviews at scale

•        Work in sales enablement - converting product specs into short explainer videos for reps

It Probably Doesn't Make Sense If You:

•        Occasionally use NotebookLM for personal research (the free plan handles this fine)

•        Need video output in languages other than English (currently English only)

•        Are under 18 (the feature is restricted to users 18+)

•        Work with proprietary data subject to privacy policies that restrict cloud processing

The clearest ROI case: internal sales enablement video production is historically painful and expensive. If NotebookLM can produce a passable explainer from a product spec in minutes, the $250/month math becomes much more interesting.

Curious how this compares to what Anthropic is building? See our breakdown: What Is Claude Cowork? The 2026 Guide You Need

NotebookLM Limitations You Need to Know

Language lock-in (for now). Cinematic Video Overviews are available in English only at launch - for Google AI Ultra subscribers (18+) on web and mobile. If your primary research or audience is non-English, you're waiting for a future expansion.

No post-generation editing. There's limited ability to make adjustments after generating content assets. You can't edit a Cinematic Video after the initial generation step. If the structure or narrative doesn't match what you wanted, you regenerate from scratch - ideally with a more specific prompt.

No offline mode. Every action requires an active internet connection on every plan. NotebookLM is a cloud-only tool at every tier.

Your data goes to Google's servers. All documents are stored and processed on Google's infrastructure. Google says it does not train AI on your data, but your content still passes through their systems. For sensitive or confidential materials, this is a legitimate concern.

Only Gemini available. Google's Gemini is the only available AI model. You can't bring your own API keys, switch to OpenAI or Claude, or run local inference for privacy. That's a real constraint for teams with model preferences or compliance requirements.

Unclear rollout path. Based on how past NotebookLM features rolled out - Audio Overviews, Video Overviews, Deep Research - Cinematic Video will likely reach Pro users before free users, but Google hasn't confirmed a timeline.

Frequently Asked Questions

Can NotebookLM generate video?

Yes. NotebookLM now generates two types of video: the original Video Overviews (narrated slides with visuals pulled from your sources) and the new Cinematic Video Overviews (fully animated explainer videos powered by Gemini 3, Nano Banana Pro, and Veo 3). Cinematic Video Overviews are currently available only for Google AI Ultra subscribers at $249.99/month.

What is the Cinematic Video Overview feature in NotebookLM?

Cinematic Video Overview is a NotebookLM feature that transforms uploaded documents - PDFs, Google Docs, research papers, transcripts - into animated, story-driven video explainers. Unlike the older narrated slides format, Cinematic overviews generate original animations and dynamic visuals using Veo 3, with Gemini 3 acting as a creative director making hundreds of structural and stylistic decisions.

How do I generate a Cinematic Video Overview in NotebookLM?

Add your source documents to a NotebookLM notebook, then open the Studio panel and select the Video option. You can generate without a prompt (one-click) or add specific direction like "three-minute explainer for a non-technical audience." Generation takes a few minutes. You need a Google AI Ultra subscription to access Cinematic Video Overviews specifically.

What are the limits for NotebookLM video overviews?

Ultra subscribers can generate up to 200 Video Overviews per day and up to 20 Cinematic Video Overviews per day. Free plan users have limited access to the standard Video Overviews. Cinematic Video Overviews are not available on the free or Pro tiers as of March 2026.

What are the limitations of the free version of NotebookLM?

The free plan includes 100 notebooks, 50 sources per notebook, 50 chat queries per day, 3 audio overviews per day, and 10 Deep Research sessions per month. Cinematic Video Overviews are not included. Free users cannot remove watermarks from generated outputs, and there is no offline mode on any plan.

How much does NotebookLM cost?

NotebookLM has three tiers: Free (no cost, limited daily usage), Pro at $19.99/month bundled with Google AI Pro (500 queries/day, 300 sources/notebook), and Ultra at $249.99/month bundled with Google AI Ultra (5,000 queries/day, 600 sources/notebook, Cinematic Video Overviews, watermark removal, 30TB storage).

Does NotebookLM accept video as input?

Not directly. NotebookLM accepts Google Docs, Google Slides, Google Sheets, PDFs, .docx files, audio files (MP3, WAV, and 20+ formats), text files, images with OCR, and CSV files. You can upload a transcript from a video, but you cannot upload a video file itself as a source.

Will Cinematic Video Overviews come to free users?

Google hasn't confirmed a timeline. Based on how past NotebookLM features rolled out - Audio Overviews, then Video Overviews, then Deep Research - the pattern suggests Pro access before free access. For now, it's Ultra-only.

What This Actually Means for Content Creators

NotebookLM Cinematic Video Overviews is not going to replace professional video production for high-stakes content. The output is impressive for AI, but a skilled editor with source footage will still produce something more nuanced and contextually specific.

What it will replace is the enormous category of "video that was never made because it was too expensive and time-consuming." Lecture summaries. Policy briefings. Internal product explainers. Study aids. Sales enablement. The video backlog that every organization, researcher, and educator carries around in their head.

The feature doesn't compete with professional video studios. It competes with the blank space where a video should have been.

And that's a much bigger category than most people realize. Google is betting $250/month on it. That bet is probably right.

More From Build Fast With AI

If you found this useful, these posts from our blog will sharpen your understanding of the tools powering NotebookLM's Cinematic Video feature:

•        Nano Banana Pro vs Nano Banana 2 - Which Google AI Image Model Actually Wins?

Nano Banana Pro powers the image generation layer inside Cinematic Video Overviews. This breakdown tells you exactly what it can and can't do.

•        Gemini 3.1 Flash Lite vs 2.5 Flash - Speed, Cost & Benchmarks (2026)

Understanding where Gemini 3 sits in Google's model stack helps you make sense of what's powering NotebookLM's creative direction layer.

•        6 Biggest AI Releases This Week - February 2026 Roundup (includes Veo 3 + Nano Banana 2)

The week Veo 3 and Nano Banana 2 shipped - full context on what changed and why it matters for NotebookLM's video quality.

•        Claude Cowork: The 2026 Guide - What It Is and How to Use It

Comparing Google's NotebookLM ecosystem to Anthropic's Cowork? This is the companion read.

•        GPT-5.4 Review - Features, Benchmarks & Access (2026)

How does Google's AI Ultra stack measure up against OpenAI's flagship? Read this before committing to either subscription.

Reference Links

All external sources used in this article:

•        Google Blog: Cinematic Video Overviews Launch

•        NotebookLM Official — Google Workspace

•        Google AI Plans & Pricing — Google One

•        NotebookLM Upgrade Plans — Support Page

•        Gemini 3.1 Pro Announcement

•        NotebookLM Homepage

Anthropic just turned its AI model into a storefront. On March 6, 2026, the company launched Claude Marketplace, a curated enterprise platform where businesses can buy Claude-powered tools from third-party partners. And unlike OpenAI's GPT Store, this one is not for hobbyists or side-project builders. It's squarely targeting the Fortune 500.

I've been watching Anthropic's product moves closely, and this one is more calculated than it looks. Six partners at launch. No commission taken. Billing consolidated through Anthropic's existing spend commitments. On the surface, it's a procurement convenience tool. Underneath, it's a play to become the operating system of enterprise AI.

Here's everything you need to know.

What Is Claude Marketplace?

Claude Marketplace is an enterprise-only procurement platform launched by Anthropic on March 6, 2026, that allows businesses with existing Anthropic spend commitments to purchase Claude-powered tools from vetted third-party partners.

Think of it as the App Store, but for enterprise AI workflows built on Claude. You can't walk in off the street. You need an existing Anthropic contract. The six launch partners cover legal AI, financial analysis, software development, data operations, and no-code app building.

Anthropic described the goal simply: simplify procurement and consolidate AI spend. Instead of managing five separate contracts with five separate vendors, your company runs everything through one Anthropic invoice. One contract. One renewal conversation. One budget line.

Cox Automotive's Chief Product Officer Marianne Johnson put it bluntly: the Marketplace lets teams "move faster by extending our Anthropic investment into the partner tools we need, with simplified procurement."

That quote tells you everything. This is solving enterprise pain, not consumer want.

How Does Claude Marketplace Work?

The mechanics are straightforward: if your organization already has an annual Anthropic spend commitment, you can redirect a portion of it toward partner tools in the Marketplace without signing a new contract.

Anthropic handles all invoicing, including for third-party purchases. That means your finance team sees one vendor, not six. Partner purchases count against your existing Anthropic commitment rather than generating separate invoices.

The workflow looks like this:

•        Your company already pays Anthropic annually (the size of that commitment varies)

•        You browse Claude Marketplace and find a partner tool your team needs

•        You add that partner to your Anthropic account

•        Purchases come out of your committed Anthropic spend

•        Anthropic sends one consolidated invoice for everything

To get started, you reach out to your Anthropic account team directly. The Marketplace is currently in limited preview, so general access is not open yet.

I think the billing consolidation is genuinely useful for large enterprises. Procurement cycles at big companies can take months. Cutting that down to a phone call with your existing account rep is real value. Whether the limited partner catalog justifies that simplicity right now is a different question.

Who Are the Launch Partners?

Claude Marketplace launched with six partners on March 6, 2026: GitLab, Harvey, Lovable, Replit, Rogo, and Snowflake.

Each covers a different enterprise use case:

Snowflake and GitLab are the two publicly traded heavyweights here. Both already sell through AWS and Azure marketplaces, which signals something important: Anthropic is not building from scratch. It's recruiting companies with proven enterprise go-to-market motions.

The Snowflake partnership is particularly notable. Anthropic and Snowflake announced a $200 million multi-year partnership in early 2026, giving Claude access to Snowflake's 12,600 global customers. That's not a small distribution channel.

Claude Marketplace vs GPT Store vs AWS Marketplace vs GitHub Marketplace

Claude Marketplace is enterprise-first. The GPT Store is consumer-first. Those two sentences explain about 80% of the difference. But the specifics matter, so here's the full breakdown.

Claude Marketplace vs GPT Store

My honest read: GPT Store failed to generate the developer ecosystem buzz OpenAI hoped for. Claude Marketplace is doing something different by narrowing the audience to enterprise and removing the commission friction. Whether that's smarter or just smaller depends on execution.

Claude Marketplace vs AWS Marketplace

Claude Marketplace vs GitHub Marketplace

Who Can Use Claude Marketplace?

Right now, Claude Marketplace is available in limited preview exclusively to enterprise customers with an existing Anthropic spend commitment. Teams and individual plan users are not currently included.

To get access, you contact your Anthropic account team directly. There is no self-serve signup. This is intentional. Anthropic is vetting both customers and partners before opening the doors wider.

Partners wanting to join the Marketplace can apply through a waitlist on Anthropic's site. The criteria are focused on enterprise-grade security, scale, and compliance capabilities. If you're a startup building a Claude-powered tool and want distribution access to Anthropic's enterprise base, this is the channel to apply for.

General availability timing has not been confirmed. Anthropic has not announced when limited preview ends or when Teams plan users might get access.

Why Anthropic Is NOT Taking a Commission (And What That Really Means)

This is the part I find most interesting. Anthropic is handling all billing and invoicing for Marketplace purchases but is not taking a commission cut on transactions. That's unusual for a marketplace model.

AWS and Azure both take a percentage of marketplace transactions. Salesforce's AppExchange runs on revenue share. The App Store famously takes 30%. Anthropic is, at least at launch, leaving that revenue on the table.

Why? A few reasons worth thinking about:

•        The real revenue is in API token consumption. Every time a Harvey user runs a legal workflow, or a Rogo user generates a financial model, Claude processes those tokens. That's where Anthropic earns.

•        The commission waiver is a partner acquisition strategy. Lower friction for early partners means more tools in the catalog faster, which makes the Marketplace more useful, which keeps enterprise customers inside the Anthropic ecosystem.

•        It creates a direct contrast with OpenAI's GPT Store, which does take revenue share. Anthropic gets to position itself as the partner-friendly option.

Here's my contrarian take: the no-commission model is probably temporary. Once the partner catalog grows and the Marketplace proves commercial traction, a revenue share arrangement becomes the logical next step. This is how cloud marketplaces evolved. AWS didn't charge commissions on day one either.

The Vendor Lock-In Problem Nobody Is Talking About

I want to be direct about something the marketing language glosses over. Claude Marketplace is a lock-in mechanism. A clever, genuinely useful one, but a lock-in mechanism nonetheless.

Here's how it works in practice. Your company commits to Anthropic spending. You start running Harvey for legal work, GitLab for development, and Rogo for finance, all billed through Anthropic. Your workflows get built around these tools. Your teams get trained on them. Your data gets organized around them.

Now try switching to a different foundation model provider. You'd need to renegotiate with Harvey, GitLab, and Rogo individually. Your consolidated billing disappears. Your procurement simplification evaporates. The switching cost is no longer just "change our model API." It's rebuild your entire enterprise AI stack.

Pareekh Jain from Pareekh Consulting said it clearly: "Anthropic is trying to deepen switching costs. Once an enterprise has committed to Anthropic spend and multiple partner tools running through Claude, migrating to another model becomes operationally difficult."

Is this bad? Not necessarily. Every major platform does this. But enterprises signing multi-year Anthropic commitments in 2026 should go in with eyes open. The convenience is real. So is the dependency.

FAQ: Claude Marketplace

What is Claude Marketplace?

Claude Marketplace is an enterprise procurement platform launched by Anthropic on March 6, 2026. It allows businesses with existing Anthropic spend commitments to purchase Claude-powered tools from vetted third-party partners including GitLab, Harvey, Lovable, Replit, Rogo, and Snowflake.

How does Claude Marketplace work?

Organizations with an existing Anthropic spend commitment can apply a portion of that commitment toward partner tools in the Marketplace. Anthropic manages all invoicing, including for third-party products, so enterprises deal with one invoice and one contract. To get started, you contact your Anthropic account team directly.

Who are the launch partners of Claude Marketplace?

The six launch partners announced on March 6, 2026, are GitLab (software development lifecycle), Harvey (legal AI workflows), Lovable (no-code app development), Replit (developer platform), Rogo (financial analysis), and Snowflake (enterprise data operations).

Is Claude Marketplace available to everyone?

No. As of March 2026, Claude Marketplace is in limited preview and available only to enterprise customers with an existing Anthropic spend commitment. Team and individual plan users are not currently included. General availability has not been announced.

Is Claude Marketplace free?

The Marketplace itself has no separate access fee, but using partner tools costs money. Partner purchases count against a portion of your existing Anthropic commitment. Anthropic has stated it is not taking a commission on partner transactions at launch.

How is Claude Marketplace different from the GPT Store?

Claude Marketplace is enterprise-focused, requiring an existing Anthropic spend commitment to access. The GPT Store targets consumers and small creators, accepts user-created GPTs with minimal vetting, and operates on a revenue-share model. Claude Marketplace has only 6 vetted partners at launch versus thousands of GPTs in the GPT Store.

Can developers and startups join Claude Marketplace?

Yes, via a partner waitlist on Anthropic's site. Anthropic says it's looking for companies building Claude-powered products designed for enterprise-grade security, scale, and compliance. Joining is application-based and not guaranteed.

What tools are available in Claude Marketplace?

At launch, tools span five enterprise categories: software development lifecycle (GitLab), legal AI workflows (Harvey), no-code app creation (Lovable), developer production environments (Replit), financial modeling and research (Rogo), and enterprise data analytics (Snowflake).

When was Claude Marketplace launched?

Anthropic announced and launched Claude Marketplace on March 6, 2026, via a post on X. The platform launched in limited preview. Anthropic CEO Dario Amodei was not publicly involved in the announcement, which came from Anthropic's main account.

Related Articles

1. What Is Claude Cowork? The 2026 Guide You Need

2. Claude Cowork Complete Guide 2026: AI Work Automation, Use Cases & Best Practices

3. MCP: The Model Context Protocol Transforming AI Integration

4. MCP (Model Context Protocol) Simplified

5. GPT-5.3-Codex vs Claude Opus 4.6 vs Kimi K2.5 (2026)

6. Claude Can Do Your Work Now

7. Cheap Claude Alternative for AI Agents: 8x Less Cost, Same Results

8. How We Built a Website, Game, and SaaS App in Under 10 Minutes Using AI

Reference

1. Anthropic Claude Marketplace Official Page https://claude.com/platform/marketplace

2. Snowflake x Anthropic Strategic Partnership Announcement
   https://www.anthropic.com/news/snowflake-anthropic-expanded-partnership
   

I opened LinkedIn on the morning of February 18, 2026, and half my feed was celebrating Sarvam AI like it had just won a World Cup. An Indian startup - bootstrapped on $50 million and built in Bengaluru - had just dropped two open-source LLMs: Sarvam-30B and Sarvam-105B. The 105B model, trained from scratch, clocks 98.6 on Math500 and wins 90% of pairwise comparisons in Indian language benchmarks.

That number stopped me cold. A 105-billion-parameter model from an Indian startup outperforming DeepSeek-R1 on certain benchmarks - a model that has 671 billion parameters - is not something you expect to read on a Tuesday morning.

But here's the thing: I've seen Indian AI hype before. Sarvam itself got roasted in 2025 for releasing Sarvam-M, which was basically Mistral Small with Indian fine-tuning. Critics called it a foreign model wearing a desi kurta. So this time, I wanted to actually dig into what Sarvam-105B is, what the benchmarks actually mean, and whether this is genuinely India's sovereign AI moment - or just another well-timed announcement.

What Is Sarvam-105B?

Sarvam-105B is India's first fully domestically-trained, open-source large language model at 105 billion parameters, built by Bengaluru-based startup Sarvam AI and released in February 2026.

That sentence matters more than it sounds. The word 'domestically-trained' is doing a lot of work here. Unlike Sarvam-M - the company's earlier model from May 2025 that was fine-tuned from Mistral Small, a French model - Sarvam-105B was trained from scratch. That's the distinction that makes critics sit up and take notice.

The model was released under the Apache 2.0 license, meaning startups, researchers, and enterprises can download, deploy, and modify it commercially without paying licensing fees. Weights are available on Hugging Face (sarvamai/sarvam-105b) and AI Kosh.

Sarvam AI was selected by the IndiaAI Mission to build India's sovereign LLM ecosystem - a government-backed initiative funded with INR 10,372 crore ($1.1 billion). This release is the first major public deliverable of that mandate.

My take: The 'sovereign AI' label carries real weight for government procurement and strategic deployments. For pure developers? The Apache license and open weights matter more than the patriotism angle.

Architecture: Why MoE Changes Everything

Sarvam-105B uses a Mixture-of-Experts (MoE) architecture, which means it has 105 billion total parameters but only activates approximately 10.3 billion parameters per token during inference. That's the efficiency play that makes this model viable at scale.

Think of it like a hospital with 100 specialists. You don't consult all 100 doctors for a headache - you route to the right expert. MoE works the same way. For each task, the model dynamically routes to the most relevant subset of its network.

This matters for cost. A full 105B dense model would require enormous GPU infrastructure for every inference call. Because only ~10% of parameters activate per token, Sarvam-105B can serve far more requests at lower compute cost compared to a traditional model of the same parameter count.

Key Technical Specifications

•        105B total parameters, ~10.3B active per token (MoE architecture)

•        128K token context window - handles long documents and multi-turn research sessions

•        MLA-style attention stack with decoupled QK head dimensions (q_head_dim=192 split into RoPE and noPE components)

•        v_head_dim=128, head_dim=576 - enabling high representational bandwidth per attention head

•        Hidden size: 4096

•        Sigmoid-based routing scores for expert gating (instead of traditional softmax - reduces routing collapse during training)

•        Trained on 12 trillion tokens across code, web data, math, and multilingual corpora

•        Pre-training in three phases: long-horizon pre-training, mid-training, and long-context extension

The 128K context window is one feature I keep coming back to. Most Indian enterprise use cases - legal document review, government policy analysis, multilingual customer support logs - involve long documents. GPT-4 in its early forms capped at 8K tokens. Sarvam-105B handles 16x that natively.

Sarvam-105B Benchmark Results (Real Numbers)

Sarvam-105B consistently matches or surpasses several closed-source frontier models and stays within a narrow margin of the largest global systems on diverse reasoning and agentic benchmarks. Here are the published numbers:

The Math500 score of 98.6 is genuinely impressive for any model, let alone a 105B parameter system. The AIME 25 score reaching 96.7 with tool use puts it ahead of most open models in its class.

The BrowseComp score of 49.5 and Tau2 average of 68.3 - both highest among compared models - signal strong agentic capability. These aren't just Q&A benchmarks. Tau2 measures the model's ability to complete real-world multi-step workflows, which is increasingly how enterprise customers actually use LLMs.

Contrarian point worth making: benchmark scores are not the same as real-world performance. The Hacker News thread on this release includes reports of hallucination issues and a knowledge cutoff of June 2025 - meaning the model has no awareness of events in the second half of 2025 or 2026. For live business intelligence use cases, that's a limitation worth flagging.

Indian Language Performance: The 90% Win Rate Explained

Sarvam-105B wins 90% of pairwise comparisons across Indian language benchmarks and 84% on STEM, math, and coding tasks - making it the highest-performing open model for Indian languages at its parameter class as of March 2026.

The benchmark Sarvam designed for this evaluation is worth understanding. It covers 22 official Indian languages, evaluates both native script (formal written usage) and romanized script (Hinglish and colloquial text messaging style), and spans four domains: general chat, STEM, mathematics, and coding. The source prompts were 110 English questions translated into all 22 languages.

Why this matters: most Indian users don't type in pure Hindi or pure Tamil. They code-switch. A customer service message might start in English, switch to Hinglish halfway through, and include a technical term in Telugu script. GPT-4o and Llama 70B consistently stumble on these mixed inputs. Sarvam-105B was explicitly trained on native script, romanized, and code-mixed inputs for the 10 most-spoken Indian languages.

India has 1.4 billion people and 22 official languages. Less than 12% of the population communicates primarily in English. The implication is straightforward: most of the next billion AI users will need a model that understands them - not just translates for them.

I find the 90% win rate credible for the 22-language scope, but I'd want independent third-party evals before deploying this in a production system. Sarvam designed and ran their own benchmark, which is fine as a starting point - it's not fine as the only data point you rely on.

Sarvam-105B vs Sarvam-30B vs Sarvam-M: Which Model Do You Need?

Three models, three very different use profiles. Here's the breakdown:

Sarvam-30B is the one I'd actually recommend for most Indian startups right now. The 32K context window handles most real-world conversational use cases, and the lower GPU requirements make it deployable on more accessible infrastructure. It was also trained on 16 trillion tokens - more than the 105B model - which Sarvam says optimizes it for conversational quality and latency.

Sarvam-105B is for complex, multi-step, document-heavy, or agentic workflows - the tasks where you need 128K context and the highest possible reasoning quality. Government deployments, legal document analysis, complex enterprise automation. If you're building a basic chatbot, 105B is overkill.

Sarvam-M (24B) is effectively the legacy option. It was a meaningful milestone when it launched in May 2025 - the first model to demonstrate that a lean Indian team could compete on reasoning benchmarks - but the criticism about its Mistral Small foundation was fair. Both 30B and 105B supersede it.

How to Download and Use Sarvam-105B

The model is fully open-source and accessible through multiple channels. Here's exactly where to go:

•        Hugging Face: sarvamai/sarvam-105b - model weights, documentation, and vLLM inference examples

•        AI Kosh: Government-backed AI repository with direct download links for both 30B and 105B

•        Sarvam API: Cloud inference via the Sarvam API dashboard - no self-hosting required for testing

•        Indus App: Consumer-facing chat interface where you can try the model immediately

Minimum Hardware Requirements for Self-Hosting

Because of the MoE architecture, inference is more efficient than a dense 105B model, but self-hosting still requires serious hardware. The Hugging Face page uses tensor_parallel_size=8, which implies a minimum of 8 GPUs for efficient inference. Sarvam recommends high-end GPUs or distributed inference setups. For most Indian startups and individual developers, API access is the practical path.

Quick start with vLLM (from the Hugging Face page): load using AutoTokenizer and LLM from the vllm library, set tensor_parallel_size to match your GPU count, apply the chat template with enable_thinking=True for reasoning mode, and generate with standard SamplingParams. The documentation is solid - this is not a model you'll spend three days trying to get running.

Real-World Use Cases: Where Sarvam-105B Actually Shines

Benchmark numbers are one thing. Here's where Sarvam-105B has a genuine, practical advantage over global alternatives:

1. Government Services and Citizen Connect

India's government serves 1.4 billion people across 22 official languages. The IndiaAI Mission's flagship use cases - 2047: Citizen Connect and AI4Pragati - are specifically designed to deliver public services through conversational AI in regional languages. A citizen in rural Tamil Nadu asking about MNREGA eligibility in Tamil, or a farmer in Gujarat checking crop insurance details in Gujarati, needs a model that actually understands their language without forcing them into English.

Sarvam-105B's 128K context window and 22-language coverage make it structurally suited for document-heavy government deployments in a way that Llama 70B or GPT-4o - despite their overall capability - simply aren't optimized for.

2. Enterprise Multilingual Customer Support

India's top consumer companies - telecom, banking, e-commerce - serve hundreds of millions of customers across linguistic divides. Current solutions rely on a patchwork of rule-based systems, English-first chatbots, and human agents for regional language escalations. A model that handles Hindi, Tamil, Kannada, Bengali, and Hinglish in a single deployment changes that calculus entirely.

The 90% Indian language win rate and explicit training on code-mixed inputs directly addresses this use case. A customer typing 'mera account block ho gaya hai' (my account has been blocked) in romanized Hindi gets handled natively - no translation layer, no context loss.

3. Education Technology

India has 250 million school students, and the majority of them study in regional medium schools. An AI tutor that explains calculus in Marathi or answers science questions in Odia has a fundamentally different impact than an English-only assistant. Sarvam-105B's strong STEM benchmark scores (84% win rate on STEM, math, and coding in Indian languages) make it genuinely applicable for this use case.

4. Legal and Document Intelligence

India's courts process millions of documents annually in multiple languages, often with mixed-script formats. The 128K context window allows the model to ingest entire legal documents, contracts, and policy briefs in a single inference call -something the Sarvam Vision model (their 3B document intelligence model) can then complement with visual understanding of scanned PDFs.

The Honest Verdict: Strengths, Gaps, and What's Next

I want to be clear about what Sarvam-105B is and isn't, because the hype on both sides of this conversation is unhelpful.

What Sarvam-105B Gets Right

•        First Indian LLM trained from scratch at frontier scale - the sovereign AI argument is now legitimate

•        Best-in-class Indian language performance across 22 languages, including code-mixed formats

•        MoE architecture delivers 105B-level capability at ~10B active parameter efficiency

•        Apache 2.0 license removes the commercial deployment friction that kills most enterprise pilots

•        128K context window is practically essential for Indian enterprise and government use cases

What It Doesn't Yet Do

•        Does not match the scale of GPT-4o, Claude Opus, or Gemini Ultra - Sarvam themselves acknowledge this gap

•        Knowledge cutoff of June 2025 means the model has no awareness of recent events without RAG implementation

•        Self-hosting requires 8+ high-end GPUs - not accessible for most Indian developers without cloud support

•        Early community reports note hallucination tendencies that need further post-training work

•        Model lineup (30B, 105B) still lacks a sub-7B variant for edge and mobile deployment

My honest view: Sarvam-105B is a real technical achievement that deserves serious recognition. It is India's most credible foundational LLM as of 2026. It is not yet a replacement for frontier global models in general-purpose tasks. It is a genuinely superior choice for Indian language use cases, government deployments, and organizations that need open-source flexibility without foreign model dependencies.

The fact that Sarvam pulled this off on $50 million - compared to the billions OpenAI and Anthropic have raised - is the part that should make Silicon Valley take notice. Not because the model is bigger, but because it proves frugal engineering with sovereign intent can produce competitive results at scale.

FAQ: Sarvam-105B - Questions People Actually Ask

What is Sarvam-105B?

Sarvam-105B is a 105-billion-parameter open-source large language model developed by Sarvam AI, an Indian startup based in Bengaluru. Released in February 2026, it was trained from scratch under the IndiaAI Mission and supports all 22 official Indian languages. It is available under the Apache 2.0 license on Hugging Face (sarvamai/sarvam-105b) and AI Kosh.

How does Sarvam-105B perform on benchmarks compared to other models?

Sarvam-105B scores 98.6 on Math500, 88.3 on AIME 25 (96.7 with tools), and 85.8 on HMMT. It wins 90% of pairwise comparisons in Indian language benchmarks and 84% in STEM, math, and coding tasks. On certain agentic benchmarks, it outperforms DeepSeek-R1, which has 671 billion parameters - a model more than six times larger.

What makes Sarvam-105B different from previous Indian AI models like Sarvam-M?

Sarvam-M, released in May 2025, was fine-tuned from Mistral Small - a French model - with Indian language datasets. Sarvam-105B was trained entirely from scratch on 12 trillion tokens, making it India's first sovereign foundational LLM at this scale. The distinction matters for strategic and regulatory deployments where dependency on foreign model architectures is a concern.

Can I download and use Sarvam-105B for free?

Yes. Sarvam-105B is released under the Apache 2.0 open-source license, allowing free download, commercial deployment, and modification. Weights are available on Hugging Face (sarvamai/sarvam-105b) and AI Kosh. Sarvam also provides cloud API access through their API dashboard for teams who prefer not to self-host.

What hardware do I need to run Sarvam-105B locally?

Self-hosting Sarvam-105B requires significant GPU infrastructure - the official documentation recommends tensor_parallel_size=8, indicating a minimum of 8 high-end GPUs for efficient inference. Because of its Mixture-of-Experts architecture, only approximately 10.3 billion parameters are active per token, reducing compute requirements compared to a dense 105B model. For most developers, the Sarvam API or Indus app are the practical access points.

How many Indian languages does Sarvam-105B support?

Sarvam-105B supports all 22 scheduled Indian languages. It was trained on native script, romanized Latin script, and code-mixed inputs (like Hinglish) for the 10 most-spoken Indian languages, making it one of the few models to handle colloquial multilingual usage rather than just formal script translations.

Is Sarvam-105B better than GPT-4o for Indian language tasks?

For Indian language tasks specifically, Sarvam-105B outperforms GPT-4o, Gemini 3, and Llama 70B in head-to-head comparisons according to Sarvam's benchmarks, winning 90% of pairwise comparisons. For general-purpose global tasks or tasks requiring up-to-date knowledge beyond June 2025, frontier models like GPT-4o and Claude remain significantly more capable due to scale, training data recency, and tooling maturity.

What is the Sarvam-105B context window?

Sarvam-105B supports a 128,000-token context window. This makes it suitable for processing long documents, extended multi-turn conversations, and complex agentic workflows in a single inference session. The companion Sarvam-30B model has a 32,000-token context window, optimized for lower-latency conversational applications.

Related articles

1. https://www.buildfastwithai.com/blogs/best-chatgpt-prompts-in-2026-200-prompts-for-work-writing-and-coding

2. https://www.buildfastwithai.com/blogs/build-websites-with-ai-in-10-minutes

3. https://www.buildfastwithai.com/blogs/vibe-coding-google-ai-studio-build-ai-apps-minutes

4. https://www.buildfastwithai.com/blogs/top-11-ai-powered-developer-tools

5. https://www.buildfastwithai.com/blogs/what-is-generative-ai

6. https://www.buildfastwithai.com/blogs/what-is-transformer

7. https://www.buildfastwithai.com/blogs/how-to-make-your-own-ai-software-engineer-like-devin

8. https://www.buildfastwithai.com/blogs/what-is-gptcache

References

•        Sarvam AI Official Blog - Open-Sourcing Sarvam 30B and 105B (sarvam.ai)

•        Hugging Face Model Card - sarvamai/sarvam-105b (huggingface.co)

•        Business Standard Coverage - Sarvam Launches India's First Sovereign LLMs (business-standard.com)

I woke up on March 5, 2026 to a notification I’d been half-expecting for weeks: OpenAI just dropped GPT-5.4. And this time, it’s not a minor patch. It’s the most significant capability jump since GPT-5 launched last August - and it’s already reshaping how I think about the frontier model race.

Native computer use. 1 million token context. 83% match with human professionals across 44 occupations. GPT-5.4 is genuinely different from what came before it. But “different” doesn’t automatically mean “better for you.”

I’ve spent the last two days going through every benchmark, benchmark caveat, pricing table, and real-world test I could find. Here’s the complete picture- including where GPT-5.4 actually loses to Claude Opus 4.6 and Gemini 3.1 Pro.

1. What Is GPT-5.4?

GPT-5.4 is OpenAI’s most capable and efficient frontier model for professional work, released on March 5, 2026. It ships across ChatGPT, the API, and Codex simultaneously - the first time OpenAI has done a unified triple release.

The “5.4” version number signals something specific: this is the first mainline reasoning model that incorporates the coding capabilities of GPT-5.3-Codex. OpenAI is effectively merging its general and coding model lines into one system, simplifying the choice for developers.

There are three versions you need to know about:

•        GPT-5.4 Thinking - the standard tier, available to Plus, Team, and Pro users. Replaces GPT-5.2 Thinking.

•        GPT-5.4 Pro - maximum performance mode, available to Pro and Enterprise plans.

•        GPT-5.4 (API / Codex) - the developer-facing version with the full 1M token context window and native computer-use capabilities.

GPT-5.2 Thinking is being retired June 5, 2026, but stays in the model picker under Legacy Models until then. If you’re on Enterprise or Edu plans, you can enable GPT-5.4 early via admin settings.

2. GPT-5.4 Key Features Breakdown

Native Computer Use

This is the headline feature. GPT-5.4 is OpenAI’s first general-purpose model with built-in computer-use capabilities - meaning it can interact directly with software through screenshots, mouse commands, and keyboard inputs. No plugin required, no wrapper needed.

On the OSWorld-Verified benchmark, it scores 75.0% - which surpasses the human expert baseline of 72.4%. That’s not a rounding error. That’s the first frontier model to beat humans at autonomous desktop task completion. I think that deserves more attention than it’s getting.

1 Million Token Context Window

The API and Codex versions support up to 1 million tokens of context - OpenAI’s largest ever. The exact breakdown is 922K input and 128K output tokens.

One thing to flag: prompts over 272K input tokens get charged at 2x input and 1.5x output pricing for the full session. Budget accordingly if you’re processing massive documents.

Tool Search

OpenAI reworked how the API version handles tool calling. The new “Tool Search” system helps agents find and use the right tools more efficiently without sacrificing intelligence. In internal testing, it reduced token usage by 47% on tool-heavy workflows.

Hallucination Reduction

Individual claims from GPT-5.4 are 33% less likely to be false compared to GPT-5.2, and full responses are 18% less likely to contain any errors. That’s significant. Hallucinations are the #1 reason enterprise teams avoid deploying AI in production, and OpenAI has been chipping away at this systematically.

Token Efficiency

GPT-5.4 is OpenAI’s most token-efficient reasoning model yet - using significantly fewer tokens to solve problems than GPT-5.2. Faster outputs and lower API costs in the same call. For developers running high-volume agent workflows, this matters more than almost any benchmark number.

Upfront Thinking Plans (GPT-5.4 Thinking)

In ChatGPT, GPT-5.4 Thinking can now show you its plan before diving into execution - so you can redirect it mid-response. Anyone who’s burned 30 minutes waiting for a long AI output only to get the wrong thing will understand why this is worth celebrating.

3. GPT-5.4 Benchmarks: The Full Data

Here’s every major benchmark result I could verify from official sources and independent testing as of March 7, 2026.

Sources: OpenAI official launch blog (March 5, 2026), evolink.ai benchmark comparison, digitalapplied.com three-way comparison, Artificial Analysis Intelligence Index. Benchmarks are vendor-reported unless noted.

The GDPval score is the one I keep coming back to. 83% on a test spanning 44 professions - including law, finance, and medicine. That’s not “pretty good for AI.” That’s matching or beating industry professionals. On the BigLaw Bench specifically, GPT-5.4 scored 91% - which is genuinely useful for legal document analysis, not just demo-ware.

4. GPT-5.4 vs Claude Opus 4.6 vs Gemini 3.1 Pro

No single model wins this race outright. Each one dominates a specific category - and the best teams are routing intelligently between all three rather than picking one and locking in forever.

My honest take: if you’re doing professional knowledge work - document analysis, presentations, financial modeling, legal drafting - GPT-5.4 is the new default. But Anthropic isn’t sleeping. Claude Opus 4.6 still leads on coding precision and web research. Gemini 3.1 Pro is the value play that no one’s talking about enough: near-identical intelligence scores at 7.5x lower cost than Opus.

The contrariant point I’ll make: benchmark convergence at the frontier might be the actual story of 2026. GPT-5.4, Opus 4.6, and Gemini 3.1 Pro are all scoring within 2-3 percentage points of each other on most evals. At some point, pricing and developer experience start to matter more than raw performance.

5. GPT-5.4 Pricing & API Access

GPT-5.4 is listed on OpenRouter at $2.50 per 1M input tokens and $20.00 per 1M output tokens, with cached input at $0.625 per 1M tokens. OpenAI direct billing can differ by account tier and contract.

For prompts over 272K input tokens, you’re charged 2x input and 1.5x output for the entire session. Regional processing endpoints add a 10% cost uplift.

6. How to Access GPT-5.4 (Step by Step)

In ChatGPT:

•        Step 1: Log into your ChatGPT account at chat.openai.com

•        Step 2: Click the model selector dropdown at the top of the chat window

•        Step 3: Select “GPT-5.4 Thinking” from the model list (requires Plus, Team, or Pro)

•        Step 4: For Enterprise/Edu, go to Admin Settings and enable early access

In the API:

•        Use model ID: gpt-5.4 or pinned snapshot gpt-5.4-2026-03-05

•        API endpoint: standard /v1/chat/completions or the new Responses API

•        Supports reasoning_effort parameter: none, low, medium, high, xhigh

•        Tool Search is available via the Responses API - enable it in your tool configuration

In Codex:

•        GPT-5.4 is now the default model in Codex, replacing GPT-5.3-Codex

•        Computer use capabilities are natively available in the Codex environment

•        Context compaction for long-horizon agentic coding sessions is supported

7. Is GPT-5.4 Free?

No, GPT-5.4 is not available on the ChatGPT free tier. Access requires a paid ChatGPT subscription (Plus at $20/month is the minimum) or direct API usage.

GPT-5.2 Thinking - the model GPT-5.4 is replacing - will remain available for paid users under Legacy Models until June 5, 2026, when it will be permanently retired.

If you’re a developer and want to test GPT-5.4 without a ChatGPT subscription, you can access it directly via the OpenAI API at $2.50/1M input tokens, or through aggregators like OpenRouter which listed it on launch day at identical pricing.

8. GPT-5.4 vs GPT-5.3 Codex: What Actually Changed?

This is the comparison that matters for developers. GPT-5.4 absorbs GPT-5.3-Codex - so is Codex dead? Not quite.

OpenAI explicitly states the jump from 5.3 to 5.4 reflects the integration of Codex capabilities - which is why the version number skipped 5.3 in the main model line. GPT-5.3-Codex stays available for teams doing terminal-heavy development where raw execution speed still beats general capability.

9. My Honest Take: Who Should Actually Switch?

Switch immediately if you’re doing professional knowledge work - legal, finance, document-heavy analysis, or anything involving Excel/PowerPoint workflows. The GDPval score and BigLaw Bench results aren’t marketing. They represent real, measurable improvements on tasks that cost companies actual money.

Wait for independent evals if you’re a developer who just needs a reliable coding model. Claude Opus 4.6 still leads on SWE-Bench precision. Gemini 3.1 Pro still dominates on cost. GPT-5.4’s coding improvements are real, but the benchmark coverage from independent sources is still catching up to the launch-day claims.

Use model routing, not model loyalty. I’ll say this plainly: in March 2026, committing to a single AI model is like committing to a single SaaS tool for every business function. The right approach is GPT-5.4 for professional tasks, Gemini 3.1 Pro for high-volume cost-sensitive queries, and Claude Opus 4.6 for production code and deep reasoning chains.

The OpenAI vs Anthropic vs Google race right now is genuinely the most competitive it’s ever been. Artificial Analysis ranks GPT-5.4 (xhigh) and Gemini 3.1 Pro Preview tied at 57 on their Intelligence Index - with Opus 4.6 just behind at 53. These are not different leagues of capability anymore. They are different tools for different jobs.

10. Frequently Asked Questions

What is GPT-5.4?

GPT-5.4 is OpenAI’s most capable frontier model, released March 5, 2026. It combines the coding capabilities of GPT-5.3-Codex with advanced reasoning and native computer-use abilities. It is available in ChatGPT (as GPT-5.4 Thinking), the API, and Codex simultaneously.

Is GPT-5.4 free?

No. GPT-5.4 requires a paid ChatGPT subscription (Plus, Team, Pro, or Enterprise). The minimum plan to access it is ChatGPT Plus at $20/month. API access is available at $2.50 per 1M input tokens and $20.00 per 1M output tokens.

How do I access GPT-5.4?

In ChatGPT, select GPT-5.4 Thinking from the model picker (requires Plus/Team/Pro). In the API, use the model ID gpt-5.4 or the pinned snapshot gpt-5.4-2026-03-05. Enterprise and Edu customers can enable early access through admin settings.

How do I switch to GPT-5.4 from GPT-5.2 Thinking?

The transition is automatic for Plus, Team, and Pro users - GPT-5.4 Thinking now appears in your model picker by default. GPT-5.2 Thinking remains available under Legacy Models until June 5, 2026, when it will be permanently retired.

Is GPT-5.4 better than Claude Opus 4.6?

It depends on the task. GPT-5.4 leads on knowledge work (83% GDPval), computer use (75% OSWorld), and professional document tasks. Claude Opus 4.6 leads on coding (80.8% SWE-Bench) and web research (84% BrowseComp). Neither model wins across all dimensions in March 2026.

Is GPT-5.4 better than Gemini 3.1 Pro?

GPT-5.4 leads on professional work tasks and computer use. Gemini 3.1 Pro leads on abstract reasoning (77.1% ARC-AGI-2 vs 73.3%) and science (94.3% GPQA Diamond vs 92.8%). Gemini 3.1 Pro is also significantly cheaper at $2/$12 per 1M tokens vs GPT-5.4’s $2.50/$20.

What is GPT-5.4’s context window?

The API and Codex versions of GPT-5.4 support up to 1.05 million tokens of context (922K input, 128K output). In ChatGPT, the context window for GPT-5.4 Thinking is unchanged from GPT-5.2 Thinking. Prompts exceeding 272K input tokens are billed at 2x input pricing.

What is GPT-5.4 Pro?

GPT-5.4 Pro is the maximum-performance variant of GPT-5.4, available to Pro and Enterprise plan users. It is optimized for the most demanding professional tasks. On ARC-AGI-2, GPT-5.4 Pro scores 83.3%, significantly higher than the standard tier’s 73.3%.

What is the GPT-5.4 API model ID?

The model IDs for GPT-5.4 are: gpt-5.4 (alias, always points to latest) and gpt-5.4-2026-03-05 (pinned snapshot for consistent behavior). OpenAI recommends pinning the snapshot in production deployments.

Will GPT-5.4 replace GPT-5.3-Codex?

GPT-5.4 is now the default in Codex and incorporates GPT-5.3-Codex’s coding capabilities. GPT-5.3-Codex remains available as a fallback, particularly for terminal-heavy workflows where it scores 77.3% on Terminal-Bench 2.0. Full deprecation timelines have not been announced.

Software stocks lost billions the day Anthropic launched this thing. ServiceNow dropped 23%. Salesforce fell 22%. Thomson Reuters cratered 31%. That should tell you everything about how seriously the market is taking Claude Cowork.

So what actually is it, and should you care?

I've spent time going through everything Anthropic has published, every hands-on review, and every enterprise announcement since the January 12, 2026 launch. Here is the straightforward breakdown that most articles are getting wrong.

What Is Claude Cowork, Really?

Claude Cowork is Anthropic's agentic AI desktop tool that does actual work on your files instead of just answering questions about them. Launched on January 12, 2026, it lives inside the Claude desktop app as its own tab, sitting right next to Chat and Code.

The simplest way I can put it: you give Claude access to a folder on your computer, describe what you want done, and it goes and does it. Reorganize your downloads folder. Pull expense data from a pile of screenshots into a spreadsheet. Draft a report from scattered notes. All without you manually copying and pasting anything.

Anthropic describes it as "Claude Code for the rest of your work." That framing matters. Claude Code turned out to be a general-purpose agent that developers were using for almost everything. Cowork strips out the terminal interface that scared non-developers away and wraps the same underlying technology in something anyone can use.

One important detail that most coverage missed: Cowork is not running Claude on your raw files. According to a technical analysis by developer Simon Willison, it uses Apple's VZVirtualMachine virtualization framework to boot a custom Linux environment. Your files get mounted into that sandbox. This means Claude literally cannot reach anything you have not explicitly handed it.

Quotable stat: Claude Cowork launched on January 12, 2026, initially limited to Claude Max subscribers paying $100 or $200 per month, then expanded to Pro users on January 16 and Team and Enterprise plans on January 23.

What Can Claude Cowork Actually Do?

Claude Cowork handles multi-step file tasks, document creation, research synthesis, and now connects to over a dozen enterprise software tools. Here is what that looks like in practice.

File and document tasks it handles out of the box:

•        Sort and rename files in a folder based on custom rules

•        Pull data from screenshots or PDFs into a formatted spreadsheet

•        Write first drafts of reports from your raw notes

•        Create and edit presentations and Word documents

•        Pass context between Cowork, Excel, and PowerPoint without restarting

Enterprise connectors available as of February 25, 2026:

•        Google Drive, Gmail, Google Calendar

•        DocuSign, LegalZoom

•        FactSet, MSCI, S&P, LSEG

•        Apollo, Clay, Outreach, SimilarWeb

•        WordPress, Harvey

Plugins cover these departments:

•        HR, Design, Engineering, Operations

•        Financial analysis, Investment banking, Equity research, Private equity, Wealth management

•        Marketing, Sales, Enterprise search, Productivity

Anthropic released 11 open-source plugins at the January 30, 2026 plugin launch. Organizations can also build their own private plugins using Plugin Create, one of the launch tools, and distribute them internally through private marketplaces connected to GitHub.

I find the plugin architecture genuinely interesting here. Scott White, Anthropic's head of enterprise product, put it well: the goal is for Cowork to feel like "a specialist for your company specifically, not just Claude for legal, but Cowork for legal at your company." That is a meaningfully different product vision than a generic chatbot.

How to Set Up Claude Cowork Step by Step

Setting up Claude Cowork takes under 10 minutes if you are on a paid Claude plan. Here is the exact process.

Step 1: Check your plan. Cowork requires a paid Claude subscription. As of March 2026, it is available in research preview on Pro, Max, Team, and Enterprise plans. Free accounts do not have access.

Step 2: Download the Claude desktop app. Go to claude.com/download. Cowork is available on both macOS and Windows (Windows support with full feature parity launched alongside the February 2026 enterprise update).

Step 3: Open the Cowork tab. Inside the desktop app, you will see three tabs: Chat, Code, and Cowork. Click Cowork.

Step 4: Grant folder access. Cowork asks you to select a folder on your computer. This is the only folder it can see. Claude cannot read or edit anything outside what you explicitly grant.

Step 5: Set your global instructions. This is a feature I think people sleep on. You can tell Claude your preferred tone, your role, your formatting preferences, and it applies that across every session. You can also set folder-specific instructions that activate when you are working in a particular directory.

Step 6: Connect any external tools. If you use Google Drive, Gmail, or any of the supported MCP connectors, you can link them from the connectors panel. Each connector only gets access when you enable it.

Step 7: Queue up your first task. Write a plain-English description of what you want done. You do not need to wait for one task to finish before starting another. You can queue tasks in parallel.

One thing worth knowing before you hand Claude a folder: it can take destructive actions if instructed to, including deleting files. Give it clear guidance upfront about anything you do not want touched.

Claude Cowork vs Claude Code: The Real Difference

Claude Cowork is Claude Code with a non-developer interface and a pre-configured file sandbox. The underlying AI is identical. But the practical differences matter depending on who you are.

The honest contrarian take: I think for power users, Claude Code is still more capable right now. It has been around longer, the community has built more tooling around it, and there are fewer guardrails between you and what you want to accomplish. Cowork is genuinely better for non-developers and for teams that need something they can deploy and explain to a 50-person department without a training session.

What Claude Code did for engineering teams in 2025, Anthropic is betting Cowork does for every other department in 2026. Kate Jensen, Anthropic's Head of Americas, said it directly: "Engineers think about Claude Code as a tool they just couldn't live without anymore. We expect every knowledge worker will feel that way about Cowork."

Claude Cowork Pricing and Plans

Claude Cowork is included in all paid Anthropic plans as a research preview, with no separate charge as of March 2026. Here is the breakdown.

Because Cowork is still in research preview, Anthropic has not announced a separate pricing tier for it. The current access is bundled with your existing plan.

For enterprise deployments, pricing becomes more complex once you factor in private plugin development and organizational admin controls. Direct enterprise contracts are handled through Anthropic's sales team at anthropic.com/contact-sales.

My honest read: the value proposition is currently strongest for Max subscribers who have access to all the enterprise connectors and can actually test the full feature set. Pro access is there, but the plugin ecosystem and connector integrations are more constrained at lower tiers.

Is Claude Cowork Safe for Work Documents?

Yes, Claude Cowork is designed with explicit access controls that prevent it from reading or modifying anything outside the folder you assign. But "designed with controls" and "risk-free" are not the same thing.

Here is what the safety architecture actually looks like:

•        File isolation. File isolation

Cowork runs inside a virtualized Linux environment using Apple's VZVirtualMachine. Your files are mounted into that container. Claude cannot reach outside that mount point.

•        Explicit permission model. Explicit permission model

You choose which folders it can see. You choose which connectors it can access. None of this is on by default.

•        Action confirmation. Action confirmation

Before taking significant actions, Cowork asks for your approval. You can steer or correct it mid-task.

•        Enterprise admin controls. Enterprise admin controls

Team and Enterprise accounts get organizational-level settings that control which connectors and plugins employees can access. Admins can run private plugin marketplaces connected to internal GitHub repositories.

What should still give you pause: Cowork can delete files if instructed to, and there is always a chance it misinterprets an instruction. Back up anything irreplaceable before pointing it at a folder.

For regulated industries, Anthropic's enterprise contracts include data handling terms that address compliance requirements. For sensitive financial or legal work, the FactSet, MSCI, LegalZoom, and Harvey integrations were specifically built with enterprise data governance in mind.

My Honest Take: What It Gets Right and Wrong

I have been watching Anthropic's product releases closely for a while. Cowork is genuinely impressive in one specific way: it solves the "last mile" problem that made Claude Code inaccessible to most people.

What it gets right:

•        The virtualization approach is smart. Sandboxing files into a Linux container is a real security architecture, not just a policy statement.

•        Global and folder instructions are underrated. Being able to encode how you work once and have it persist across sessions removes a major friction point.

•        The plugin marketplace model scales. Enterprises building their own mini-apps for specific workflows is a much more sustainable adoption path than hoping a general tool fits everyone.

What it gets wrong, or at least what is still missing:

•        The research preview label is doing a lot of work here. Multiple testers noted display bugs and rough edges. This is not a finished product yet.

•        Windows support only arrived in the latest update. Mac-first releases in 2026 still feel like a choice that cuts off a huge portion of enterprise users on day one.

•        The pricing transparency for Team and Enterprise is basically nonexistent right now. If you are evaluating this for a 500-person company, you are going to a sales call before you know what anything costs.

Anthropic's Head of Economics Peter McCrory acknowledged during the February 25, 2026 enterprise launch that the company has not yet seen widespread labor market displacement from Cowork. That is an honest thing to say. Whether that changes depends entirely on adoption speed.

Frequently Asked Questions

What is Claude Cowork?

Claude Cowork is Anthropic's agentic AI productivity tool that reads, creates, and edits files on your computer, connects to enterprise software like Google Drive and Gmail, and runs multi-step work tasks autonomously. It launched on January 12, 2026 as a research preview.

How is Claude Cowork different from regular Claude chat?

Regular Claude chat answers questions and generates text in a conversation window. Cowork actually accesses files you grant it, executes multi-step tasks in parallel, connects to external tools via MCP connectors, and completes work without you needing to manually copy outputs. It is closer to a virtual assistant than a chatbot.

Is Claude Cowork free?

No. As of March 2026, Cowork requires a paid Anthropic subscription. It is available in research preview on Pro (approximately $20/month), Max ($100 or $200/month), Team, and Enterprise plans. Free accounts do not have access.

What is the difference between Claude Cowork and Claude Code?

Both run on the same underlying AI. Claude Code is built for developers and runs in a terminal interface where you configure your own file access. Cowork is a graphical desktop tool pre-configured for non-developers, with plugin support and a simpler setup process. For technical power users, Claude Code is still more flexible.

What apps does Claude Cowork connect to?

As of February 25, 2026, Cowork connects to Google Drive, Gmail, Google Calendar, DocuSign, LegalZoom, FactSet, MSCI, S&P, LSEG, Apollo, Clay, Outreach, SimilarWeb, WordPress, and Harvey. Organizations on Team and Enterprise plans can also build private custom plugins.

Is Claude Cowork safe for sensitive business documents?

Cowork uses Apple's VZVirtualMachine virtualization to run a sandboxed Linux environment. It can only access folders you explicitly grant. It confirms significant actions before proceeding. That said, it can delete files if instructed to, so backing up important data before use is still smart. Enterprise plans include organizational admin controls for compliance use cases.

How do I set up Claude Cowork?

Download the Claude desktop app from claude.com/download, open the Cowork tab, select a folder you want Claude to access, set your global instructions, and optionally connect external tools like Google Drive or Gmail. The full setup takes under 10 minutes for most users.

Does Claude Cowork work on Windows?