March 4, 2026
Bots, docs, and drama
Googleworkspace/CLI
One tool to run Gmail, Drive & Calendar—fans hyped, skeptics spooked
TLDR: A new tool called gws promises one-stop control of Gmail, Drive, Calendar and more, auto-updating from Google’s own API listings. Commenters are split between hype for easy automation and AI features, and worry about trust, rule-breaking, and commands changing unexpectedly—making it a bold but risky way to supercharge workflows.
Meet gws, the “one remote” for Google apps, promising to run Gmail, Drive, Calendar and more from a single command line. It reads Google’s own Discovery Service to auto‑update what it can do, and outputs clean JSON for both humans and bots. The community’s mood? Split down the middle.
Cheerleaders see a future where AI assistants and teams automate everything with “zero boilerplate” and 40+ skills. “Finally, real APIs (the ways apps talk) and CLIs!” cried the AI crowd, saluting a wave of agent‑friendly tools. CTOs joked about plugging it into “OpenClaw,” picturing dashboards lighting up like a Christmas tree.
Skeptics hit the brakes. This isn’t a Google‑made app, so terms‑of‑service anxiety flared: could it break rules? And the command list changing dynamically? One commenter called that an “anti‑pattern,” worrying the ground keeps shifting under users. Add the dev’s warning — expect breaking changes before version 1.0 — and the cautious vibes grow.
Memes rolled in: “Who gave the intern root access to my inbox?” and “Auto‑pilot for spreadsheets.” Whether you love the automation comeback or fear a surprise permission pop‑up, gws just turned Google Workspace into a new battleground.
Key Points
- •gws is a unified CLI for Google Workspace APIs that generates commands dynamically from Google’s APIs Discovery Service.
- •The tool targets both humans and AI agents, providing structured JSON responses, auto-pagination, tab completion, and per-resource help.
- •Installation is via npm, with examples covering Drive file listing, Sheets creation, Chat messages, schema introspection, and NDJSON streaming.
- •Authentication options include interactive desktop login (encrypted credentials), manual OAuth via Google Cloud Console, browser-assisted flows, exported credentials for CI, service accounts (with optional DWD), and pre-obtained tokens.
- •The project is under active development and may introduce breaking changes before reaching v1.0.