Configs Create

50 chapters · 232 min

⚠️ This skill creates a config — it does not make it servable. A freshly-created config has its fallthrough pointing at an auto-generated disabled variation, not at the variation you just created. The SDK will return ai_config.enabled=False on every evaluation until you flip targeting on and point the fallthrough at your new variation. This is not a bug — it’s the default state. You must run /configs-targeting (or the equivalent REST / CLI call shown in Step 5) before verifying against the SDK, or verification will look like the LD-served path is broken when it isn’t. The single most common failure mode users hit with this skill is skipping the targeting step and spending time debugging enabled=False in their application code.

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.

Primary MCP tool:

• setup-ai-config – create a config with its first variation in one step (recommended)

Alternative MCP tools (for more control):

• create-ai-config – create just the config shell (key, name, mode)
• create-ai-config-variation – add a variation with model, prompts, and parameters
• get-ai-config – verify the config was created correctly

Optional MCP tools (enhance workflow):

• list-ai-configs – browse existing configs to understand naming conventions
• create-project – create a project if one doesn’t exist yet

Important: Bias Towards Action

When the user provides enough context (use case, model, mode), proceed through the entire workflow without stopping to ask for details you can infer. Use reasonable defaults for unspecified fields: default for variation key, the use case as the basis for instructions/messages, kebab-case for config keys. Complete all steps (create + verify) in one pass.

Workflow

Step 1: Understand the Use Case

Before creating, identify what you’re building:

• What framework? LangGraph, LangChain, CrewAI, Strands, OpenAI SDK, Anthropic SDK, custom
• What does the agent need? Just text generation, or tools/function calling?
• Agent or completion? See the decision matrix below

Step 2: Choose Agent vs Completion Mode

This choice is about input schema and framework compatibility, not execution behavior. Agent mode returns an instructions string; completion mode returns a messages array. Both provide provider abstraction, A/B testing, and metrics tracking.

Both modes support tools. Not all models support agent mode – check model compatibility if using agent mode. If unsure, start with completion mode (it’s the API default and more flexible).

Step 3: Create the Config (Recommended: One Step)

Use setup-ai-config to create the config and its first variation in one call. This is the recommended approach: it handles creation, variation setup, and verification automatically.

Config fields:

• key – unique identifier (lowercase, hyphens)
• name – human-readable name
• mode – "agent" or "completion"
• Optional: description, tags

Variation fields:

• variationKey, variationName – identifiers for the first variation
• modelConfigKey – must be Provider.model-id format (e.g., OpenAI.gpt-4o, Anthropic.claude-sonnet-4-5)
• modelName – the model identifier (e.g., gpt-4o). Always pass this in the initial call — leaving it off produces a variation that displays “NO MODEL” and forces a second PATCH to set it. The field is modelName; it is not name or model.name on this endpoint.

For agent mode, provide:

• instructions – a string with the agent’s system instructions

Example agent-mode call:

For completion mode, provide:

• messages – an array of {role, content} objects (system, user, assistant)

Example completion-mode call:

Optional:

• parameters – model parameters like {temperature: 0.7, max_tokens: 2000} (match the UI’s snake_case keys)

The tool returns the full verified config detail with the variation attached.

Step 3 (Alternative): Two-Step Creation

If the user asks for more control or a step-by-step approach, use the individual tools:

1. create-ai-config – create the config shell
2. create-ai-config-variation – add the variation with model, prompts, and parameters
3. get-ai-config – verify the result

Execute all three steps without stopping to ask for details. Infer the variation key (default), name (Default), instructions/messages, and model from the user’s request context. If the user asked for GPT-4o agent mode, you have enough to complete the entire flow. Only ask clarifying questions if the mode or model is truly ambiguous.

Step 4: Verify

If you used setup-ai-config, verification is automatic: the response includes the full config with variations. Check:

1. Config exists with the correct mode
2. Variation has a model assigned (not “NO MODEL”)
3. Instructions or messages are present
4. Parameters are set

