Why a Google Engineer Was Fired After Building the Open‑Source Google Workspace CLI
The open‑source Google Workspace CLI, which turned the Workspace API into a unified, human‑ and AI‑friendly command‑line tool and quickly amassed thousands of GitHub stars, led its creator Justin Poehnelt to be dismissed by Google amid concerns over branding and internal politics.
Project Overview
Google Workspace CLI is an open‑source command‑line tool that wraps the Google Workspace REST APIs. It replaces hand‑crafted curl commands with typed commands, provides per‑resource --help, supports --dry-run previews, automatically handles pagination, and returns all output as structured JSON.
Repository: https://github.com/googleworkspace/cli. The project has close to 30 000 stars. Contribution statistics show the primary author with 24 commits and a bot with 20 commits.
Architecture – Two‑Phase Parsing
Parse argv to identify the target service (e.g., drive).
Fetch the service’s Discovery Document and cache it for 24 hours.
Generate a clap::Command tree from the document’s resources and methods.
Parse the remaining command‑line arguments against the generated tree.
Perform authentication, build the HTTP request, and execute it.
All responses—including successful results, error messages, and download metadata—are emitted as structured JSON.
Agent Skills
The CLI ships with more than 100 built‑in Agent Skills defined in SKILL.md, covering Gmail, Drive, Docs, Calendar, Sheets and other Workspace apps. It also includes high‑level workflow helpers and 50 curated usage examples.
Impact
By exposing the Workspace APIs through a uniform JSON‑based CLI, the tool enables both human developers and LLM‑driven agents to interact with Workspace without writing custom request code.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
