Strategies and indicators
Keep what worked, version it, and export it to the platform you trade on.
Strategies and indicators are what you actually accumulate here. Results go stale; rules do not.
How a strategy gets into the library#
There is one way in: adopt a spec from a conversation.
The spec card's button reads Adopt as a strategy; on a later version of the same strategy it reads Adopt as v2. Clicking it writes the rules to the library.
The library#
/strategies lists everything you have kept: name and instrument, direction, version count, run count, the most recent result, and when it last changed. Row actions open the detail drawer, open the version tree, or remove the strategy.
The detail drawer has three sections:
- Rules — the same groups as the spec card: Entry when (all), Session (UTC), Exit when (any)
- Backtests — every run of this strategy
- Code — export targets, with Python open by default
Versions and the version tree#
v1, v2, v3 of a strategy are a sequence, not three unrelated cards. The version tree (/strategies/<id>/tree) draws that sequence as a canvas you can zoom:
- Each node is a version
- Each node carries the runs made from it
- Two versions can be compared side by side
Branching versions is a Pro feature; Free keeps a single line of work.
A version tree with at least three versions and one branch, zoomed to fit, with the run badges on the nodes.
Exporting to another platform#
The Code section offers three targets:
| Target | Use |
|---|---|
| Python | Runs anywhere, no trading platform needed |
| Pine | Paste into TradingView |
| MQL5 | Drop into MetaTrader |
Pick one to open the source; copy it, or download strategy.py, strategy.pine or strategy.mq5.
The strategy drawer's Code section with Python expanded, showing real rules rather than a toy one-line strategy.
Custom indicators#
Indicators are made in conversation. In agent mode, describe what you need:
Build an RSI(14) that paints green above 50 and red below 50
The assistant returns an indicator card. Save to indicators keeps it. From then on it:
- Appears in the
/indicatorslibrary - Appears in the chart's indicator picker, beside the built-ins
- Can be referenced by later strategies
The card can also copy the source for any target it supports.
When a strategy names an indicator you do not have#
If a spec uses an indicator that is not in your library, the card says so and offers two ways out:
- Create — have the assistant build it now
- Use existing — map it to one you already have
Running anyway would produce a result missing that signal, which is why the prompt is not decoration.
Next#
Once the library grows, the hard part is judgement: what actually changed between two runs, and whether the improvement is the strategy or the luck. “Backtest runs and comparison” is about that.