Use get-ai-config for the verification call — do not drop to raw curl + jq. The MCP tool returns a typed object you can inspect directly. Hand-rolled jq filters against the REST response routinely break: the configs detail endpoint returns the variation list under different keys depending on expand, and a filter like .variations.items[] will fail with Cannot index array with string "items" when the response shape is a bare array. If you must call the REST API, use jq -e . first to inspect the actual shape before drilling in.

Report results:

• Config created with correct structure
• Variation has model assigned
• Flag any missing model or parameters
• Provide config URL: https://app.launchdarkly.com/projects/{projectKey}/ai-configs/{configKey}

Step 5: Make the variation servable

setup-ai-config and create-ai-config-variation create the variation but do not promote it to fallthrough. The new config will return enabled=False to every consumer until targeting is updated. This is the single most common “I created a config but my SDK still gets the fallback” failure. The workflow is not complete until this step is done.

What to tell the user

Print this checklist verbatim to the user after Step 4, then wait for confirmation. Do not claim the skill succeeded until the user confirms the fallthrough was flipped.

✅ Config and variation are created.

🔴 The SDK will return enabled=False until you flip targeting on. The fallthrough is currently pointing at an auto-generated disabled variation, not at the {variationKey} you just created.

Next step — run /configs-targeting with these inputs:

• Project key: {projectKey}
• Config key: {configKey}
• Environment key: the env whose SDK key is in your .env (usually test or production)
• Fallthrough variation: {variationKey} (the one this skill just created)

Verify after targeting is flipped by:

1. Opening the config in the LD UI, switching to the correct environment, and confirming “Default rule serves: {variationName}“ is shown with targeting On.
2. Running a quick test: ai_config = ai_client.{completion|agent}_config(...) and asserting ai_config.enabled is True.

Direct shortcut if the user wants to flip targeting without invoking the sibling skill

configs-targeting is the canonical path — it handles percentage rollouts, targeted rules, and variation-ID lookups. But for the simplest case (“promote the new variation to fallthrough in one environment”), you can run the underlying semantic PATCH yourself once you know the new variation’s _id.

Get the variation ID (use get-ai-config MCP, or):

Flip the fallthrough to point at it:

Or the same thing via the LD CLI if it’s installed locally:

Do not use turnTargetingOn — that semantic-patch instruction does not work for configs. updateFallthroughVariationOrRollout is the only instruction that actually flips the fallthrough.

modelConfigKey Format

Required for models to display in the UI. Format: {Provider}.{model-id}

• OpenAI.gpt-4o
• OpenAI.gpt-4o-mini
• Anthropic.claude-sonnet-4-5
• Anthropic.claude-3-5-sonnet

The create-ai-config-variation tool validates this format and rejects invalid values.

Edge Cases

What NOT to Do

• Don’t create configs without understanding the use case
• Don’t skip the two-step process (config then variation)
• Don’t try to attach tools during initial creation – update the variation afterward
• Don’t forget modelConfigKey (models won’t show in the UI)
• Don’t omit modelName from the initial variation call. It is required at create time; setting it via a follow-up PATCH is a workaround for a bug, not the intended flow. The PATCH field is also modelName, not name.
• Don’t drop to raw curl + jq for verification. Use get-ai-config (MCP) — it returns a typed object and avoids brittle jq filters that break on response-shape variation.
• Don’t consider the workflow complete until the user has been told to run configs-targeting. A created variation that isn’t promoted to fallthrough returns enabled=False to every consumer.

More resources

To learn more about creating a config in the LaunchDarkly UI, read Create configs (opens in a new tab)

To learn more about configuring the SDK, read:

• .NET AI SDK reference (opens in a new tab)
• Go AI SDK reference (opens in a new tab)
• Node.js (server-side) SDK AI reference (opens in a new tab)
• Python AI SDK reference (opens in a new tab)
• Ruby AI SDK reference (opens in a new tab)

Related Skills

• tools – Create tools before attaching
• configs-variations – Add more variations for experimentation
• configs-update – Modify configs based on learnings