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

# GitLab

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

GitLab is a bundled OAuth2 provider in authsome. Project and repository access on GitLab.com and self-hosted GitLab instances.

## At a glance

|                           |                                                                               |
| ------------------------- | ----------------------------------------------------------------------------- |
| Provider name             | `gitlab`                                                                      |
| Display name              | GitLab                                                                        |
| Auth type                 | OAuth2                                                                        |
| Default flow              | `pkce`, PKCE browser flow                                                     |
| PKCE supported            | Yes                                                                           |
| Device code supported     | No                                                                            |
| DCR supported             | No                                                                            |
| Default scopes            | `api`, `read_user`, `profile`, `email`, `read_repository`, `write_repository` |
| Proxy host                | `gitlab.com`                                                                  |
| Env var (`access_token`)  | `GITLAB_ACCESS_TOKEN`                                                         |
| Env var (`refresh_token`) | `GITLAB_REFRESH_TOKEN`                                                        |

## Prerequisites

You need to register an OAuth app with GitLab once. Create an application under your GitLab user settings (or group / instance admin for self-hosted), set the redirect URI to authsome's callback, and copy the application ID and secret.

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://gitlab.com/-/user\_settings/applications](https://gitlab.com/-/user_settings/applications).

## Log in

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

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

Verify:

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

## Custom scopes

The bundled definition requests `api`, `read_user`, `profile`, `email`, `read_repository`, `write_repository`. Override at login time:

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

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

## Self-hosted instances

For self-hosted GitLab, pass the base URL:

```bash theme={null}
authsome login gitlab --base-url https://gitlab.acme.com
```

The base URL is saved on the connection and reused for every token refresh.

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

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

## Override the bundled definition

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

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>