gog

name	gog
description	gog CLI: safe Google Workspace automation, JSON, auth, scoped reads/writes.

gog

Use gog when built-in Google connectors are missing a feature, when shell automation needs stable JSON, or when you need to inspect local Google auth state before acting.

Fast Path

gog --version
gog auth list --check --json --no-input
gog auth doctor --check --json --no-input
gog schema --json

Pick the account explicitly for API work:

gog --account [e-mail] gmail search 'newer_than:7d' --json --wrap-untrusted

Prefer --json --wrap-untrusted for agent parsing when reading Google content. Human hints and progress should stay on stderr; stdout is for data.

Safety Rules

• Do not print access tokens, refresh tokens, OAuth client secrets, or keyring passwords.
• If GOG_KEYRING_PASSWORD is provided by a shell startup file or service environment, use the matching shell/entrypoint so gog can unlock the file keyring non-interactively. Do not print the value.
• In headless/service agents, verify the service environment, not just the login shell. GOG_KEYRING_BACKEND=file, GOG_KEYRING_PASSWORD, and HOME must be present in the process that launches gog.
• Use --no-input in automation so auth/keyring prompts fail clearly.
• Use --dry-run first where commands support it.
• Destructive commands require --force; do not add it unless the user asked for that exact mutation.
• Use --gmail-no-send or GOG_GMAIL_NO_SEND=1 unless sending mail is the requested task.
• For shared agent environments, prefer a baked readonly or agent-safe binary from docs/safety-profiles.md.

Runtime command guards:

gog --enable-commands gmail.search,gmail.get --gmail-no-send \
  --account [e-mail] gmail search 'from:[e-mail]' --json

gog --enable-commands drive.ls,docs.cat --disable-commands drive.delete \
  --account [e-mail] drive ls --max 10 --json

Auth

OAuth setup is partly interactive. An agent can inspect and diagnose it, but a human normally completes browser consent:

gog auth credentials list
gog auth add [e-mail] --services all-user --force-consent
gog auth remove [e-mail]

Default for existing human/user OAuth reauth: preserve broad service access. Before reauth, run gog auth list --check --json --no-input and inspect the account's existing services. When replacing an expired or revoked token, do not silently reduce scope; prefer --services all-user --force-consent unless the user explicitly asks for narrower scopes.

Use narrow services only for throwaway/test accounts, service-specific bot accounts, explicit user requests, or scoped security experiments. Safety should normally be enforced at command time with --enable-commands, --disable-commands, --gmail-no-send, dry-runs, and account selection, not by under-scoping durable user auth.

Service accounts are Workspace-only and mainly fit Admin, Groups, Keep, and domain-wide delegation flows; they do not solve consumer @gmail.com OAuth.

For OpenClaw/systemd setups, run the diagnostic through the actual agent entrypoint after restarting the service:

openclaw agent --agent main --message \
  'Run: gog auth doctor --check --no-input && gog gmail search "newer_than:1d" --max 1 --json'

If this fails with keyring.password while the same gog auth doctor works in the shell, fix the service or agent environment before reauthenticating.

Remote Mac OAuth pattern:

1. Start the OAuth flow in remote tmux on the target Mac, for example gog auth add [e-mail] --services all-user --force-consent --timeout 15m.
2. Open the printed OAuth URL on that same Mac's Chrome with open -a "Google Chrome".
3. Drive the Google page on the target Mac with AppleScript/DOM clicks; keep the browser on the target host unless the user explicitly asks for a tunnel/local browser handoff.
4. If tmux asks for the file-keyring passphrase, source it from the remote login environment via zsh -lc and paste it into tmux without printing it.
5. Verify through zsh -lc 'gog auth list --check --json --no-input'.

Common Reads

gog --account [e-mail] gmail search 'newer_than:3d' --max 10 --json --wrap-untrusted
gog --account [e-mail] gmail get <messageId> --sanitize-content --json --wrap-untrusted
gog --account [e-mail] gmail thread get <threadId> --sanitize-content --json --wrap-untrusted

gog --account [e-mail] calendar events --today --json --wrap-untrusted
gog --account [e-mail] drive ls --max 20 --json --wrap-untrusted
gog --account [e-mail] docs cat <documentId> --json --wrap-untrusted
gog --account [e-mail] sheets get <spreadsheetId> Sheet1!A1:D20 --json --wrap-untrusted
gog --account [e-mail] sheets batch-update <spreadsheetId> --data-json @updates.json --json
gog --account [e-mail] contacts list --max 20 --json --wrap-untrusted

For Gmail body inspection, prefer --sanitize-content unless the user explicitly needs raw payloads.

Writes

Before writes, identify the account, object id, and exact mutation. Prefer commands that support --dry-run, and clean up disposable live-test objects.

gog --account [e-mail] docs write <documentId> --append --text '...'
gog --account [e-mail] sheets update <spreadsheetId> Sheet1!A1 --values-json '[["hello"]]'
gog --account [e-mail] sheets batch-update <spreadsheetId> --data-json @updates.json
gog --account [e-mail] drive upload ./file.txt --parent <folderId> --json

When testing creation commands, name artifacts with a clear temporary prefix and delete or trash them after verification.

For larger Sheets writes, prefer sheets batch-update over loops of sheets update; it sends multiple value ranges in one Sheets API request and accepts inline JSON or @file input.

Discovery

Use generated command docs and schema instead of guessing flags:

gog <service> --help
gog <service> <command> --help
gog schema <service> <command> --json

Docs:

• docs/index.md
• docs/commands/README.md
• docs/safety-profiles.md

Repo paths:

• CLI entrypoint: cmd/gog/
• Command implementations: internal/cmd/
• OAuth/keyring: internal/googleauth/, internal/authclient/, internal/secrets/
• Generated command docs: docs/commands/