Integrations · LaunchDarkly
A Guild agent can read, create, update, and delete feature flags, user segments, approval requests, and audit log entries in LaunchDarkly on your team’s behalf. Guild stores the LaunchDarkly API key server-side and injects it through its credential proxy, so agent code never sees it. Credential policies let you restrict which operations and resources each agent may touch, and every call appears in Guild’s audit trail.
Book a demo
See how teams govern agents that use LaunchDarkly.
Talk to sales
Get access to Guild, then connect LaunchDarkly to your first agent.
What the LaunchDarkly integration exposes
The tools cover feature flags and their per-environment configurations, user segments, approval requests, scheduled changes, custom roles, team members, webhooks, data export destinations, integration subscriptions, relay proxy configs, access tokens, and usage metrics. Read tools fetch lists and individual records; write tools create, patch, copy, and delete them. Audit log tools retrieve both lists of entries and single entries by resource ID.How it works
1
Open credentials in Guild
Go to your account or organization and open Access & setup > Credentials. Click Connect to start.
2
Select and configure LaunchDarkly
Search for and select launchdarkly, then paste your LaunchDarkly API key into the API Key field.
3
Import tools into your agent
Import
LaunchdarklyTools from @guildai-services/guildai~launchdarkly and spread it into your agent’s tools object. Use pick() to include only the tools your agent needs.Why LaunchDarkly access needs governing
Feature flag changes affect production behavior immediately across every environment they touch. An agent that can delete a flag or modify targeting rules in a production environment can cause an outage. Guild’s credential proxy enforces credential policies before any request leaves Guild: DENY rules block specific operations or HTTP methods, and ALLOW rules can restrict access to named projects or environments. Policies can be scoped to individual agents or workspaces, so a triage agent gets read-only access while a release agent gets write access, all on the same connected credential. Credentials are stored and injected server-side; agents never receive the raw API key. You can scope a credential to one workspace, one member, or one agent using credential scoping, and Guild’s security architecture keeps the key out of agent code entirely. Without policies, the default posture is allow-all; deleting the allow-all policy switches the fallback to deny.About the LaunchDarkly integration
Agents can read, create, update, and delete feature flags and their configurations across projects and environments. They can manage team members, custom roles, webhooks, scheduled changes, and data export destinations. Usage metrics, audit log entries, and user targeting rules are also accessible. The integration isguildai~launchdarkly.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect LaunchDarkly
In Guild, go to Access & setup > Credentials, click Connect, select launchdarkly, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thelaunchdarkly_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~launchdarkly:
All 105 tools
All 105 tools
Frequently asked questions
Can an agent copy a flag configuration from one environment to another?
Can an agent copy a flag configuration from one environment to another?
Yes. The
launchdarkly_copy_feature_flag tool copies a feature flag’s configuration from one environment to the same flag in another environment within the same project.Does the integration support webhook event triggers from LaunchDarkly?
Does the integration support webhook event triggers from LaunchDarkly?
No. The catalog entry lists no webhook events for LaunchDarkly, so Guild cannot trigger an agent run from a LaunchDarkly event at this time.
How do I limit an agent to read-only flag access?
How do I limit an agent to read-only flag access?
Write a credential policy that allows only operations matching
launchdarkly_get_* or restricts the methods resource to GET, then scope that policy to the agent you want to limit.Can I give one agent a different LaunchDarkly account than the rest of my workspace?
Can I give one agent a different LaunchDarkly account than the rest of my workspace?
Yes. Connect a dedicated credential on the installed agent’s page or scope a credential to that agent alone. Guild resolves dedicated and granted credentials before the workspace or account default, as described in credentials.
Put a governed agent on LaunchDarkly this week
Book a demo
See how teams govern agents that use LaunchDarkly.
Talk to sales
Get access to Guild, then connect LaunchDarkly to your first agent.