Google launches Rust-based Workspace CLI gws for Gmail, Drive, Sheets

The Google Workspace CLI project vaulted to 15.5k GitHub stars and shot to number one on Hacker News with 571 points, putting a Rust-built command-line front end for Gmail, Drive, Sheets, Calendar, Docs, Slides, Chat, Admin, and more in front of developers today. The repo googleworkspace/cli, written 99.3 percent in Rust and licensed Apache-2.0, is live with 20 releases and a latest tag of 0.8.0 on March 7, 2026; if you want to try it now the published install command is npm i -g @googleworkspace/cli.

Under the hood the tool reads Google’s Discovery Service at runtime and builds its entire command surface dynamically, so new API endpoints appear without a client update, summarized in the project notes as: "No update needed on your end." The CLI advertises AI agent skills, structured output, and MCP support, and the repository explicitly describes itself as "one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more" while also warning users up front that "This is not an officially supported Google product."

The workspace editing workflows are concrete and opinionated: a git-like pull and push model pulls a Google Sheet into a local folder containing a .tsv file and a formula.json, lets you edit those files locally or have an agent edit them, and pushes the changes back to Sheets; the same pull/push idea extends to Docs and Slides. As one observer put it, "It’s the kind of workflow that makes you wonder why it didn’t exist five years ago." The project lists 26 contributors on GitHub, including usernames such as @jpoehnelt and bots like @gemini-code-assist[bot], and the repo includes a code of conduct, contributing guide, and security policy.

Google published documentation alongside the code showing how to integrate MCP-compatible agent tooling, with ready examples for connecting agents such as OpenClaw and MCP apps like the Claude Desktop app and the Gemini CLI. The documentation framing is blunt: "OpenClaw and other AI agents now have an official means to integrate with Google Workspace." That capability is the reason many community threads are focused less on basic OAuth plumbing and more on what agents should be permitted to do once they have programmatic Workspace access.

There are important caveats. The repo and project notes repeatedly label this release pre-v1.0 and warn that functionality may change dramatically and break workflows you build on top of it. The banner in the repository reads plainly, "This is not an officially supported Google product," and a cautionary line in the commentary asks, "How do you know this setup won’t blow up and delete all your data? That’s the fun part—you don’t." To get started you need a Google account with Workspace access, OAuth credentials for a Google Cloud project, and Node.js.

This release sits alongside Google’s wider push into Rust, including an official Rust SDK for Google Cloud that covers more than 140 APIs and is published on crates.io, authored in part by Aile Momoh and Carlos ORyan. Treat the Workspace CLI as an aggressive developer preview: it accelerates agent workflows and experiments now, but expect rapid change until a v1.0 and clearer support story arrive.