September at EasyTrading: Studio ships, and CopyTrader explains how to connect subscribers
Studio is available across three desktop platforms. A look at useful alpha.4 changes, CopyTrader’s guide to connecting subscribers and the portfolio-management concept.
XTester Studio is available to download for Windows, macOS and Linux. The current preview, 1.0.0-alpha.4, was published on September 29.
CopyTrader also published a practical guide to its existing platform, covering how to connect a trading account and give subscribers access to copying.
Research conversations now have a home
Studio brings the editor, market data, simulation and AI Lab into one application. In the lab, you can work on strategy versions, run experiments and compare results. Alpha.4 gives each investigation its own Copilot conversation. You can open it when needed, and the assistant's questions take you back to the relevant investigation, making parallel experiments easier to pick up again.
Restarting a simulation now preserves the selected period. The release also fixes slippage on market orders placed at minute boundaries and several Pine partial-exit and trailing-exit cases. If an earlier result relies on those operations, rerun it in the new version before continuing your comparison.
The XTester site has the alpha.4 release details and download entry point.
CopyTrader: connecting your account and subscribers
On September 22, CopyTrader published a guide to connecting traders and investors. It addresses people who already trade on an exchange account and have an audience interested in copying those trades.
The existing setup has distinct roles: the owner creates a project and connects an exchange account as a trader; participants connect their own accounts as investors. If a robot trades on the source account, that account's trades remain the source for copying. The connection described in the guide does not require uploading the robot's source code to CopyTrader.
The guide covers choosing a supported exchange and market, configuring participant access and setting copying parameters. Before enabling copying, you also need to understand how existing open positions will be handled in that project's configuration. The guide explains where to look and how to compare a system-log event with actual orders on an investor's exchange account.
Funds remain on exchange accounts. Withdrawal permission is not required, but trading API access does authorize trades. An investor's fill price, position size and result can differ from the trader's.
Studio's release does not add automatic deployment from the lab into CopyTrader.
The next design problem: several strategies, one account
In September, we also described a concept for a programmable portfolio layer. It addresses a different problem: strategies may pass individual tests while competing for the same capital and building exposure to the same market when run together. This is not an alpha.4 feature, and no release date has been committed.
The proposed management module would allocate risk across strategies using market conditions and account state. Its rules would be programmable, with the user retaining the ability to intervene. Those allocation rules would also need testing: how does the same set of strategies behave under different constraints on shared capital?
The optional daily loss limit added to individual robot profiles in alpha.4 is not the same as portfolio-wide allocation. TradeStat likewise remains a planned public-statistics service.
What you can try now
For strategy development and research, download Studio and revisit a familiar experiment: inspect its period, trades and assistant conversation. If your immediate task is to connect people to an account you already trade, use the CopyTrader guide to work through your project's settings.
Studio is still a preview. The release notes distinguish completed checks from outstanding validation: native macOS execution and Gatekeeper acceptance remain unverified, while Linux testing used WSL2/Xvfb and did not cover every installation path. Windows packages lack Authenticode signing; macOS packages lack Developer ID signing and notarization. Read the release notes for your platform before installing.