What makes experimentation with LaunchDarkly stand out among other tools on the market?
What makes experimentation with LaunchDarkly stand out among other tools on the market?
What makes experimentation with LaunchDarkly stand out among other tools on the market?
We've rebuilt the flag list page to make it faster to scan and easier to action:
These changes will roll out to customers in phases over the next week (Aug 11-14 2026).
Share link copied!
Agent Optimization is now available in public beta, giving teams a systematic way to improve their AI agents by running iterative optimization passes across models, configurations, and prompts - and deploying the best-performing result directly from LaunchDarkly.
Agent Optimization lets teams run structured optimization experiments against their AI agents to find the best-performing configuration. Rather than manually tweaking prompts and models and guessing at what works, teams can configure an optimization run that systematically tests variations across models and prompt strategies, evaluates each result using a judge model, and surfaces the winner so it can be deployed immediately.
Agent Optimization works with the LaunchDarkly Python AI SDK and integrates with popular agent frameworks. Configurations can be managed entirely in the AgentControl UI and pulled at runtime, or defined inline in code without any UI setup required.
To get started, read the Agent Optimization documentation.
Our team is happy to walk you through using Agent Optimization. To get help or share feedback, contact your LaunchDarkly account team or email product@launchdarkly.com.
Share link copied!
Know exactly which customer is driving your AI cost, latency, and usage. You can now filter and group AgentControl monitoring by context kinds, so you can see tokens, cost, latency, generations, and satisfaction for a single tenant, a single user, or any slice of your traffic, instead of only the global average.
Global averages hide what individual customers experience. One power user can drive far more token spend than a typical user, and that difference disappears in the aggregate. Now you can attribute cost and latency to the customer causing them, debug one tenant's behavior in minutes, and understand how usage differs across your customer base without writing custom queries against raw data.
What you can do:
Compare customers side by side. Group the dashboard by user, organization, or an attribute like plan tier to see how different customers use your AI features.
Zoom in on one customer. Filter to a tenant, a department, or a specific user and every chart and table follows. Search works even with thousands of customers.
Take the data with you. CSV export matches whatever you have filtered or grouped on screen.
To get started, open a config's Monitoring tab and use the filter and Group by controls. Learn more about monitoring config performance.
Share link copied!
LaunchDarkly Terraform provider v3 is now generally available. This release is a major rebuild on the newer Terraform Plugin Framework, replacing the older v2 SDK foundation and setting the provider up to support new LaunchDarkly capabilities more quickly.
With v3, teams can manage more of their LaunchDarkly configuration in Terraform, including eight new resources: Context Kinds, Release Policies, Metric Groups, Announcements, Big Segment Stores, OAuth Clients, Integration Delivery, and Flag Import.
This release also improves plan-time validation, helping teams catch some configuration issues earlier in the workflow instead of discovering them only at apply time.
For customers using approval workflows and role mappings, v3 adds support for segment approval settings on environments and scoped role attributes on team role mappings.
Because v3 includes breaking syntax changes, existing v2 configurations will need updates before they plan cleanly against v3. To help with that transition, v3 includes a migrate-tf-syntax command to rewrite Terraform configuration from v2 syntax to v3 syntax, and provider state upgrades are handled automatically on first apply without requiring destroy-and-recreate workflows.
More information on migrating from v2 to v3 can be found here.
Share link copied!
You can now define a Ratio Metric with a specific numerator and denominator aggregation. Ratio Metrics have two primary use-cases:
See our documentation to learn more and get started.
Share link copied!
