macOS
Homebrewverified ยท 100%
brew install gogcliprovider-native install command
brew / rank 902
Install gogcli with Homebrew
Google Suite CLI. Version 0.34.1 via Homebrew; verified 2026-07-27.
install
Additional install commands
overview
Package summary
Google Suite CLI
Project links
Commands and aliases
- gog
history
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 posture
No protected-tool coverage found yet
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.
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
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
Config paths the tool may read or write during local use.
- Unix
$(os.UserConfigDir())/gogcli/config.json
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
$(os.UserConfigDir())/gogcli/credentials.json$(os.UserConfigDir())/gogcli/credentials-<client>.json$(os.UserConfigDir())/gogcli/keyring/
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
gog | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version0.34.1
manager updated2026-07-27
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:gogcli |
|---|---|
| Version | 0.34.1 |
| Package manager | Homebrew |
| Homepage | https://gogcli.sh |
| Repository | https://github.com/openclaw/gogcli |
| Last updated | 2026-07-27T14:57:51+02:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation