Find your way around Studio
Studio brings together Copilot conversations, strategy construction and testing views. Before making a change, check the selected strategy’s name, market and version. These identify the project you are about to work on.
A conversation explores an idea. A saved strategy contains rules. A proposal in a reply and a completed test have different roles, so review the strategy’s actual state after requesting a modification.
Start an organised research project
Use names that describe the behaviour being studied. EURUSD M15 · mean reversion is easier to find than several projects called “New strategy”. Distinguish variants when their hypotheses differ.
- Select the relevant strategy or create a separate project for a new idea.
- Give Copilot the market, horizon and purpose of your request.
- Say whether you want discussion or a change to the rules.
- Review proposed changes before moving to a test.
- Keep an identifiable version before an important experiment.
Avoid combining unrelated strategies in one discussion. When returning to older work, restate the relevant context instead of assuming every earlier detail still applies.
Find and organise conversations
Use History to search for a title or message content. Specific titles help when several conversations concern the same instrument.
| Action | Useful purpose | Check afterwards |
|---|---|---|
| Rename | Describe the question studied | Is the title distinctive? |
| Pin | Keep active research easy to reach | Keep the pinned set manageable |
| Archive | Put finished work away | Use the archived filter to retrieve it |
| Delete | Remove an unwanted conversation | Read the confirmation and retain useful material first |
Archiving is an organisational action. Use exports or separate research notes when you need an independent record of your work.
Keep an identifiable baseline
Project: EURUSD M15 · mean reversion
Question: does the signal remain useful after costs?
Baseline: version saved before adding the session filter
Data: selected dataset and dates shown in the report
Costs: values entered in the test settings
Next step: inspect losses, then compare one variantResume interrupted work
After signing in again or returning from a break, check the account, selected strategy, saved rules and displayed report. An older report can remain a useful reference without describing your latest changes.
If an operation is still marked as running, inspect its status before repeating it. When a setting appears missing, return to the view where you edited it and check for a save action or validation message.
Prepare a support request
Describe the action, screen and expected result. Include a focused screenshot, time and request identifier when one is displayed. Do not send passwords, access keys or unnecessary account information.
See Troubleshooting for initial checks and Account, credits and privacy for account-related questions.