For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
      • Creating new flags
      • Flag types
      • Turning flags on and off
      • Creating flag variations
      • Cloning existing flags
      • Importing flags
      • Flag settings
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
Feature flagsCreate flags

Cloning existing flags

Was this page helpful?
Previous

Importing flags

Next
Built with

Overview

You can create new flags by cloning existing flags. When you clone a flag, LaunchDarkly makes a new flag and copies the original flag’s targeting configuration for all environments, including default values and whether the flag is toggled on or off. You can then modify the clone’s configuration if needed.

To clone a flag:

  1. In the left navigation, click Code. The CodeControl menu appears.

  2. Click Flags.

  3. Open the flag you wish to clone.

  4. Click the three-dot overflow menu in the right sidebar.

  5. Select Clone this flag.

  6. The “Clone feature flag” dialog appears:

    The "Clone feature flag" dialog.

    The "Clone feature flag" dialog.
  7. Enter a unique, human-readable Name.

  8. (Optional) Update the unique flag Key. You’ll use this key to reference the flag in your code. A suggested key auto-populates from the name you enter, but you can customize it if you wish.

  9. (Optional) Enter a Description of the new flag. A brief, human-readable description helps your account members understand what the flag is for.

  10. (Optional) Add the flag to one or more Views.

  11. (Optional) Click into the Tags menu and choose one or more tags for your flag.

Tags sort flags into groups

Use tags to group related flags so your team can find them more easily.

For most access-control use cases, use views to scope access within a project. To learn more, read Onboarding to views.

  1. Click Save flag. The Targeting tab for the new flag opens.

The new flag appears in the Flags list.

Restrictions on rollouts

If the flag you are cloning has an active guarded rollout or progressive rollout, the rollout is not cloned.

You can also use the REST API: Copy feature flag