Installer gogcli avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• gog

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

• 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

• https://github.com/steipete/gogcli
• https://gogcli.sh/
• https://gogcli.sh/quickstart.html
• https://gogcli.sh/spec.html