Two months ago, Justin Poehnelt was fired by Google. The reason: he created Google Workspace CLI (gws) — a command-line tool that unified Drive, Gmail, Calendar, and every Workspace API, designed for both humans and AI agents.
The project shot to the top of HN and earned thousands of GitHub stars. Then Google’s legal department got involved.
Trademarks, Logos, and the “Confusable Official Look”
From the HN comment thread, the direct trigger was brand usage. Poehnelt’s project was hosted under github.com/googleworkspace/cli and used Google’s logo and brand colors. Multiple commenters noted that from the project homepage alone, you could easily mistake it for an official Google product.
Google Legal’s stance on this is clear: unauthorized use of company trademarks and brand identity, even by an internal employee, can constitute a violation. The comment section split into two camps.
One camp saw an obvious line crossed. “Releasing something that can be mistaken for an official release demonstrates a massive judgment problem,” one commenter wrote. “If done without the process, at minimum significant disciplinary action; if explicitly warned before, termination is reasonable.”
The other camp argued the brand issue could have been resolved purely through technical means — remove the logo, rename it — just like the Clawdbot → Moltbot → OpenClaw case. “Google is famous for rarely firing people even over performance issues,” one commenter noted. “Either the company’s stance has shifted, or there’s more to this story.”
20% Time Is Dead?
The deeper controversy is cultural.
Google was once famous for its “20% time” policy — engineers could spend one-fifth of their work hours on personal projects. Gmail, Google News, and AdSense were all born from 20% time. The prevailing sentiment in the comments: if Poehnelt’s CLI had appeared at Google in 2010, the outcome would have been completely different.
“Google went from encouraging 20% time to create amazing projects, to firing people for doing it,” one highly-upvoted comment read. Others pointed to a parallel event: Google’s open-source Gemini CLI being replaced by the closed-source Antigravity CLI — interpreted as two sides of the same trend: internal innovation is no longer encouraged unless it serves a specific product roadmap.
Pournelle’s Iron Law was invoked as an explanatory framework: “In a bureaucracy, those who fight for the system’s own sake will always take power, while those who fight for the values the system is supposed to serve will have diminishing influence.” Poehnelt was the latter — building interesting and useful things out of self-driven motivation. His opponents were the former — more concerned with internal bureaucracy and their own role within it.
The AI Anxiety
There’s also context that can’t be ignored: Poehnelt’s CLI was explicitly designed to serve both human users and AI agents. Its tagline was “built for humans and AI agents.” This positioning created direct tension with Google’s internal push toward closed-source AI tooling.
When a frontline engineer’s personal project starts colliding with the company’s planned commercial AI product roadmap, “trademark violation” may just be the easiest card to play. As one commenter put it: “I think the real reason is that some leader or project inside Workspace is afraid of being disrupted.”
Poehnelt’s own follow-up response was restrained: “I won’t share too much additional information, but I think this reflects the experience of working at a big tech company and the disruption AI is causing at the level of teams, roadmaps, incentives, and user behavior changes.”
The Eternal Tension: Open Source and Employers
This case also triggered discussion about engineers’ open-source rights.
Even within Google, the boundaries around how much personal open-source work an employee can do, how they can use the company brand, and whether they can release internal tools externally have always been a gray area. Enforcement varies enormously across teams and managers. One commenter noted: “I’m not sure Googlers regularly open-source side projects under the official org — Google’s policy on this has always been ambiguous.”
Poehnelt’s case may become a precedent: big companies’ tolerance for employee personal open-source projects is narrowing. When a side project gains enough attention and traction to potentially interfere with the company’s official product roadmap, brand compliance issues get magnified into existential ones.
This article draws on publicly available information and community discussions. If you have deeper first-hand experience with this topic, corrections and additions are welcome.