The rebuild we announced on Friday is finished. Version 2.0.0 went out on Sunday afternoon, and over
Sunday and Monday we followed it with seven smaller builds as you told us what the new layout got
wrong. The current build is 2.0.7. Update from inside the app as usual, or get the installer from
the
Download page.
This post covers what you will find, what we fixed after the first build, and what stayed the same.
The plan we published before the work started is
here.
1. What each screen is now
Dashboard. One screen for is it running, what did it do today, and is anything wrong: engine
and broker state, your daily loss limit, the equity curve with drawdown underneath, a calendar of
daily results, recent fills, performance by strategy, and a backtest of the same strategy next to
what it did live. A fresh install starts with a short checklist instead of an empty page.
Top and bottom bars. The top bar shows state, live or paper, the operating profile, today's
realised result, positions, the loss limit and the data feed. Start and stop are one control, and
the arrow next to it lets you choose between stopping the engine, pausing new entries, or
flattening everything. One correction came out of this: the old stop confirmation said it would
close every position at market, but it only stopped the engine. The new menu says exactly what
each choice does. The bottom bar carries connection, engine, machine load and version.
Settings. A grouped menu on the left, and operating profiles: one named bundle of strategy,
symbol selection, money and risk, trading hours and order method. A summary fixed to the bottom
of the screen tells you what is still unsaved.
Backtest. Six tabs. A strategy editor with a larger code area, a factor reference, completion
and inline errors. An overview with diagnostics and a robustness view. A trade list that shows why
each entry fired and how it filled. Optimisation drawn as a map of two parameters with the stable
region marked. One-second replay with the order book. A run history that puts two runs side by
side together with the code that changed between them.
Live trading. Click a price on the order book to place a limit order there, and sell a whole
position from its row with a single confirmation. Flatten everything now re-reads the account
afterwards and tells you what it actually holds, instead of assuming the orders worked.
Scanner. A workspace you lay out yourself: drag boxes, resize them, and the layout is saved.
Lists refresh every second and prices flash when they change.
Trade journal. New. It fills itself from your fills: round trips, orders that never filled, a
calendar, notes and tags, automatic tags such as a pre-market entry or a quick re-entry after an
exit, and a daily check of your trade ledger against the fill reports your broker sent.
Subscription and light mode. The subscription screen is redesigned, and light mode was
reworked across the whole app rather than inverted.
2. What we fixed after the first build
The dashboard could trap you on a saved paper view with no records and no way back. Starting a
backtest from the editor tab hid its progress. Picking a broker in settings closed the list.
Opening the plan comparison squashed the cards above it. The server backtest kept resetting its
start date. Scanner boxes showed six rows no matter how large you made them. The live screen grew
without limit as positions and engine messages piled up. Price flashes had gone missing in the
rebuild. All of these are fixed in 2.0.1 to 2.0.7.
Two behaviour changes arrived in the same builds. Daily bars now refresh automatically for every
account, not only some. And ETFs are no longer included when the app scans for symbols, so the
ETF option in settings is gone.
3. What did not change
Your strategies, recordings and trade history were not migrated or rewritten. Your settings kept
their values under the new labels. As announced, the AI model section in settings and the AI
check strip at the bottom of the screen were removed. If you had a backtest whose results
depended on the ML entry gate, run it again on 2.0.
4. Tell us where it costs you a click
That is the failure a rebuild like this introduces most often, and the one we see least from the
inside. Post it in
Bug Reports or
Feature Requests.