Kepler Documentation

Pull Request Integrations

Last updated: June 2026

Overview

Kepler (GitKraken’s Agentic Development Environment, or ADE) connects to your Git hosting platform so you can create a Task directly from an existing pull request. This lets an agent address review comments or begin a code review without manual setup.

Supported providers

Provider Auth method Self-hosted support
GitHub OAuth No
GitHub Enterprise Personal Access Token Yes
GitLab OAuth No
GitLab Self-Managed Personal Access Token Yes
Bitbucket OAuth No
Azure DevOps OAuth No

When you connect a PR, Kepler pulls the following from it:

  • Diff
  • Description
  • Open review comments
  • Current review state

GitHub

Prerequisites

  • A GitHub account with at least read access to the repository.

Connect GitHub

  1. In Kepler, open Settings and navigate to Integrations.
  2. Under GitHub, click Connect.
  3. Authorize Kepler in the GitHub OAuth window that opens.
  4. After authorization, GitHub is now connected in Integrations.
GitHub shown as connected in Kepler Integrations settings
GitHub connected in Kepler Integrations

GitHub Enterprise

Prerequisites

  • A GitHub Enterprise account with at least read access to the repository.
  • A Personal Access Token (classic) with the repo scope, or a fine-grained token with Contents (read) and Pull requests (read) permissions.

Connect GitHub Enterprise

  1. In Kepler, open Settings and navigate to Integrations.
  2. Under GitHub Enterprise, click Connect.
  3. Enter your GitHub Enterprise Host URL (for example, https://github.example.com).
  4. Paste your Personal Access Token.
  5. Click Save.
GitHub Enterprise connection form in Kepler showing host URL and token fields
GitHub Enterprise connection form in Kepler

GitLab

Prerequisites

  • A GitLab account with at least Reporter access to the project.

Connect GitLab

  1. In Kepler, open Settings and navigate to Integrations.
  2. Under GitLab, click Connect.
  3. Authorize Kepler in the GitLab OAuth window that opens.
  4. After authorization, GitLab is now connected in Integrations.
GitLab shown as connected in Kepler Integrations settings
GitLab connected in Kepler Integrations

GitLab Self-Managed

Prerequisites

  • Access to a GitLab Self-Managed instance with at least Reporter access to the project.
  • A Personal Access Token with the read_api and read_repository scopes.

Connect GitLab Self-Managed

  1. In Kepler, open Settings and navigate to Integrations.
  2. Under GitLab Self-Managed, click Connect.
  3. Enter your GitLab Self-Managed Host URL (for example, https://gitlab.example.com).
  4. Paste your Personal Access Token.
  5. Click Save.
GitLab Self-Managed connection form in Kepler showing host URL and token fields
GitLab Self-Managed connection form in Kepler

Bitbucket

Prerequisites

  • A Bitbucket account with at least read access to the repository.

Connect Bitbucket

  1. In Kepler, open Settings and navigate to Integrations.
  2. Under Bitbucket, click Connect.
  3. Authorize Kepler in the Bitbucket OAuth window that opens.
  4. After authorization, Bitbucket is now connected in Integrations.
Bitbucket shown as connected in Kepler Integrations settings
Bitbucket connected in Kepler Integrations

Azure DevOps

Prerequisites

  • An Azure DevOps account with at least Reader access to the project.

Connect Azure DevOps

  1. In Kepler, open Settings and navigate to Integrations.
  2. Under Azure DevOps, click Connect.
  3. Authorize Kepler in the Azure DevOps OAuth window that opens.
  4. After authorization, Azure DevOps is now connected in Integrations.
Azure DevOps shown as connected in Kepler Integrations settings
Azure DevOps connected in Kepler Integrations

Have feedback about this article? Did we miss something? Let us know!
On this page