Prompt snippets

Overview

This topic explains how to use prompt snippets to create, manage, and reuse prompts across AgentControl config variations.

Prompt snippets are reusable, versioned pieces of prompt text that you manage as standalone resources in LaunchDarkly. Snippets let you define prompt content one time and reuse it across configs and variations.

Create and manage snippets in the Library, and reference them inside variation messages to reuse prompt content. The centralized snippets library helps you maintain consistency across config variations and quickly find a snippet you wish to use again. Snippet versioning lets you update prompt content without losing earlier versions of each snippet.

Use prompt snippets to:

• Reduce duplicated prompts across config variations
• Define and reuse prompt content such as tone, formatting, or governance language
• Identify which configs and variations use a specific snippet
• Track updates to prompt content by version
• Maintain prompt consistency across teams

How prompt snippets work

Each snippet has a name, key, and prompt content, along with versioning information and metadata such as tags, description, and maintainer. You reference snippets using their key and version. When LaunchDarkly evaluates a variation, it resolves these references and returns the fully assembled prompt.

These fields determine how you reference, update, and organize snippets:

• The key identifies the snippet and lets you reference it in variation messages
• The version lets you update prompt content without affecting existing variations
• Metadata helps you organize snippets across your project

Snippets are included as part of a config variation’s message body. When LaunchDarkly evaluates a variation, it replaces the reference with the snippet content and returns the fully assembled prompt to your application. A single message can include multiple snippet references along with other prompt content.

Core functions of prompt snippets

Prompt snippets’ core functions include:

• Editing a snippet creates a new version instead of modifying the existing one
• Config variations reference a specific snippet version
• Updating a snippet does not automatically update variations
• Snippets cannot reference other snippets

These behaviors let you update prompt content safely, review changes before applying them, and keep existing variations stable until you choose to update them.

You manage prompt snippets from the Library under AI. The snippets library provides a centralized place to create, view, and update reusable prompts across your project.

View snippets

Use the snippets list in the library to browse, search, and manage snippets across your project.

The snippets list provides a centralized view of all prompt snippets, so you can review existing content, identify reusable snippets, and understand how snippets are organized.

From the snippets list, you can:

• View all snippets in your project in a centralized list
• Search for snippets by name, key, or content
• View snippet details, including versions and usage

Create a snippet

Create a snippet to define reusable prompt content that you can reference across config variations. Use snippets for shared content such as tone, formatting, or common instructions.

To create a snippet from the Snippets tab:

1. Navigate to your project.
2. In the left navigation, click Agents. The AgentControl menu appears.
3. Click Library.
4. Select the Snippets tab. The snippets list appears.
5. Click New snippet. The “Save snippet” dialog appears.
6. Enter a name for the snippet. The snippet’s key auto-populates based on the name.
7. (Optional) Add a description to help others understand when to use this snippet.
8. In the “Body” field, enter the prompt text you want to save as a snippet.
9. (Optional) Click the tag icon to add tags to organize snippets across your project.
10. Click Create.

New snippets appear in the library’s “Snippets” tab.

You can also create a snippet inline while editing a variation message. To create a snippet this way, read Use snippets in config variations.

Snippet versioning

New snippets start at version 1. When you edit a snippet, LaunchDarkly creates a new version of that snippet instead of modifying the existing one. Previous versions remain available, so you can refer back to them or use them again if needed.

To edit a snippet, click the snippet in the snippets list. This opens the editing page, where you can update the snippet’s name, prompt content, and metadata.

Manage snippet usage and versions to understand where snippets are used and control how updates are applied across config variations.

Each snippet includes version history and usage information. Use this information to review how a snippet is used before updating variations to a new version. From the snippet list, you can view all config and variations that reference the snippet and see which version each variation is using. This helps you understand where a snippet is in use before making changes.

From a config variation, you can compare the current snippet version to the latest version and update the variation to use a newer version. Use this workflow to review how changes affect variations and update them individually as needed. This approach lets you apply changes intentionally and keep existing variations stable until you update them.

Compare snippet versions

You can view and compare versions of a snippet from the snippets list. Here’s how:

1. From the snippets list, find the snippet with versions you wish to view.
2. Click the version number in the “Versions” column. The “Version history” window appears.
3. Click Compare and select two versions to see a code diff of the changes between them.

Delete a snippet

Delete a snippet when you no longer need it and it is not used by any config variations. Here’s how:

1. From the snippets list, find the snippet you wish to delete.
2. Click snippet in the snippets list. The snippet detail page appears.
3. Click Delete. The snippet is deleted.

Before you delete a snippet, remove any references to it from config variations. LaunchDarkly prevents you from deleting snippets that are still in use.

Use snippets in config variations

You can use snippets in config variations in two ways:

• Attach existing snippets to a variation
• Create new snippets directly in variation messages

Attach snippets to a variation

Attach snippets from the variation editor to include reusable prompt content in a variation message.

To attach snippets to a variation:

1. Navigate to your config.
2. Select the Variations tab and open a variation.
3. There are three ways to use snippets in messages:

• Click the “Load prompt snippet” button in the variation message body toolbar to open search and find a snippet.
• In the variation message body, use the {{snippet.}} selector to open search and find a snippet.
• Reference a snippet directly using {{snippet.example-snippet-key#version-number}}.

4. Click Review and save.

Create inline snippets in messages

You can also create a snippet directly while editing a variation message.

To create snippets in a message:

1. Open a variation and begin editing the message content.
2. Click “Save as” in the variation message body toolbar.
3. Choose to either save the message body text as a New snippet or New version of existing snippet.

Behavior for in-use variations

You can use prompt snippets in variations that are part of active experiments or guarded rollouts.

If a variation that uses a snippet is part of an active experiment or guarded rollout, updating the snippet version may be blocked. LaunchDarkly blocks these updates to prevent changes that could affect experiment results or rollout behavior. If an update is blocked, LaunchDarkly provides details about the active usage, including which experiment or rollout is affected. Use this information to determine when to update the variation after it is no longer part of an active experiment or rollout.

Audit logs and access control

Prompt snippets use the same access control model as AgentControl configs, so you can manage access using existing roles and permissions. Access to create, update, and delete snippets follows the same permissions as other AgentControl resources.

LaunchDarkly records changes to snippets and their attachments in audit logs. These records show when snippets are created, updated, or attached to variations.

Permissions align with existing AgentControl actions. Audit log entries are created for snippet creation, updates, and changes to snippet attachments on variations.

Use audit logs to review changes to snippets and their attachments. This helps you track how snippets change over time and maintain control over changes across AgentControl config variations.