gog (Google Workspace CLI)

A per-service API-enablement gotcha in gog, the CLI wrapping Gmail/Calendar/Drive/Sheets/Docs — hit while trying to pull reference images from a Google Drive folder.

Dogfooded 2026-08-15 on a real task: Gavin asked for four Krea-2 LoRA images per playbook, sourced from a Google Drive folder of playbook docs. mcp__gogcli__drive_search against that folder failed outright.

Goals

Use gog's Drive integration (drive_search/drive_get) to pull reference content straight from a shared Drive folder, the same way Gmail search and Calendar already work reliably for this account.

Effectiveness

Not adopted (for Drive specifically) — blocked before it started. The call returned exit code 6 with a plain-English fix pointer: "Drive API is not enabled for this OAuth project," with a direct console link to enable it. Gmail, Calendar, and the rest of gog's surface have been solid for months on this same account; Drive was simply never switched on for the OAuth client backing it.

What made it effective

The failure mode itself was well-behaved: a clear exit code, a human-readable stderr message, and a working console URL to fix it — no guessing, no stack trace archaeology. That's the bar every CLI in this workspace gets held to, and gog cleared it even while blocked.

Friction, pain points, surprises

Per-service enablement is a hidden setup step. Getting Gmail/Calendar working earlier didn't imply Drive would work too — each Google API has to be individually enabled for the OAuth project in Cloud Console, and there's no single "enable everything gog needs" step. Re-confirmed on retry the next day (2026-08-16): still blocked, same message, same project ID (690728802103) — this needs a one-time manual click in Cloud Console before drive_search/drive_get become usable at all.

Blocked a real task, not just a curiosity check. The playbook-image job stalled entirely on this — no images generated, no fallback content pulled — until Gavin either enables the API or pastes the playbook text in directly. Flagging it here (and to Gavin directly) rather than silently working around it, since there isn't a good workaround: the content genuinely lives in that Drive folder.