Google interdit le codage, sa plus grande attaque contre les développeurs à ce jour : AntiGravity 2.0

On Tuesday, May 19th, thousands of developers opened their computers and found their code editors had basically vanished. Terminals gone, file explorer's gone, the actual ability to directly edit code just stripped out. What they got instead was a chat interface. Google had pushed an automatic update to anti-gravity overnight, and within hours, Reddit and Google's own developer forums were flooded with people saying their active projects were now unusable. One developer said it felt like non-technical people had just shipped code straight to production. Another called the whole thing a massive step backward. But here's the thing, this wasn't a bug. This was intentional. Google didn't just update a coding tool. They completely rewired it to force developers into something much bigger. And whether the developer community was ready for it or not, Google decided the transition was happening now. So, let's talk about what actually happened here. Because anti-gravity version 2 is not really an upgrade in the traditional sense. It's more like Google took a product that developers were already using and turned it into something fundamentally different. And in doing that, they might have just forced the entire software development world into the AI agent era, whether it wanted to go there or not. Anti-gravity started back in November 2025 as an AI powered code editor. That was the pitch. Google built it to compete with tools like cursor and it was basically one thing. You open it up, you write code, the AI helps you along the way. It did what you'd expect from that kind of tool. Fast forward to May 2026 and Google IO and suddenly anti-gravity is not a code editor anymore. It's a full platform. Version 2 now ships with five major components. There's a standalone desktop app, a new command line interface that's replacing the old Gemini CLI entirely, a developer SDK for building custom workflows, something called managed agents, which is basically an API layer for spinning up AI agents on demand, and then an enterprise deployment path through Google Cloud. That's not an update. That's a total rebuild. The desktop app is where most of the action is. It's not designed like a traditional IDE anymore. It's designed as what Google is calling an agent control tower. You can now run multiple AI agents at the same time working on completely different parts of your project in parallel. One agent handles the backend, another builds the interface. They work simultaneously, and you're not waiting around for one to finish before the other starts. You can schedule tasks to run in the background. So, these agents aren't just sitting there waiting for you to tell them what to do. They're actively working even when you're not looking. Google added voice command support which lines up with what they've been doing across Gmail and Docs. And the whole thing connects directly into Google AI Studio, Android development, Firebase, the entire Google ecosystem. Google even said they used anti-gravity itself to help build Gemini 3.5 Flash, which is a pretty strong signal that this tool is already handling real production level work internally. Now, the CLI migration is a whole separate issue and it's causing its own set of problems. If you've been using Gemini CLI, Google wants you off of it completely. The deadline is June 18th, 2026. After that date, Gemini CLI stops working for prousers, ultra users, and even people on the free tier. Another report says Gemini Code Assist IDE extensions will also stop processing requests entirely. So, this isn't optional. The new anti-gravity CLI is built in Go, which makes it faster and more responsive than the old tool. It supports asynchronous workflows, so you can control multiple agents running in the background, and it uses the same agent harness as the desktop app, which means any improvements Google makes to the core agent system apply to both products at once. The actual migration is straightforward if you know what you're doing. The old command was Gemini and now it's anti-gravity, but the structure is the same. The issue is not the complexity of the switch. The issue is that Google gave people less than a month to make it happen and then basically said the old tool is getting shut off whether you're ready or not. But the really interesting part of this whole platform is the managed agents layer. This is where Google is making a much bigger move than just giving developers a nicer coding assistant. With managed agents, you can create an AI agent through the Gemini API with a single API call and that agent can reason, use tools and execute code inside an isolated Linux environment. Every time you start a conversation with the agent, it spins up an environment and that environment persists across subsequent calls. It remembers what it did. It keeps the context. Developers can extend these agents with custom instructions and skills. And Google AI Studio Playground now provides custom agent templates to make that easier. This is Google essentially handing developers the same agent infrastructure it uses internally. And it's co-optimized with Gemini 3.5 Flash specifically for this kind of workload. And that brings us to the model itself. Because none of this works unless the underlying AI is fast enough to actually handle it. Gemini 3.5 Flash is the engine running everything here. Google claims it hits 289 tokens per second. For comparison, Claude Opus 4.7 runs at 67 tokens per second and GPT 5.5 runs at 71 tokens per second. If those numbers hold up, that's roughly four times faster than the competition. Google also says Gemini 3.5 Flash beats the older Gemini 3.1 Pro model across most benchmarks while being significantly faster. And speed matters a lot more when you're running agentic workflows where multiple agents are waiting on each other in chains. If one agent is slow, the whole system bottlenecks. The speed difference is the reason this kind of parallel agent orchestration is even possible in the first place. During the IO keynote, Varun Mohan, who runs Google's anti-gravity platform, did a live demo that was honestly pretty wild. He showed the system building a complete operating system from scratch in 12 hours for under $1,000. The process ran 93 sub aents working simultaneously, processed 2.6 billion tokens across 15,000 model requests, and then at the end of the demo, he ran Doom on the new OS Live on stage. That's not a toy project. That's a full operating system with a working kernel and enough stability to run a game. Whether or not that demo was perfectly polished for the stage, the scale of what it showed is a pretty clear signal of where Google thinks this is all going. So, let's talk about pricing because Google is clearly trying to build this into a tiered product line. The base pro plan is bundled with a Google AI pro subscription and that's the entry point for individual developers or people just experimenting with agents. The new AI Ultra plan costs $100 a month and gives you five times the usage limits of Pro. For people running multiple agents regularly or building production workflows, that tier makes a lot more sense than Pro. Then there's Ultra Premium at $200 a month, which used to be $250, and that comes with 20 times the Pro usage limits. It's aimed at teams and enterprises, especially ones already running on Google Cloud. Google is also offering $100 in bonus credits for new subscribers through May 25th, 2026. And the Ultra plan includes extras like 20 terabytes of storage and YouTube Premium. For freelancers, Pro is probably enough. For startups shipping fast, Ultra is the sweet spot. For enterprise teams, the upgrade path into Google Cloud's full agent platform is sitting right there. Google is also putting serious money behind the ecosystem. They launched the Build with Gemini X-P Prize hackathon with a $2 million prize pool, which they're calling the largest hackathon prize ever. That's not just a marketing stunt. That's Google trying to jumpstart a developer community around this platform and get people building on top of it as fast as possible. They also announced a Google AI Studio mobile app that developers can pre-register for. And the pitch there is that you can capture an idea on the go and turn it into a working prototype before you even sit down at your desk. Agents can now make native calls to Google Workspace APIs. There's full Android support so you can build Android apps using prompts and publish them straight to the Google Play Console test track from inside AI Studio and entire projects can be exported to local development in anti-gravity with one click while keeping the full project context intact. This is not just a tool. This is Google trying to own the entire stack from idea to deployment. When you compare anti-gravity 2.0 zero to the competition. The positioning becomes pretty clear against cursor anti-gravity wins on multi-agent orchestration, background task scheduling, voice command support, deep firebase and Android integration, and the enterprise path through Google Cloud. Cursor still has the advantage of familiarity because it's built on VS Code, so developers don't have to change their entire setup. against GitHub copilot workspace. Anti-gravity has much stronger multi-agent capabilities and more aggressive automation. Anti-gravity starts at $100 a month for the ultra plan. Cursor is $20 a month. Copilot workspace is 19. So Google is clearly not trying to compete on price. They're competing on depth and infrastructure. If you're building on Android or Google Cloud, anti-gravity is designed to be the obvious choice. If you just want an AI assistant inside your existing editor, cursor still makes more sense. But here's where the story gets messy. Because while Google was announcing all of this at IO, the actual roll out of anti-gravity 2.0 was causing chaos for a lot of developers. The update was automatic. People didn't opt in. They just woke up to a completely different product. And the problems were immediate. Anti-gravity 2.0 Zero and anti-gravity IDE, which is the traditional code editor version, apparently conflict with each other during installation. They fight over the same directory and overwrite each other. That means if you had both installed, one of them would just delete the other. Existing workspace configurations were getting corrupted. Developers were losing their setups. And the bigger issue is that anti-gravity 2.0 is built for a completely different workflow. The traditional editor experience was gutted. Visual indicators for warnings and errors were either gone or much harder to find. Direct code editing was stripped down or removed in favor of a much more minimalist interface. Git and repository management became way more manual and command line driven instead of being visually integrated. Some developers said they felt completely blind to smaller bugs because the AI would ignore minor warnings as long as the application was still running and didn't crash. On top of that, the system had tracking issues. close an app, anti-gravity was testing, and the chat interface would still register it as running, then diagnose the closure as a malfunction. Developers had to manually kill processes just to prevent false error reports. Reddit and Google's forums filled with complaints within hours. One person said it felt like non-technical people were shipping to production. Another called the agent first pivot a massive step backward. The fix for many was uninstalling anti-gravity 2.0 zero completely downloading anti-gravity IDE separately, manually copying config files or rolling back to version 1.23.2 and disabling automatic updates. There were positives though. Realtime monitoring improved significantly. Memory consumption dropped from over a gigabyte down to 150 to 500 megabytes with automatic efficiency mode. Google refilled credits as compensation, but developers now face three separate tools. Anti-gravity 2.0 for agents, anti-gravity IDE for traditional coding, anti-gravity CLI for terminal work. The automatic rollout broke environments without warning or roll back options. So why push this hard? Because Google isn't treating AI as a feature anymore. It's the foundation. They're using similar tech in search to build custom layouts per query. Gemini Spark runs background tasks across workspace. Gemini Omni handles video generation. The pattern is clear. AI that works continuously, not just on demand. The real question is whether developers are ready. Because Google isn't just making coding faster. They're redefining the developers role from writing code to supervising agents. That's fundamentally different. And the backlash shows many weren't ready for that jump overnight, but Google forced it anyway. So, where do you stand on this? Are you excited about the move toward AI agent workflows, or do you think developers are right to push back? Let me know below. Thanks for watching, and I'll catch you in the next one.