Google Workspace in your terminal.
Despite being only ~5 months old (created 2025-12-12), the project is at v0.16.0 with a release as of 2026-05-10 — demonstrating rapid, structured versioning cadence rather than ad-hoc tagging. The release history implies deliberate milestone cuts. Sub-1.0 by convention, but behaviorally this reads as a solid late-beta: only 7 open issues against 7361 stars signals effective triage. Not yet 1.0, so one point withheld for that and the relative youth of the codebase.
Exceptional. The README alone covers install (Homebrew, Docker, Windows ZIP, source), quickstart, all auth modes (OAuth, ADC, service accounts, direct access tokens), daily command examples across 15+ Google surfaces, and links to rendered docs at gogcli.sh. Beyond the README: per-command generated reference docs, feature guides for Gmail workflows, Drive audits, contacts dedupe, Docs editing, sed-style document edits, email tracking, and Pub/Sub watch flows. The pattern of separating stdout (data) from stderr (hints/progress) is documented explicitly for script and agent consumers — a rare level of tooling literacy in docs.
Go is the right language for a script-friendly CLI: single static binary, fast startup, excellent concurrency for parallel API calls. The design choices are strong: predictable --json / --plain flags, --sanitize-content for agent-safe output, --gmail-no-send safety guards, runtime allowlist/denylist baking — these are not afterthoughts. No dependency manifest was available for inspection, so direct dependency hygiene cannot be scored. No explicit CI badge or test-presence signal in the README, which costs one point.
Last commit was 2026-05-11 — the day before this appraisal. Latest release was 2026-05-10. The gap between open issues (7) and stars (7361) implies either rapid close-out or very clear scope boundaries. Someone is very much home.
7,361 stars and 566 forks accumulated in ~5 months is a strong trajectory signal — this is not a slow-burn project. Forks-to-stars ratio (~7.7%) is healthy and suggests downstream scripting and customisation rather than passive bookmarking. No visible downstream dependents or package registry data available, which caps the score.
Overall: 4.4/5
Category: Google Workspace CLI
Known alternatives in vault: None. No other Google Workspace tooling appears in the landscape summary.
Differentiation: gogcli is unusually broad — it covers Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Meet, Apps Script, Analytics, Search Console, Contacts, Tasks, Classroom, Chat, YouTube, and Workspace admin flows from a single binary with unified auth. Alternatives like gcalcli (Calendar only) or gam (admin-focused) are narrower. The explicit agent-safety features (--sanitize-content, no-send guards, read-only audit modes, allowlist/denylist baking) and the stdout/stderr discipline distinguish it from informal wrapper scripts. The support for ADC and Workspace service accounts alongside consumer OAuth is a rare combination. No vault alternative does any of this.
Gap or crowd: Clear gap. This is the first and only Google Workspace CLI in the vault. No crowding risk.
Score: 4/5
Harvestable: The stdout/stderr discipline pattern (data on stdout, hints on stderr) is directly reusable in any PAI tool-execution layer. The --sanitize-content flag demonstrates a clean approach to LLM-safe content extraction worth copying in other data-harvesting tools. The runtime allowlist/denylist safety-profile binary concept is a useful pattern for sandboxing tool calls in agent pipelines. The contact deduplication logic and Drive inventory/audit patterns are reusable for knowledge-graph ingestion workflows.
Integration path: gogcli fits naturally as a PAI tool-layer executable: wire gog gmail search → email triage skill, gog calendar events --today --json → daily briefing hook, gog drive changes list → knowledge-vault change feed, gog contacts search → people-resolution skill. The JSON output makes downstream parsing trivial in any orchestrator. A PAI system could call it directly via subprocess with no wrapping library needed.
Overlap with existing: No overlap with any repo currently in the vault. The landscape shows no Google-adjacent tooling.
Adoption cost: Moderate. Requires: (1) Google Cloud project setup with enabled APIs, (2) OAuth client configuration, (3) per-account gog auth add flow, (4) optional service-account setup for Workspace domains. Once auth is configured, individual skill integrations are trivial — each is a gog <service> <subcommand> --json call. The Docker path with a persistent config volume reduces per-machine setup cost for CI/agent environments.
This is the most immediately actionable data-source tool appraised so far. Every major Google surface a personal knowledge vault would need to harvest — email, calendar, contacts, drive files, docs — is covered with a consistent, LLM-friendly interface. The explicit call-out in the README to "coding agents" and the --sanitize-content flag confirm the authors are deliberately targeting AI orchestration use cases, not just human terminal use. The 5-month age is the only meaningful risk: OAuth scope handling, token refresh edge cases, and rate-limit behaviour on long-running harvests are areas where a younger tool may still have rough edges. At v0.16.0 and with this commit cadence, those edges are likely being filed down quickly. Strongly recommended for vault inclusion; no close alternatives exist in the current collection.