💻 techPerson2 views3 min read

What Happened to Justin Poehnelt?

Justin Poehnelt, a Google Workspace CLI developer with nearly seven years at Google, was fired in April 2026 after his independently developed Google Workspace CLI tool, 'gws', went viral. He attributes his dismissal to Google's internal fears of AI Agent disruption to its Workspace products, while Google's legal department cited branding issues for the unauthorized release of the tool. The firing occurred just two days before Google Cloud Next 2026 announced an upcoming official Workspace CLI.

Share:

Quick Answer

Justin Poehnelt, a Google developer, was fired by Google in April 2026, approximately two months before he publicly disclosed the event on June 23, 2026. His dismissal followed the viral success of 'gws', a Google Workspace CLI tool he developed. Poehnelt believes the underlying reason was Google's apprehension about AI Agent disruption to its Workspace offerings, despite the company's legal department citing branding policy violations. Ironically, Google announced its own official Workspace CLI just two days prior to his termination.

📊Key Facts

Google Tenure
Nearly 7 years
ABAB News, OfficeChai
Firing Date (Approx.)
April 2026
ABAB News, OfficeChai
Public Disclosure Date
June 23, 2026
ABAB News, OfficeChai
GitHub Stars (gws)
Thousands
ABAB News

📅Complete Timeline9 events

1
Circa 2019Notable

Justin Poehnelt Joins Google

Justin Poehnelt begins his tenure at Google, eventually working in the Workspace Developer Relations team for nearly seven years.

2
Prior to March 2026Major

Development of 'gws' Google Workspace CLI

Justin Poehnelt independently develops 'gws', a unified command-line interface for Google Workspace APIs, designed for both human and AI agent interaction.

3
March 5, 2026Major

Addy Osmani Tweets About 'gws'

Addy Osmani, then a Director at Google Cloud AI, shares Poehnelt's 'gws' tool on X (formerly Twitter), describing it as 'built for humans and agents', contributing to its viral spread.

4
March 2026Major

'gws' Goes Viral

Poehnelt's Google Workspace CLI tool, 'gws', gains significant popularity, topping Hacker News and receiving thousands of GitHub stars.

5
April 2026Critical

Google Cloud Next 2026 Announces Official Workspace CLI

Google Cloud Next 2026 announces that an official Workspace CLI is in development, with CEO Thomas Kurian declaring 'the era of the agent is here.' This announcement occurs two days before Poehnelt's dismissal.

6
April 2026Critical

Justin Poehnelt Fired by Google

Justin Poehnelt is dismissed from Google, approximately two months before his public disclosure. He believes the firing was due to Google's fear of AI Agent disruption, while Google cited branding policy violations.

7
June 23, 2026Critical

Poehnelt Publicly Discloses Firing on X

Justin Poehnelt posts on X (formerly Twitter) revealing his dismissal from Google and sharing his perspective on the reasons behind it, sparking widespread discussion.

8
June 23, 2026Major

Hacker News Discussion Ignites

The news of Poehnelt's firing and his perspective becomes a top discussion on Hacker News, with many developers debating Google's actions and policies.

9
June 24, 2026Major

Media Coverage Expands

News outlets like OfficeChai and ABAB News report on Justin Poehnelt's firing, analyzing the implications for open-source development, internal innovation, and the impact of AI agents in large tech companies.

🔍Deep Dive Analysis

Justin Poehnelt, a software engineer who had dedicated nearly seven years to Google, found himself at the center of a significant tech industry discussion in June 2026 following his public disclosure of being fired by Google. The termination, which occurred around April 2026, stemmed from his development of an unofficial yet highly popular Google Workspace Command Line Interface (CLI) tool, dubbed 'gws'. This tool, designed to provide unified access to various Google Workspace APIs for both humans and AI agents, quickly gained traction, topping Hacker News and accumulating thousands of GitHub stars.

Poehnelt, who worked in the Workspace Developer Relations team, stated that his role often involved building open-source layers and abstractions over Google APIs. He claims that while his project initially garnered attention from leadership, it later faced scrutiny from Google's legal department over branding issues. However, Poehnelt contends that the branding violation was merely a pretext, and the true motivation behind his dismissal was a broader concern within the Workspace team regarding the potential disruption posed by AI Agents. He highlighted that Google Cloud Next 2026 announced an official Workspace CLI just two days before his firing, creating a stark irony where the engineer who had already built a successful, agent-ready tool was let go.

The incident has sparked considerable debate within the developer community and among former Google employees. Some commenters on Hacker News acknowledged that releasing a project with Google's branding without proper approval constitutes a policy violation, regardless of the project's technical merit. They pointed out that a long-tenured employee like Poehnelt should have been aware of the disclosure and approval processes for such projects. Conversely, many view the firing as an extreme consequence, especially given Google's historical embrace of open-source contributions and the fact that Poehnelt's tool addressed a clear need for a unified Workspace CLI, particularly in the emerging 'agentic AI era' that Google itself is championing.

This event is seen by some analysts as reflecting a broader tension within large tech companies like Google, where internal innovation, especially in rapidly evolving fields like AI, can clash with established corporate strategies and control mechanisms. The fear of AI Agent disruption within existing product lines, coupled with the desire to maintain product control and concentrate resources on core strategic projects, appears to be a significant factor. The situation underscores how big companies' defensive reactions to disruptive tools can accelerate talent movement towards external open-source communities and independent AI projects.

As of June 24, 2026, Justin Poehnelt has publicly shared his story on X, generating widespread discussion and media coverage. While his immediate next steps in terms of employment are not explicitly detailed in the available information, the narrative suggests a potential path towards independent development or involvement in the burgeoning open-source AI ecosystem, benefiting from the accelerated talent movement in this space.

What If...?

Explore alternate histories. What if Justin Poehnelt made different choices?

Explore Scenarios
Building relationship map...

People Also Ask

Who is 'The Google Workspace CLI Developer Fired by Google'?
The developer in question is Justin Poehnelt, a former Google employee who worked in the Workspace Developer Relations team for nearly seven years. He was fired in April 2026 after creating a popular, unofficial Google Workspace CLI tool.
Why was Justin Poehnelt fired from Google?
Justin Poehnelt states he was fired due to Google's internal fears of AI Agent disruption to its Workspace products, with the legal department citing branding issues for his unauthorized open-source CLI tool. Commenters also noted that releasing a project with Google's logo without brand approval is a policy violation.
What was the Google Workspace CLI tool that Justin Poehnelt created?
Justin Poehnelt created 'gws', a unified command-line interface (CLI) that provided access to various Google Workspace APIs. It was designed to be used by both humans and AI agents and gained significant popularity.
What is the irony surrounding Justin Poehnelt's firing?
The irony lies in the timing: Google Cloud Next 2026 announced an upcoming official Google Workspace CLI just two days before Poehnelt, who had already built a viral and agent-ready version of such a tool, was dismissed.
What is Justin Poehnelt's current status?
As of June 24, 2026, Justin Poehnelt has publicly disclosed his firing on X, and his story has generated widespread discussion and media attention within the tech community. His specific next employment steps are not yet publicly detailed.