Two of the biggest cloud vendors are quietly walking away from their own AI coding assistants. AWS stopped taking new Amazon Q Developer signups in May 2026 and will pull support for its IDE plugins entirely by 30 April 2027, pointing existing users toward Kiro instead. Google went further and faster: individual-tier Gemini Code Assist and Gemini CLI shut down for solo developers on 18 June 2026, with Google steering them to a new agent-first platform, Antigravity, launched as a preview the month before. Team and Enterprise Gemini customers are unaffected — this is specifically the free and individual tiers that have gone.
Why two well-funded platforms are folding a product line
Neither AWS nor Google is short of money or AI talent, which makes this a genuine market signal rather than a cost-cutting story. When two hyperscalers both retreat from general-purpose coding assistants in the same quarter, it means the category has already consolidated around a smaller set of tools that most developers actually reach for day to day. Search and adoption data back that up: Claude Code, Cursor and GitHub Copilot now account for the overwhelming majority of daily AI coding usage, each occupying a distinct niche — Copilot for editor-embedded enterprise adoption, Cursor for standalone-IDE agility, Claude Code for terminal-first, deep codebase reasoning.
So what
If you’re choosing a development partner and asking what tools they use, “we support whatever the client prefers” is no longer a neutral answer — half the AI coding assistants on the market a year ago won’t be supported past 2027. A team that has already consolidated its own workflow around the tools that are actually winning is one that isn’t going to hand you a stack it’ll need to migrate off mid-project. That’s part of what we mean by AI-assisted development done properly: picking tools for where they’re heading, not just where they are today.