Support

Start with the local checks. They separate credential, catalog, and Google API setup problems before you open an issue.

bash

gum doctor
gum auth status
gum search "gmail messages"
gum describe gmail.users.messages.list

Common paths

Problem	Start here
Install or PATH issue	`Install`
First API call	`Quickstart`
OAuth, API key, service account, or ADC setup	`Auth`
Service-specific Google setup	`Google Auth Guides`
Agent client configuration	`Agent setup`
Operation lookup	`Operations by service`
CLI flags	`Commands`

OAuth connection timeouts

If AUTH_REFRESH_FAILED reports a timeout at oauth2.googleapis.com/token, check network access before replacing credentials. A firewall can require a new approval after a Homebrew upgrade changes the executable's versioned path.

bash

command -v gum
gum --version
brew --prefix gum
gum auth probe --strategy byo_oauth --scopes datamanager

For a Homebrew installation, the executable is under the formula prefix at libexec/gum. Approve its HTTPS access to oauth2.googleapis.com and the API you intend to call, such as datamanager.googleapis.com. If the firewall needs interactive approval, wait until the operator is present, then retry the probe.

When the probe succeeds, repeat the validation-only request from the Data Manager guide.

Contributing

Contributor workflow lives in the README's development section. New Google API coverage should also follow Catalog ABI and the Test Matrix.