Skip to main content
A variation is one runnable configuration for an agent. It combines a prompt, model, constraints, discovery and compaction behavior, plus its assigned tools, sub-agents, and memory. This guide adds a second variation to an existing agent and configures how new objectives choose between them.

What you need

  • The published Conference Attendee Generator agent from the Quickstart.
  • An enabled model for each variation.

Add a second variation

Open the agent and stay on Variations. Click New variation and configure a candidate that differs for a reason you can evaluate. For the conference attendee agent, create: Keep the remaining settings equal to the Default variation. This isolates the prompt format as the intentional difference.
Current variation form with prompt, model configuration, constraints, discovery, and compaction settings

The New Variation pane collects the candidate's prompt, model, and runtime settings

Click Create variation. Both candidates now appear in the variation list. Assign the Faker MCP tool set to Detailed, then select either variation to inspect its exact configuration.
Variations pane with Default and Detailed candidates and Faker MCP assigned to the selected Detailed variation

The agent now has Default and Detailed candidates with the same Faker capability

Choose how unpinned objectives select

The agent’s Details card contains Variation Selection:
  • Random gives each variation equal probability on every new objective.
  • Feedback Driven samples from the feedback history of each variation. It balances using the current best candidate with continued exploration.
Select Feedback Driven when you intend to score representative objective runs. Leave it on Random when equal traffic is the desired invariant.
Agent Details card with Feedback Driven variation selection and two variations

Variation Selection is changed from the agent Details card

Selection happens at objective creation

When an objective is created without variationId, Cadenya selects one variation and writes it into configSnapshot.agentVariation.
That snapshot stays with the objective. Later edits to either variation affect future objectives only.

Pin a variation for a controlled run

Pass variationId when a test, migration, or application route must use one exact candidate:
Pinning overrides both Random and Feedback Driven selection. It is the right mechanism for deterministic evaluation, not a permanent weight setting.

Optimize with feedback

Score pinned test runs, then observe future sampled selections.

Assign capabilities

Give each candidate a controlled set of tools, sub-agents, and memory.