For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
      • Developer tools
        • LaunchDarkly CLI
        • LaunchDarkly MCP server
        • LaunchDarkly developer toolbar
        • LaunchDarkly agent skills
        • Vega
          • Connecting Vega to GitHub
          • Using Vega in Slack
        • IDE connectors and agents
      • Setting up an SDK
      • Joining an account
      • Using feature management
      • Getting started in different roles
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • How GitHub access works
  • Setting up the GitHub integration
  • When GitHub is required
Get startedGet startedDeveloper toolsVega

Connecting Vega to GitHub

Was this page helpful?
Previous

Using Vega in Slack

Next
Built with

Overview

Vega integrates with GitHub to read your code, make code changes, and open pull requests. Connecting GitHub is optional for using Vega investigate mode, but is required for fix mode and flag cleanup, both of which create pull requests.

To learn more about Vega, read Vega.

How GitHub access works

Vega’s GitHub access is scoped by both user and organization:

  • At the organization level, an admin installs the LaunchDarkly Vega GitHub App and selects which repositories Vega is allowed to access.
  • At the user level, each developer authenticates with their personal GitHub account.

The repositories Vega can access for a given user are the subset of repositories that user has access to, among the organization’s repositories that were granted access to Vega.

One GitHub organization per workspace

Currently, LaunchDarkly supports connecting one GitHub organization per workspace.

Setting up the GitHub integration

Vega may clone a connected repository

If you connect Vega to your GitHub account and you specify a repository when making a request, Vega may clone your repository code into an isolated environment to facilitate agent investigations.

To connect Vega to GitHub:

  1. Install the LaunchDarkly Vega GitHub App at the organization level.
  2. Authenticate with your personal GitHub account. This lets Vega act on your behalf by opening pull requests and reading from repositories you can access.
  3. Choose which repositories Vega can access. You can restrict Vega’s permissions to specific repositories. These access scopes apply across all modes and can be modified at any time from your GitHub organization’s settings.

All GitHub interactions are logged and scoped to your authenticated session. Vega will only operate within the repositories and permissions you’ve explicitly approved.

When GitHub is required

Vega featureGitHub required?
Investigate modeOptional (uses code context to improve analysis)
Fix modeRequired (creates pull requests)
Flag cleanupRequired (creates pull requests)
Search assistantNot used