IdeaWell

Project ideas from Hacker News discussions.

Google Workspace CLI

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Is it really a Google product?
The community is split over whether the CLI is an official Google offering.
- “This is not an officially supported Google product.” – spankalee
- “I think an official project from Google would be hosted under github.com/google.” – hrmtst93837
- “It’s published by Google, they just don’t provide active ‘support’ for it.” – Lermatroid

2. Authentication is a nightmare.
Users repeatedly complain that the setup requires a full GCP project, OAuth screens, and manual scope verification.
- “I had to do all that the last time I wanted to do a little JS in my Google Sheets.” – jitl
- “The error tells me I need to verify my app… there’s no streamlined way to do this.” – virgildotcodes
- “I need to create an app in GCP to use it. Can't really expect non‑technical users to set this up across the company.” – mogili1

3. CLI vs. MCP vs. raw API – which is better for agents?
The discussion centers on the ergonomics of a CLI for LLMs versus a machine‑compatible protocol or plain HTTP calls.
- “CLI is probably more reliable.” – wonderfuly
- “The CLI has abstracted that into one single reusable, scriptable command.” – theshrike79
- “MCP is like ‘this is what the API is about, figure it out’.” – fergie
- “CLI tools are easy to write and you can cut it down to only what you need, saving thousands of tokens per prompt.” – corby

4. DevRel projects are often short‑lived and poorly maintained.
Many users warn that Google DevRel releases are “samples” that can be abandoned quickly.
- “They are not actually tasked with or graded on engineering projects.” – spankalee
- “I once had to fork a DevRel CLI that our on‑call scripts depended on and maintaining that fork cost a weekend plus a steady trickle of small fixes.” – hrmtst93837
- “It could be abandoned. That happens frequently with DevRel projects.” – spankalee

These four themes capture the main concerns and viewpoints circulating in the discussion.

🚀 Project Ideas

Google Auth Simplifier

Summary

  • Provides a one‑click OAuth flow for any Google account (personal or Workspace) without requiring a GCP project or console setup.
  • Stores tokens locally, auto‑refreshes, and exposes a simple gauth login command that works out of the box.
  • Eliminates the “create OAuth client” pain point that frustrates 70% of users.

Details

Key Value
Target Audience Developers, AI agents, sysadmins who need quick access to Google APIs
Core Feature Device‑flow OAuth, automatic client‑ID creation via Google API, token caching
Tech Stack Rust (for speed), reqwest, serde, clap, dirs, open
Difficulty Medium
Monetization Hobby

Notes

  • HN commenters complain: “I had to create an app, add 85 scopes, verify… it took hours.” (e.g., virgildotcodes, sbinnee).
  • A single gauth login command would satisfy the “3‑click install” desire and reduce friction for agents and humans alike.

Static Google Workspace CLI

Summary

  • A lightweight, statically‑generated CLI that bundles the most common Google Workspace API commands (Sheets, Docs, Drive, Calendar) into a single 10 MB binary.
  • No dynamic discovery; commands are pre‑compiled, fully documented, and include shell completion.
  • Solves the “750 MB npm install” and “dynamic command surface” pain points.

Details

Key Value
Target Audience Teams with limited bandwidth, CI/CD pipelines, AI agents needing deterministic commands
Core Feature Pre‑generated command set, auto‑completion, minimal dependencies
Tech Stack Go (static binaries), cobra, viper, google-api-go-client
Difficulty Medium
Monetization Revenue‑ready: freemium with paid enterprise support

Notes

  • Users like tonymet and m8s lament the huge install size and lack of static docs.
  • A small binary with clear help (--help) would be a “killer use case” for agents and humans alike.

DocsSync

Summary

  • A git‑style sync tool for Google Docs, Sheets, Slides, and Forms that pulls files into a local folder, lets you edit them as plain files (Markdown, CSV, JSON), and pushes changes back.
  • Maintains version history with the user’s identity, enabling agent‑driven edits without breaking Google’s audit trail.
  • Addresses the frustration of “editing Google Docs via API is error‑prone” (e.g., ksri, sothatsit).

Details

Key Value
Target Audience Knowledge‑base teams, AI agents, developers needing programmatic document editing
Core Feature Pull/push workflow, format conversion, per‑file change tracking
Tech Stack Rust (performance), google-drive-rs, serde, pulldown-cmark, csv, open
Difficulty High
Monetization Revenue‑ready: SaaS tier for enterprise audit logs and SSO

Notes

  • Commenters like ksri and sothatsit already use similar internal tools; an open‑source version would spark discussion and adoption.
  • The “git‑like” metaphor resonates with HN’s love for version control and agent‑friendly workflows.

Google CLI Hub

Summary

  • A meta‑CLI that installs, updates, and orchestrates multiple Google service CLIs (gws, gdoc, gsheet, gdrive, etc.) from a single command.
  • Handles authentication once, shares tokens, and provides unified help and auto‑completion across services.
  • Solves the “install each CLI separately, manage multiple auth flows” frustration.

Details

Key Value
Target Audience DevOps, AI agents, teams using multiple Google services
Core Feature One‑click install (gcli install all), shared auth, version pinning, update checker
Tech Stack Node.js (cross‑platform), pkg, inquirer, node-fetch, googleapis
Difficulty Medium
Monetization Hobby

Notes

  • Users like varenc and bigstrat2003 complain about installing each CLI via npm or curl; a single hub would streamline the experience.
  • The hub could expose a REST endpoint for agents, turning it into a lightweight “CLI‑as‑a‑service” for Google APIs.

Read Later