> ## 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.

# Discord

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

Discord is a bundled OAuth2 provider in authsome. User identity, guild membership, and connection info.

## At a glance

|                           |                                              |
| ------------------------- | -------------------------------------------- |
| Provider name             | `discord`                                    |
| Display name              | Discord                                      |
| Auth type                 | OAuth2                                       |
| Default flow              | `pkce`, PKCE browser flow                    |
| PKCE supported            | No                                           |
| Device code supported     | No                                           |
| DCR supported             | No                                           |
| Default scopes            | `identify`, `email`, `guilds`, `connections` |
| Proxy host                | `discord.com`                                |
| Env var (`access_token`)  | `DISCORD_ACCESS_TOKEN`                       |
| Env var (`refresh_token`) | `DISCORD_REFRESH_TOKEN`                      |

## Prerequisites

You need to register an OAuth app with Discord once. Create an application at the Discord developer portal, then add a redirect URI under OAuth2 settings.

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://discord.com/developers/applications](https://discord.com/developers/applications).

<Note>
  Discord's OAuth2 endpoint does not require PKCE. Authsome runs the standard authorization-code flow.
</Note>

## Log in

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

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://discord.com/oauth2/authorize` for the authorization step.

Verify:

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

## Custom scopes

The bundled definition requests `identify`, `email`, `guilds`, `connections`. Override at login time:

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

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

## 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 discord --connection personal
authsome login discord --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 discord --format env)"
  ```
</CodeGroup>

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

## Override the bundled definition

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

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>