Last updated: March 2026
Use this page to connect GitKraken Desktop to GitLab.com for repository access, SSH setup, clone and remote workflows, and pull request activity. It also explains the public-repository limitation on the Community plan and how multiple GitLab accounts are handled through profiles.
Requirements and limits
- Integration covered here: GitLab.com
- Community plan limit: Public repositories only
- Authentication options: Browser-based GitLab connection or manual OAuth token entry
- Account limit: One GitLab account per profile; multiple accounts require multiple profiles and a GitKraken Pro subscription
- SSH behavior: GitKraken uses the key in Preferences > SSH unless you configure a GitLab-specific key or enable your local SSH Agent
| Workflow | Supported | Community limit | Notes |
|---|---|---|---|
| Connect GitLab.com account | Yes | None | Browser-based connection or manual OAuth token entry |
| Clone and browse repositories | Yes | Public repositories only | Private repository access requires a paid plan |
| SSH key generation and upload | Yes | Public repositories only | Uses GitKraken SSH settings unless overridden |
| Create and manage pull requests | Yes | Public repositories only | Supported directly in GitKraken Desktop |
| Multiple GitLab accounts | Yes | Not included | Requires separate profiles and a Pro plan |
Quick Start
- Go to Preferences > Integrations in GitKraken Desktop.
- Select GitLab.com and click Connect to GitLab.
- Log in to GitLab in the browser window that opens, then click Open GitKraken to complete the connection.
To configure SSH access after connecting:
- In Preferences > Integrations, click Generate SSH key and add to GitLab to generate and upload a key automatically.
- Or click Add key to GitLab to upload your existing SSH default.
Once connected, GitKraken Desktop displays your GitLab repositories when cloning, shows forks when adding remotes, and supports creating and managing pull requests from within the application. To manage more than one GitLab account, use multiple profiles with a GitKraken Pro plan.
What the GitLab integration lets you do
- Create new repositories on your GitLab account with optional .gitignore and license templates.
- Automatically generate and upload an SSH key pair to GitLab.
- Clone repositories directly from your GitLab repo list.
- Easily identify GitLab repos via remote avatars on the graph.
- Add remotes to GitLab repositories.
- Create and manage pull requests from within GitKraken.
- Work with GitLab Issues alongside your code.
Note: The GitKraken Community plan only supports public repositories.
How to connect the GitLab integration
To authenticate with GitLab:
Use the browser-based GitLab connection when: standard GitLab OAuth access is available and you want the simplest setup. Use a manual OAuth token when: your environment requires token-based access or you need to paste a token directly into GitKraken Desktop.
- Open Preferences > Integrations from the upper-right corner.
- In the integration window, select GitLab.com and click .
- Log in via your default browser. After successful authentication, click Open GitKraken to complete the connection.
You may also connect manually using an OAuth token.
How to generate an SSH key for GitLab
Note: GitKraken uses the SSH key listed in Preferences > SSH unless you configure a GitLab-specific key or enable your local SSH Agent.
Once GitLab is connected, you can generate a new SSH key or upload an existing one:
- Click to automate the process.
- Use to use an existing SSH Default.
- Use Add existing SSH key to upload your own key manually.
What GitLab OAuth enables in GitKraken Desktop
With GitLab connected, GitKraken enhances your workflow with features such as:
Use the GitLab integration when: you want cloning, remotes, pull requests, and issue workflows tied directly to GitLab.com inside GitKraken Desktop. Don’t use this page when: you need self-hosted GitLab guidance, which belongs on the self-managed GitLab integration pages.
- Browsing your GitLab repositories during cloning:
- Viewing forks when adding remotes:
You can still manually enter repository URLs if preferred.
How to connect multiple GitLab accounts
GitKraken supports one GitLab account per profile. With profile support in GitKraken Pro, you can switch between multiple GitLab accounts easily.
Use multiple profiles when: you need to switch between separate GitLab identities or organizations cleanly. Don’t use multiple profiles when: one GitLab account already covers the repositories you need and profile switching would add unnecessary overhead.
