gog Google Workspace CLI

Problem

When Gmail, Calendar, Drive, Contacts, Sheets, and Docs are spread across browser UIs, batch queries, exports, updates, and scriptable workflows become awkward. gog moves these Google Workspace operations into a command-line path suited to terminals, CI, automation, and agent workflows, rather than manual page clicks.

Core Capabilities and Workflow

The skill is organized around OAuth setup and common operations. It expects a Google OAuth client secret and grants a specified email access to Gmail, Calendar, Drive, Contacts, Sheets, and Docs. Afterwards, commands cover Gmail search and send, Calendar event queries, Drive keyword search, Contacts listing, Sheets cell reads, updates, appends, clears, and metadata, plus Docs export and content viewing. For scripting, prefer --json and --no-input, and pass Sheets values with --values-json to reduce parsing ambiguity.

Boundaries

It is useful for explicit read, search, spreadsheet write, and document export tasks, but it is not a full Google API client. Docs supports export, cat, and copy; in-place edits require an additional Docs API client. Mail sending and event creation should be confirmed before execution to avoid unintended automation. GOG_ACCOUNT can reduce repeated account flags, but multi-account, permissions, and OAuth configuration still require manual maintenance.