Remix vs. Edit: Remix creates a brand-new scenario. If you just want to update the current scenario (including character behavior, response guidelines, voice, or evaluation criteria), use Edit instead — there’s no longer a category of change that requires remixing.
When to Use Remix
- Reuse a scenario’s structure or learning objective for a different audience
- Create a variation for a different company size, role, or industry
- Change character behavior, tone, or background without disrupting the original
- Experiment with a new approach without impacting the version your team is using
How to Remix a Scenario
1
Open the three-dot menu
Navigate to the scenario you want to remix and click the three-dot menu (⋯) in the top-right corner, then select Remix Scenario.

2
Confirm the remix
A confirmation appears letting you know a new scenario will be created from the original. Click Start Remixing.

3
Describe your changes
The Scenario Studio opens with the original scenario loaded as your starting point — note the Remix: prefix in the header and the Publish button in the top-right. The Remix: prefix is a working label in the Studio, not a permanent part of the scenario’s name. Tell the AI Agent what you want to keep or change:
- “Make the character more friendly and engaging instead of defensive and skeptical.”
- “Change the company context to an enterprise-sized organization.”
- “Adjust the stakes and tone for a senior leader audience.”

4
Review and publish
Once the scenario looks right, review the updated character details, context, and objectives, then click Publish.Your remixed scenario will exist as a new, independent scenario — the original stays unchanged.
Tips
- Clearly describe what you want to keep vs. what you want to change — the more specific, the better
- Rename your remixed scenario so it’s easy to distinguish from the original. You can rename it while you’re editing or any time after publishing, so the Remix: prefix does not have to stay in the name
- If you’re building variations for multiple audiences (e.g., sales, HR, engineering), remix once per variation rather than repeatedly overwriting drafts