# Install gogcli with Homebrew Google Suite CLI. Version 0.34.1 via Homebrew; verified 2026-07-27. ## Install ```sh sudo av install brew:gogcli ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install gogcli ``` Evidence: provider-native install command ## Package facts - **Package key:** brew:gogcli - **Package manager:** Homebrew - **Version:** 0.34.1 - **Source summary:** Google Suite CLI - **Homepage:** - **Repository:** - **Last updated:** 2026-07-27T14:57:51+02:00 - **Generated:** 2026-08-03T00:40:33+00:00 ## Executables - gog (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.34.1 ## Project history and usage gogcli provides the gog command, a Go CLI for Google Workspace services. It is organized around task-first commands, automation-friendly output, and account-aware authentication. The project is young compared with classic Go tools, but its official spec is unusually explicit about why it exists: to replace separate Google service CLIs with one coherent command surface. ### Project history Repository history starts in December 2025 with an initial commit and early work unifying Google CLI authentication, services, and CI. Official docs describe the command as one binary for Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Meet, Apps Script, Analytics, Search Console, Contacts, Tasks, Classroom, Chat, YouTube, and Workspace admin. The spec states that gog replaces earlier separate CLIs named gmcli, gccli, and gdcli, plus a Python contacts server conceptually, without preserving legacy command names, flags, output formats, or state migration. ### Adoption history The official README emphasizes script, CI, and agent use through stable JSON/plain output, non-interactive mode, read-only mode, Gmail send blocking, and generated command schemas. That positions gogcli for automation rather than only interactive account administration. Package-manager facts in the input list Homebrew, Nix, Scoop, and winget entries. That spread fits a cross-platform personal and automation CLI where installation matters on macOS, Linux, and Windows workstations. ### How it is used The quickstart flow asks users to create a Google Cloud project, enable APIs, create a desktop OAuth client, store client credentials with gog auth credentials, authorize an account with gog auth add, and then run service commands such as gmail search or calendar events. The spec documents config.json under the per-user config directory, OAuth client credential JSON files, refresh tokens in OS keyring storage, and an encrypted file keyring fallback for headless or container environments. ### Why package nerds care gogcli is notable because it treats a personal productivity CLI like infrastructure: parseable stdout, documented exit behavior, non-interactive safety, generated command references, and a typed MCP server instead of a generic shell bridge. For package curators, it is also a good example of a CLI whose packaging story must include credentials and config locations. The binary is simple to install, but the operational state lives in platform config directories and keyrings. ### Timeline - 2025: Repository history begins with initial commits for a unified Google CLI. - 2025: v0.1.0 release tag appears in December. - 2026: Official docs describe task-first Google Workspace workflows, OAuth setup, generated command references, and a typed MCP server. - 2026: Releases continue through frequent 0.x tags as service coverage and automation behavior expand. ### Related projects - gmcli, gccli, and gdcli are named in the spec as separate CLIs that gog conceptually replaces. - Google Workspace APIs are the service surface behind the command set. - MCP is related through gog mcp, a typed server intended for agent clients. ### Sources - - - - ## Security Notes No matching local secret-handling manifest was found for gogcli. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: $(os.UserConfigDir())/gogcli/config.json ## Credential files - Unix: $(os.UserConfigDir())/gogcli/credentials.json, $(os.UserConfigDir())/gogcli/credentials-.json, $(os.UserConfigDir())/gogcli/keyring/ ## Combined YAML source View the package source record on GitHub. [combined/gogcli.yml](https://github.com/automic-vault/db/blob/main/combined/gogcli.yml) ## Sources - Nucleus package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation