Google’s Workspace CLI is here, and it’s not officially supported—use at your own risk

The command line is having a moment. Again. For some of us, it never went away, but the AI boom has given terminals a second life. Google launched a Gemini CLI last year, and now they’re back with something more targeted: the Google Workspace CLI.

This new tool bundles all the existing Workspace APIs—Gmail, Drive, Calendar, the whole suite—into a single command-line package. The pitch is that you can hook it up to AI agents like OpenClaw and let them rummage through your data, send emails, check schedules, whatever you want. It’s designed for both humans and AI, but let’s be real, Google’s emphasis here is squarely on the AI side.

Here’s the catch: this is not an officially supported Google product. The GitHub repo is from Google, sure, but the README basically says “you’re on your own.” They warn that functionality may change dramatically as the tool evolves, and those changes could break whatever workflows you’ve built. So if you’re planning to wire this into something critical, maybe have a backup plan.

I’ve been around long enough to remember when Google would release experimental tools and then quietly kill them two years later. This feels similar. The Workspace CLI is clearly meant for tinkerers and power users who don’t mind living on the edge. If that’s you, great. If you’re hoping for a polished, stable product you can rely on, you might want to wait.

That said, the tool itself is genuinely useful for automation. Having a single CLI that can interact with all your Workspace data is a big step up from juggling individual API calls. And with OpenClaw integration, you can build some pretty sophisticated workflows. I can see this being a hit with developers who already live in the terminal and want to glue their AI agents to their email and calendar.

But the risk is real. You’re essentially giving a command-line tool full access to your Gmail, Drive, and Calendar. If something goes wrong—and it might—you could lose data. Google’s disclaimer is basically “we told you so.” So before you start piping your inbox through OpenClaw, make sure you understand what you’re getting into.

Personally, I’d treat this as a toy for now. Play with it in a sandbox environment, experiment with small automations, but don’t build your entire workflow around it until Google decides whether to officially support it. And knowing Google’s track record with experimental projects, that day may never come.