How-to guide
Work with the AI copilot
The in-app assistant that helps you compose strategies and interrogate a finished run.
The copilot is a chat assistant wired into the product. It doesn't replace the engine, it helps you build a strategy and make sense of a finished run, in plain English. It never scores or tunes the numbers; the engine does that deterministically.
Where it appears#
- Builder copilot: alongside the strategy you're composing. Ask it to refine a condition, add a stop, fix an awkward phrasing, or turn a vague idea into a runnable query.
- Results copilot: a dock in the terminal after a run. Ask why a metric looks the way it does, what a condition actually did in the trades, or what to check next.
What you can ask#
| Ask | It can |
|---|---|
| "tighten the stop", "add a trend filter" | Propose an edit to your current strategy |
| "why is the Sharpe low?" | Read the run's metrics and explain them |
| "what did the RSI condition actually do?" | Explain a condition against the trade ledger |
| "is this overfit?" | Point you at the right robustness check and the overfit verdict |
| "how does this compare to my last run?" | Line up two runs for you |
What it can't do#
- It acts on your current strategy or run, the results copilot needs a saved run to read from, so run the backtest first.
- It never steers the result. Your query compiles to a fixed spec and the engine scores it; the copilot can suggest a change, but it can't make a losing strategy look like a winner. Same query ⇒ same spec ⇒ same test.
Treat suggestions as drafts
The copilot proposes; you decide. Every edit it suggests lands in your editable strategy, so you review and run it, nothing changes your backtest without you.
Related: write your first strategy, analysis & export, robustness.