Skip to main content

Studio · Product guide

Save strategy versions without changing running bots

Keep research changes separate from execution.

Before you begin

Open a project with at least one strategy version. Save or discard any code edits before leaving it.

Step-by-step instructions

Screenshots are examples. Your balances, limits, availability and status may differ.

  1. A project holds your idea and conversations. A version saves a particular strategy definition: logic, indicators, market, timeframe and risk assumptions.

  2. Choose New version beside the version selector, give it a label and optionally explain the change. This clones the selected version and current edits.

  3. A tested definition stays unchanged. Editing it and running a test creates a new version; edits to an untested draft can remain in that draft.

  4. Use the version selector or its history icon to reopen a definition. Use Backtest results > Test history to reopen an individual test run.

    Step 4 · Save strategy versions without changing running botsActual app screen · English interface · Illustrative demo data
  5. Saving a tested version to the bot library approves it and creates a library entry. Each deployment pins that approved version to an account and retains its own risk settings. Research changes do not replace running bots.

What you should see

You can reopen versions and runs without silently changing an already deployed bot.

If something goes wrong

If a saved strategy no longer matches its test, reopen it in Studio, run a valid test and save the tested version again.

Contact support
Changing a research project must never silently replace the logic of a running bot.
Open StudioProduct manual · Follow the current status and rules shown in your account