Here’s a concise comparison between **SUPERCLI** and **[Google Workspace CLI (gws) repository on GitHub](https://www.sourcetrail.com/software/google-workspace-cli-the-ai-first-command-line-for-gmail-drive-and-more/?utm_source=chatgpt.com)** — positioning SUPERCLI as **the OSS alternative you’re aiming for**.

---

## 🔎 **Google Workspace CLI (`gws`) — What It Is**

**Scope**
A unified CLI front‑end for Google Workspace APIs (Gmail, Drive, Calendar, Sheets, Docs, Chat, Admin, etc.). It dynamically builds its command surface from the Google Discovery Service and exposes Workspace capabilities to both humans and AI agents. ([SourceTrail][1])

**AI‑Agent Focused Features**

* Structured JSON output by default
* Built‑in agent “skills” (100+ predefined operations)
* Optional MCP server mode for direct agent integration
* Dynamic schema discovery so commands reflect the latest APIs without manual updates ([openclawai.io][2])

**Strengths**

* Covers an entire ecosystem (Google Workspace)
* Dynamic runtime command generation
* Structured output and agent compatibility from day one
* MCP server for agent tool discovery

**Limitations**

* Focused on **one specific ecosystem** (Workspace)
* CLI is tied statically to Google APIs
  – Designed as a direct wrapper over Google’s REST surface rather than a meta‑command platform
* Version 1.0 not yet final; breaking changes likely ([SourceTrail][1])

---

## 📌 **SUPERCLI — The OSS Alternative**

SUPERCLI is **architecture‑agnostic** and meant to go well beyond a single API stack. It is designed as:

### 🧠 1. **Discoverable**

Commands are generated from cloud config (OpenAPI, MCP servers, custom integrations), so any API surface — internal or external — becomes part of the CLI.

### 🔍 2. **Introspectable**

Every command exposes:

* Input/output schemas
* Adapter info
* Side‑effects and risk metadata
  Agents can query command shapes programmatically.

### 🕹 3. **Plannable**

Each command internally builds a **DAG of execution steps** (validation, adapter calls, transforms). Agents can request this data optionally for introspection, but **execution stays single‑call** (no separate plan/execute dual‑call requirement).

### 🚀 4. **Executable**

Commands run in one invocation, returning:

* `result`
* `metadata`
* optional DAG (`--show-dag`)
  Structured, deterministic output is ideal for token‑constrained agents.

---

## 🆚 **Key Differences**

| Aspect                | Google Workspace CLI (`gws`)                                                  | SUPERCLI                                                                                  |
| --------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Scope**             | Google Workspace APIs only                                                    | Universal (any OpenAPI/MCP/custom integration)                                        |
| **Config Source**     | Google Discovery Service                                                      | Cloud config + OpenAPI specs + custom                                                 |
| **Agent Integration** | Built‑in MCP server + agent skills                                            | Agent‑friendly by design (structured JSON, semantic exit codes, schema introspection) |
| **Execution Model**   | Traditional CLI with dynamic surface (multiple calls when using MCP)          | Single‑shot DAG execution with optional introspection                                 |
| **Extensibility**     | Focused on Workspace ecosystem                                                | Generalized to serve internal tools, infra, business systems                          |
| **OSS Positioning**   | Google project (not officially supported), practical for Workspace automation | Purpose‑built open alternative for agentic workflows across arbitrary APIs            |

---

## 🧠 **Why SUPERCLI as an OSS Alternative**

**gws** solves the narrow problem of Google Workspace API automation and agent interaction. It is extremely useful for that domain but doesn’t generalize.

**SUPERCLI, by design, is a platform:**

* Built to unify *any* API surface into a consistent CLI
* Not tied to a single ecosystem
* Provides built‑in support for schema introspection, semantic outputs, agent‑friendly error handling, and optional DAG inclusion
* Allows internal workflows, business apps, and automation stacks to be exposed consistently to agents and humans alike

In short:

> Where Workspace CLI is **a specialized tool for one suite**, SUPERCLI is **a general OSS platform for building AI‑friendly CLIs across all APIs and automation surfaces**.

---

## 🧠 **Why This Matters for AI Agents**

Both prioritize agent access, but:

* gws is useful where the API surface is already defined and singular (Workspace)
* SUPERCLI is meant to be the **developer platform** that lets teams define *their own* agent‑friendly CLIs for any backend, without writing code

This makes **SUPERCLI the open‑source alternative for teams that want agent‑friendly automation everywhere, not just in Google Workspace**. ([SourceTrail][1])

---

If you want, I can sketch a **side‑by‑side UX comparison** — what an agent sees when interacting with gws vs what they see with SUPERCLI for the same hypothetical API.

[1]: https://www.sourcetrail.com/software/google-workspace-cli-the-ai-first-command-line-for-gmail-drive-and-more/?utm_source=chatgpt.com "Google Workspace CLI: AI-first command line for Gmail and Drive"
[2]: https://openclawai.io/blog/google-workspace-cli-gws-ai-agents/?utm_source=chatgpt.com "Google Just Released a Workspace CLI Built for AI Agents — And It Has an MCP Server | OpenClaw AI"
