On April 2, 2026, Justin Poehnelt was fired from Google for building a tool that thousands of developers loved. His creation — the Google Workspace CLI — hit #1 on Hacker News and gained thousands of GitHub stars within days. Two months later, Google shut down individual Gemini Code Assist and Gemini CLI on June 18, 2026.
TL;DR: Justin Poehnelt was fired by Google in April 2026 for creating the Google Workspace CLI, a tool that hit #1 on Hacker News and gained thousands of GitHub stars within days. Google simultaneously shut down individual Gemini Code Assist and Gemini CLI on June 18, 2026, directing users to the new Antigravity CLI.
Who Is Justin Poehnelt and What Did He Build?
Justin Poehnelt was a software engineer at Google who created the Google Workspace CLI — a command-line interface that let developers interact with Google Workspace APIs directly from the terminal. The tool filled a gap that Google’s own products had left open. It spread fast.
The CLI allowed developers to manage Google Workspace resources without navigating through web interfaces or writing boilerplate authentication code. According to Poehnelt’s public statement on X, the tool gained “thousands of GitHub stars and many thousands of actual users in just a couple days” after reaching #1 on Hacker News. That level of adoption is rare for a developer tool built by a single person.
Poehnelt worked at Google as a software engineer, though the exact team and tenure he was part of have not been publicly detailed beyond his own statements. His X post describes the experience as “an incredible, confusing journey, from directors and leaders asking” questions — suggesting the tool attracted internal attention from senior Google leadership almost immediately after going viral.
The Google Workspace CLI addressed a real pain point. Developers working with Google Workspace APIs typically face complex OAuth flows, verbose SDK setup, and inconsistent documentation. A unified CLI that abstracted away authentication and provided clean commands for common operations would naturally appeal to anyone building integrations with Google Docs, Sheets, Drive, or Calendar.
What made the tool notable wasn’t just its functionality — it was the speed of adoption. Thousands of GitHub stars in days means the developer community was actively waiting for something like this. Google’s own tooling had not filled the gap.
Why Did Google Fire Justin Poehnelt?
Google fired Justin Poehnelt in April 2026, approximately two months before the company shut down individual Gemini Code Assist and Gemini CLI. Poehnelt himself confirmed the termination in a public post on X dated June 2026, stating: “Two months ago I was fired by Google for creating the Google Workspace CLI.”
The exact internal reasoning behind the firing has not been publicly documented in full detail. However, the timeline raises questions. Poehnelt built a tool that gained rapid traction among developers. Google then removed it. Two months later, the company deprecated individual access to Gemini Code Assist and Gemini CLI on June 18, 2026, and directed users toward Antigravity CLI, a newer tool with a different interface and associated migration costs.
Poehnelt’s description of the aftermath hints at internal friction. He wrote that the experience involved “directors and leaders asking” — suggesting that senior leadership became involved after the tool went viral. When a personal project built using company-adjacent resources gains that level of visibility, corporate response can go in unpredictable directions. Some companies celebrate internal innovation. Others see risk.
Possible factors behind the termination could include concerns about unofficial tooling being mistaken for Google products, API usage policy violations, or conflicts with internal product roadmaps. Without an official statement from Google detailing the cause, the precise justification remains unclear.
What is clear is the sequence: a Google engineer built a widely adopted tool, Google fired him, and then Google removed or replaced the services the tool interacted with.
How Did the Google Workspace CLI Go Viral?
The Google Workspace CLI reached #1 on Hacker News, a community-driven news site that ranks stories based on user votes and engagement. Hacker News, operated by Y Combinator, is one of the most influential platforms for developer tool adoption. A #1 ranking typically means a tool is being seen by tens of thousands of developers within hours.
Poehnelt stated that the CLI “went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.” That trajectory — from posting to peak adoption in under 72 hours — indicates strong latent demand. Developers were not just curious. They downloaded and used it.
Several factors likely contributed to the viral spread. First, Google Workspace is used by millions of organizations, meaning the potential user base for a Workspace CLI was enormous. Second, existing Google developer tooling had well-documented friction points around authentication and API complexity. A tool that simplified those workflows would naturally generate excitement.
The Digg coverage of the story amplified visibility beyond the developer community. Social media discussion on X, where Poehnelt shared his account of the firing, further extended the reach. The combination of technical merit and corporate controversy created a narrative that resonated far beyond a typical product launch.
GitHub stars are often called a vanity metric, but “many thousands of actual users” is not. That distinction matters. People were not just bookmarking the repository. They were installing and running the tool in production environments.
What Was Google’s Official Response to the CLI?
Google has not published a detailed official statement specifically addressing the Google Workspace CLI or Justin Poehnelt’s termination. The company’s actions, however, speak clearly. The tool was removed, and Poehnelt was fired.
What Google did next is more telling. On June 18, 2026, the company shut down individual access to Gemini Code Assist and Gemini CLI. According to AI Navigate News, the shutdown affected individual users, while enterprise licenses continued. Consumer-facing GitHub code review was also scheduled to end on July 17, 2026. The recommended migration path for affected users was Antigravity CLI — a new tool with a different operational model.
The Antigravity CLI and IDE represent Google’s consolidated approach to AI-assisted development tooling. A guide published on Medium in May 2026 by Darren Lester details how to configure MCP (Model Context Protocol) servers and skills for the Antigravity CLI and IDE, indicating that the tool was already being positioned as the successor to Gemini CLI before the individual shutdown took effect.
This sequence suggests that Google had a product strategy in motion. The Antigravity CLI was being prepared as the unified interface. Individual Gemini tools were being deprecated. Whether Poehnelt’s independent CLI conflicted with this roadmap is a matter of speculation, but the timing aligns uncomfortably.
Google’s silence on the specifics of the firing leaves room for interpretation. The company has not publicly contradicted Poehnelt’s account.
What Replaced the Google Workspace CLI After Removal?
After the Google Workspace CLI was removed and individual Gemini Code Assist and Gemini CLI were shut down on June 18, 2026, Google directed users to the Antigravity CLI as the primary replacement. Antigravity CLI is part of a broader Antigravity platform that includes both a command-line interface and an integrated development environment.
The transition is not frictionless. According to AI Navigate News, the shift to Antigravity CLI introduces migration costs because the operational feel and command structure differ from the previous Gemini tools. Users who relied on Gemini CLI workflows need to learn new commands and reconfigure their development environments.
The Antigravity CLI uses MCP (Model Context Protocol) servers and a skills system for configuration. Darren Lester’s guide on Medium, published in May 2026, walks through how to unify MCP server and skills configuration across the Antigravity CLI and IDE. This architecture represents a different approach from the standalone CLI model that Poehnelt’s tool followed.
For enterprise users, Gemini Code Assist remains available under paid licensing. The shutdown specifically targeted individual and consumer-tier access. This means organizations with enterprise contracts retain functionality, while independent developers and small teams face the migration to Antigravity or alternative tools.
The removal of Poehnelt’s CLI, followed by the deprecation of individual Gemini developer tools, leaves independent developers with fewer options. Some may adopt Antigravity CLI. Others may look to community-maintained alternatives or build their own integrations — though Poehnelt’s experience may give them pause.
How Does This Fit Google’s Broader AI Tooling Strategy?
Google has been aggressively consolidating its developer tooling around the Gemini brand family. The company shut down Gemini Code Assist and Gemini CLI for individual users on June 18, 2026, redirecting developers toward a unified platform called Antigravity (AI Navigate News, 2026). This strategic pivot reveals a clear preference for controlled, official tooling over community-driven projects.
The termination of Justin Poehnelt aligns with this pattern. His Google Workspace CLI gained thousands of GitHub stars and hit #1 on Hacker News within days (Poehnelt, X, 2026). That level of organic adoption for an unofficial tool likely created internal friction. Google wanted developers using Antigravity, not an independent CLI built by a single engineer.
This strategy carries real migration costs. Developers who relied on Gemini CLI must now learn a new tool with different operational patterns (AI Navigate News, 2026). Consumer-facing GitHub code review features also ended on July 17, 2026. Google is narrowing its focus.
The message seems clear. Google wants full ownership of how developers interact with its AI ecosystem. Independent projects that gain massive traction outside official channels may be treated as competitive threats rather than community contributions.
What Happened to Gemini Code Assist and Gemini CLI?
Google officially discontinued Gemini Code Assist and Gemini CLI for individual developers on June 18, 2026 (AI Navigate News, 2026). Enterprise licenses remain available, but individual developers lost access to both tools on that date. The shutdown forced thousands of independent developers to find alternatives.
The consumer-facing GitHub code review feature also received an end date. That service is scheduled to shut down on July 17, 2026 (AI Navigate News, 2026). These closures represent a significant contraction in Google’s free developer tooling offerings.
Several factors likely drove the decision. Maintaining separate individual and enterprise code assistance products requires sustained engineering investment. Google apparently decided that consolidating into a single platform made better business sense. The transition is not frictionless.
Developers migrating to Antigravity CLI face operational changes. The new tool handles configuration differently, and switching costs are real (AI Navigate News, 2026). Enterprise customers retain their existing licenses and workflows for now. Individual developers bear the brunt of the disruption.
What Is the Antigravity CLI That Replaced Them?
Antigravity CLI is Google’s new unified command-line interface and integrated development environment for AI-assisted coding. It replaces both Gemini Code Assist and Gemini CLI for individual users as of June 2026. The platform supports MCP (Model Context Protocol) servers and configurable skills (Lester, Medium, 2026).
The architecture differs from its predecessors. Antigravity CLI allows developers to configure MCP servers that provide context to AI models during code generation and review. Skills can be defined to customize how the tool responds to specific programming tasks (Lester, Medium, 2026). This modular approach gives developers more control over AI behavior.
Configuration works through a unified system. Developers define MCP servers and skills in settings files that persist across sessions. The IDE component integrates with the CLI, creating a connected workflow for writing, reviewing, and deploying code (Lester, Medium, 2026). Setup requires understanding the new configuration model.
Migration from Gemini CLI involves learning these new patterns. Developers must recreate their workflows using Antigravity’s MCP server and skills framework. The transition takes effort but offers greater customization potential.
What Does This Incident Reveal About Google’s Internal Policies?
The firing of Justin Poehnelt reveals a strict boundary around unofficial tool creation at Google. Poehnelt built the Google Workspace CLI, which gained thousands of users and GitHub stars within days of release (Poehnelt, X, 2026). Despite the tool’s popularity and apparent utility, Google terminated his employment rather than embracing the project.
This outcome suggests Google’s internal policies prioritize official product roadmaps over individual innovation that bypasses approval channels. Directors and leaders initially engaged with the project, which Poehnelt described as an incredible and confusing journey (Poehnelt, X, 2026). The enthusiastic internal response made the subsequent termination more surprising.
The incident raises questions about how Google handles employee-built tools that use company APIs. The Google Workspace CLI interacted with Google services, which likely triggered policy concerns around unauthorized product development. Google has not publicly detailed the specific policy violations cited.
Other Google employees have departed under different circumstances. A software engineer recently quit to pursue an AI startup, describing the decision as scary but necessary (Business Insider, 2026). Poehnelt’s departure was involuntary and directly tied to his creative work.
What Can Developers Learn From the Google Workspace CLI Incident?
The Google Workspace CLI incident offers several concrete lessons for developers building tools around major platforms. First, popularity does not guarantee institutional support. Poehnelt’s tool hit #1 on Hacker News and gained thousands of GitHub stars rapidly (Poehnelt, X, 2026). That viral success did not protect him from termination.
Key lessons for developers:
- Review employment agreements carefully. Internal policies at major tech companies often restrict what employees can build, even on personal time.
- Understand API terms of service. Building tools around proprietary APIs without explicit approval carries significant risk.
- Viral adoption can attract unwanted attention. A tool that gains rapid traction may trigger reviews that unofficial projects cannot survive.
- Official channels matter. Google consolidated its tooling into Antigravity CLI, demonstrating preference for controlled products (AI Navigate News, 2026).
- Open source does not equal safe harbor. Publishing code publicly can amplify scrutiny rather than provide protection.
- Internal enthusiasm is not approval. Directors engaging with a project does not constitute official endorsement.
- Platform consolidation is accelerating. Companies are narrowing their developer tooling offerings and closing individual products.
- Migration costs fall on users. When tools shut down, developers who relied on them bear the transition burden (AI Navigate News, 2026).
| Aspect | Gemini CLI (Discontinued) | Antigravity CLI (Current) | Google Workspace CLI (Unofficial) |
|---|---|---|---|
| Status | Shut down June 18, 2026 | Active | Creator fired |
| Target users | Individual developers | All developers | Google Workspace users |
| Configuration | Standard CLI | MCP servers and skills | API wrappers |
| Official support | Was official | Official | Never official |
| GitHub code review | Ended July 17, 2026 | Integrated | N/A |
Frequently Asked Questions
Did Google rehire Justin Poehnelt after the CLI went viral?
No public evidence indicates Google rehired Justin Poehnelt after his termination. Poehnelt stated he was fired two months before his public disclosure and described the experience as an incredible, confusing journey where directors and leaders initially engaged with his tool before his dismissal (Poehnelt, X, 2026). His GitHub repository for the Google Workspace CLI gained thousands of stars, but viral popularity did not reverse the employment decision.
Is the Google Workspace CLI still available on GitHub?
The Google Workspace CLI repository gained thousands of GitHub stars within just a couple days of launching (Poehnelt, X, 2026). The repository’s current availability depends on whether Poehnelt has maintained or archived it since his termination. The tool reached #1 on Hacker News and attracted many thousands of actual users before the firing occurred.
What is the difference between Gemini CLI and Antigravity CLI?
Gemini CLI was shut down for individual users on June 18, 2026, while Antigravity CLI replaced it as Google’s active platform (AI Navigate News, 2026). Antigravity CLI introduces MCP server configuration and customizable skills, which Gemini CLI did not support (Lester, Medium, 2026). The migration requires developers to learn new operational patterns, creating transition costs that did not exist with Gemini CLI.
Can other Google employees build unofficial tools without being fired?
Google has not publicly clarified its internal policies regarding employee-built unofficial tools following Poehnelt’s termination. The Google Workspace CLI case demonstrates that building a tool using Google APIs without official approval can result in termination, even when the project gains thousands of users and GitHub stars (Poehnelt, X, 2026). Employees considering similar projects should carefully review their employment agreements and internal policies first.
Summary
The Google Workspace CLI incident highlights several critical realities about platform control, developer tooling, and employment at major tech companies.
- Google terminated Justin Poehnelt for creating an unofficial CLI that went viral, gaining thousands of GitHub stars and hitting #1 on Hacker News (Poehnelt, X, 2026).
- Gemini Code Assist and Gemini CLI were shut down for individual users on June 18, 2026, with consumer GitHub code review ending July 17, 2026 (AI Navigate News, 2026).
- Antigravity CLI replaced both tools, introducing MCP server configuration and customizable skills for a new unified workflow (Lester, Medium, 2026).
- Platform consolidation is accelerating at Google, with the company narrowing its free developer offerings and directing users toward controlled, official products.
- Viral success does not guarantee protection. Building unofficial tools around proprietary APIs carries real employment and legal risks, regardless of community enthusiasm.
If you found this analysis helpful, subscribe to my newsletter at gikiewicz.com for more coverage of AI tooling, developer platforms, and security developments.