Manage LaunchDarkly feature flags, AgentControl Configs (AI agent prompts/models), experiments, guarded and automated rollouts, segments, metrics, dashboards, alerts, and observability data (logs, traces, errors, sessions) directly from chat. Create and target flags, run and analyze experiments, configure AI agent prompts and tools, build dashboards and alerts, and investigate production issues without leaving the conversation.
Also available as
How to use
- 1Add it in ChatGPT
Open LaunchDarkly in ChatGPT's Plugin directory (button above), select + to add it and sign in if asked.
- 2Use it in a chat
Type @ in the composer and pick LaunchDarkly, or start your message with its name. ChatGPT may also suggest it when it fits what you ask.
Skills 15
- agent-graphs
Create and manage agent graphs — directed graphs of configs connected by edges with handoff logic. Use when building multi-agent workflows where configs route to each other.
- alert-investigation
Investigates a triggered observability alert and returns a structured diagnosis with likely cause, scope, and next steps.
- apply
Apply LaunchDarkly SDK onboarding: install dependency (or dual-SDK pair), configure env and secrets with consent, add init at entrypoint(s), verify compile. Nested under sdk-install; next is run.
- built-in-metrics
Instrument an existing codebase with LaunchDarkly config tracking. Walks the four-tier ladder (managed runner → provider package → custom extractor + trackMetricsOf → raw manual) and picks the lowest-ceremony option that still captures duration, tokens, and success/error.
- configs-create
Create and configure configs in LaunchDarkly. Helps you choose between agent vs completion mode, create the config, add variations with models and prompts, and verify the setup.
- configs-targeting
Configure config targeting rules to control which variations serve to different users. Enable percentage rollouts, attribute-based rules, segment targeting, and guarded rollouts.
- configs-update
Update, archive, and delete LaunchDarkly configs and their variations. Use when you need to modify config properties, change model parameters, update instructions or messages, archive unused configs, or permanently remove them.
- configs-variations
Experiment with configs by creating and managing variations. Helps you test different models, prompts, and parameters to find what works best through systematic experimentation.
- create-fix-pr
Investigates a root cause and files a minimal fix PR for a reported bug or observability finding.
- create-graph
Creates observability dashboards and graphs from logs, traces, errors, sessions, metrics, and events data by previewing charts inline and saving them to a dashboard.
- custom-metrics
Create, track, retrieve, update, and delete custom business metrics for configs. Covers full lifecycle: define metric kinds via API, emit events via SDK, and query results.
- detect
Detect repository stack for LaunchDarkly SDK onboarding: languages, frameworks, package managers, monorepo targets, entrypoints, existing LD usage. Nested under sdk-install; next is plan.
- first-flag
Create a boolean first flag, add evaluation, toggle on/off for end-to-end proof. Parent onboarding Step 6; uses MCP, API, or ldcli; optional flag-create skill.
- flag-and-release-change
Drive a pull request's change end to end: decide it's flag-worthy, create the guarding flag, wire the new code path behind it on the PR branch, and record an automated release so the change ships safely when the PR merges. A portable orchestrator that composes should-flag-change, launchdarkly-flag-create, and flag-release. Keywords: flag a PR, wrap change in a flag, dark launch, kill switch, auto-release, automated rollout, end-to-end flag workflow.
- flag-release
Record an automated rollout for an existing LaunchDarkly flag that guards a pull request's change, so the change releases safely when the PR merges. Honors a stated release intent (release now / hold / notBefore / segment / prerequisite) and defers per-environment to the project's release policies. Use as the release step once the guarding flag exists and its code is wired. Keywords: record release, automated rollout, release policy, guarded rollout, staged rollout, simple vs policy, release intent, hold release, dark launch.
Things to ask
- “Find my stalest feature flags and open a PR removing the ones that are safe to delete.”
- “Create an AI Config for my support agent and roll it out to 10% of users.”