Automatic local versions of a strategy

BacktestBetty· Jul 2026 ago done· 👍 2· 💬 7

Every time a backtest runs, snapshot the strategy that produced it. Not a full version control system, just enough that a result is permanently tied to the exact code that made it. Two problems this solves: recovering a working version I edited away, and the bigger one, being able to answer "what exactly produced this result" three weeks later. Right now my results and my code drift apart and I reconstruct the pairing from memory, which is exactly as reliable as it sounds.

BacktestBetty

16 posts · 0 followers

+ Follow

7 replies

TraderWeTraderWe Team· Jul 2026 ago· edited Aug 2026 ago

This is a good request and the framing — result permanently tied to the code that produced it. Is how we'd want to build it rather than as a general version control feature. Adding it to the roadmap.

DataDrivenDee· Jul 2026 ago

Reproducibility again. Half the requests on this board are the same underlying need.

RiskFirstRita· Jul 2026 ago· edited Aug 2026 ago

Yes please. My workaround is a manual note in a spreadsheet, date, param values, result — and I skip it exactly when I'm in a hurry, which is exactly when I'm most likely to be changing something I shouldn't. Automating the boring part of the checklist is the only way it actually gets done.

PremarketPete· Jul 2026 ago

- keep a dated copy folder, painful but works - diff between snapshots is the real value, not just the rollback - would want the snapshot to include params, not only the code

DrawdownDave· Jul 2026 ago

I once spent two days trying to figure out why a strategy stopped working, convinced the market had changed. It hadn't. I'd fat-fingered a stop value during a late night edit and never noticed. No snapshot, no way to prove it to myself. Cost me more in confidence than in dollars, and it cost a fair bit in dollars.

GrandpaGrizzly· Jul 2026 ago· edited Aug 2026 ago

In my day we printed the parameters on paper and stapled them to the tape. Ugly, but paper doesn't quietly overwrite itself. Pete's right that the diff is where the money is — the rollback just saves you, the diff teaches you.

CryptoKarl· Jul 2026 ago

+1 on params being in the snapshot, otherwise it's half a receipt. I've re-run the same crypto strat twice, got different numbers, and stared at the screen for an hour before remembering I'd bumped leverage "just to see". Memory is not a database, mine especially.

← All feature requests

Automatic local versions of a strategy

Related reading

7 replies