> ## Documentation Index
> Fetch the complete documentation index at: https://authsome.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Google

> Log in to Google from authsome via OAuth2. Tokens are stored locally and refreshed automatically.

Google is a bundled OAuth2 provider in authsome. Gmail, Drive, Calendar, Sheets, Cloud Storage, and any service under `*.googleapis.com`. Authsome's `api_url` is a regex (`regex:.*googleapis.*`).

## At a glance

|                           |                           |
| ------------------------- | ------------------------- |
| Provider name             | `google`                  |
| Display name              | Google                    |
| Auth type                 | OAuth2                    |
| Default flow              | `pkce`, PKCE browser flow |
| PKCE supported            | Yes                       |
| Device code supported     | Yes                       |
| DCR supported             | No                        |
| Default scopes            | `openid`, `profile`       |
| Proxy host                | `regex:.*googleapis.*`    |
| Env var (`access_token`)  | `GOOGLE_ACCESS_TOKEN`     |
| Env var (`refresh_token`) | `GOOGLE_REFRESH_TOKEN`    |

## Prerequisites

You need to register an OAuth app with Google once. Create OAuth client credentials in the Google Cloud Console under APIs & Services. Pick "Desktop app" or "Web app" with the authsome callback URL.

The redirect URI must be:

```text theme={null}
http://127.0.0.1:7998/auth/callback/oauth
```

This is the only callback URL authsome's PKCE flow listens on.

Dashboard: [https://console.cloud.google.com/apis/credentials](https://console.cloud.google.com/apis/credentials).

## Log in

```bash theme={null}
authsome login google
```

The first time, authsome opens a local form at `http://127.0.0.1:7998` to collect your `client_id` and `client_secret`. They are encrypted in your vault and reused on every subsequent login. A second browser window then opens to `https://accounts.google.com/o/oauth2/v2/auth` for the authorization step.

Verify:

```bash theme={null}
authsome get google --field status
# → connected
```

## Headless setup

For SSH or CI environments, use the device code flow:

```bash theme={null}
authsome login google --flow device_code
```

See [Headless setup](/guides/headless-device-code) for the full flow.

## Custom scopes

The bundled definition requests `openid`, `profile`. Override at login time:

```bash theme={null}
authsome login google --scopes "<comma-separated>"
```

The granted scopes are stored on the connection and visible in `authsome get google`.

## Multiple accounts

Pass `--connection <name>` on `login` and on every read command to keep two or more accounts on the same provider side by side. See [Multiple connections per provider](/guides/multiple-connections) for the full pattern.

```bash theme={null}
authsome login google --connection personal
authsome login google --connection work
```

## Use the token

Run the agent under the proxy (recommended).

<CodeGroup>
  ```bash Proxy (recommended) theme={null}
  authsome run -- python my_agent.py
  ```

  ```bash Environment theme={null}
  eval "$(authsome export google --format env)"
  ```
</CodeGroup>

Under the proxy, authsome sets `GOOGLE_ACCESS_TOKEN=authsome-proxy-managed` in the child's environment and injects the real token into outbound requests to `regex:.*googleapis.*`. The child process never sees the actual value. Refresh tokens are never exported.

## Override the bundled definition

```bash theme={null}
authsome inspect google > ~/.authsome/providers/google.json
# edit scopes, base_url, or anything else
authsome list   # source now shows "custom" for google
```

User-registered files always win over bundled definitions.

## What's next

<Columns cols={2}>
  <Card title="Run agents with the proxy" icon="shield-halved" href="/guides/run-agents-with-proxy">
    Inject the access token into outbound requests without exposing it.
  </Card>

  <Card title="Multiple connections per provider" icon="users" href="/guides/multiple-connections">
    Keep two or more accounts on the same provider side by side.
  </Card>

  <Card title="OAuth providers" icon="right-to-bracket" href="/integrations/oauth/index">
    All bundled OAuth providers.
  </Card>
</Columns>