Developer & CI · wired today
Drive LaunchDarkly with governed agents
Build, review and release state is where agents earn their keep. The LaunchDarkly connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against LaunchDarkly
| Tool | What it does |
|---|---|
list_projects | List LaunchDarkly projects the API access token can see |
list_flags | List the feature flags in one LaunchDarkly project, optionally filtered by tag |
get_flag | Get one LaunchDarkly feature flag by project key and flag key |
list_environments | List the environments in one LaunchDarkly project (keys and names only, never SDK or mobile keys) |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the LaunchDarkly connector needs
You provide API key from your LaunchDarkly account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: LaunchDarkly's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real LaunchDarkly API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
LaunchDarkly integration FAQ
What can Quox agents do with LaunchDarkly?
Agents can run 4 read-only tools against LaunchDarkly: list projects, list flags, get flag, list environments. Every call is receipted in the evidence trail.
What does the LaunchDarkly integration need?
You provide API key from your LaunchDarkly account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my LaunchDarkly credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the LaunchDarkly connector?
This connector was blind shape-proven against the real LaunchDarkly API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.