Vega

Overview

Vega is LaunchDarkly’s AI-powered agent that works across the platform to help you investigate issues, fix bugs, and manage feature flags. Unlike general-purpose AI assistants, Vega is integrated into LaunchDarkly’s feature management and observability platform and has access to your flags, environments, telemetry, and code to deliver context-aware responses.

Vega is powered by Anthropic’s Claude models. When you ask Vega a question or invoke it from a specific view, it accesses relevant data to reason about what’s happening, identify causes, and take action.

Vega capabilities

Vega has two primary capability areas:

• Vega for auto-remediation: An AI debugging assistant embedded in observability views. Vega investigates logs, traces, errors, and alerts, summarizing what happened and identifying causes. If you connect Vega to GitHub, it can suggest or open fixes. Vega can also run automatically when alert thresholds are breached.

• Vega for flag cleanup: Vega can identify stale feature flags and safely remove them from your codebase. Click a button on any flag, and Vega determines whether it’s safe to remove, then creates a GitHub PR with the code changes.

Eligibility

Vega is available to all self-serve customers on a usage-based pricing plan and to select enterprise customers. If you are an enterprise customer and want to know whether you have access, contact your account owner. Eligible enterprise customers will see AI terms that can be accepted by workspace creators or owners.

Roles and RBAC

To use Vega your role requires the Vega actions. The Admin and Owner base roles include Vega access by default. For all other roles, an administrator must explicitly add the talkToVega action to a custom role to grant Vega access to members. To learn more about custom roles, read Custom roles.

When Vega accesses LaunchDarkly resources on your behalf, it respects your existing role permissions. For example, if Vega investigates a session replay or reads log data, it can only access resources that your role allows. If your role does not include the viewSession or viewLog actions, Vega cannot access that data either.

You can:

• Allow or deny Vega access for specific teams, projects, or environments.
• Limit which users can connect or authorize GitHub integrations.
• Configure whether users can invoke Vega in investigate or fix modes.

This helps ensure Vega can only be used by authorized developers with clearly defined permissions for both observability data and code access.

To connect Vega to GitHub, read Connecting Vega to GitHub.

Customizing Vega with repository instructions

When Vega accesses a connected GitHub repository, it reads any CLAUDE.md or AGENTS.md files in the root of the repository. These files give Vega context about your codebase, such as architecture decisions, coding conventions, important file paths, or areas to avoid.

If you want Vega to produce better results when investigating issues or cleaning up flags in your repository, add a CLAUDE.md or AGENTS.md file with relevant instructions. For example:

• Describe your project structure and key directories
• Note any conventions for how feature flags are used in your codebase
• Specify files or patterns that should not be modified
• Provide context about your deployment process or environment setup

Vega uses these instructions to make more informed decisions when analyzing code and creating pull requests.

To learn more, read Using CLAUDE.MD files or Agents.md.