DevelopmentTrading strategy portfolios in XTester: shared capital, risk and the new Studio
Why strategies need to be tested on a shared balance. A look at risk allocation, a programmable orchestrator and the development of XTester Studio.
Tag
DevelopmentWhy strategies need to be tested on a shared balance. A look at risk allocation, a programmable orchestrator and the development of XTester Studio.
DevelopmentXTester Studio will combine the Code - OSS development environment with the existing C#/.NET XTester Engine. The editor, workspace, Git and terminal will come from Code - OSS. Data handling, simulation, execution and statistics will be carried over from the current version of XTester. We are targeting October 1, 2026 for the first public milestone.
DevelopmentWhy compiling C# does not prove the same strategy behavior: timing, orders, sizing, HTF data, and trade-level checks after a TradingView port.
DevelopmentXTester 0.0.88 can read an external strategy, create a separate C# project, and report what changed during the port.
DevelopmentHow MCP connects an AI agent to a local XTester environment for projects, compilation, historical data, backtests and inspectable results.
РелизыVersion 0.0.75 brings managed ONNX models, controlled AI provider access, and one strategy lifecycle from backtesting to Launcher.
РелизыThe AI lab now detects strategies with no signals or invalid runtime evidence earlier, returns to the objectively strongest version, and requires fresh validation on unseen data.