
XTester Studio alpha.4: strategy research and the path to portfolio testing
What alpha.4 changes in research, charts and strategy checks, and how those workflows relate to our plans for risk management on a shared account.
Development
What alpha.4 changes in research, charts and strategy checks, and how those workflows relate to our plans for risk management on a shared account.
Development
Keep a baseline, test a separate hypothesis and compare results: the proposed Studio interface and documented XTester Lab operations through MCP.
Development
Treat the strategy as a project: code, backtest, trades on the chart. A market-phase analyzer ships in the upcoming XTester Studio release.
Development
A full MCP catalog can fill an agent's context before the backtest. Progressive Tool Discovery loads one tool per step. Planned for XTester.McpHost and Studio.
Development
Why strategies need to be tested on a shared balance. A look at risk allocation, a programmable orchestrator and the development of XTester Studio.
Development
XTester 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.
Development
Why compiling C# does not prove the same strategy behavior: timing, orders, sizing, HTF data, and trade-level checks after a TradingView port.
Development
XTester 0.0.88 can read an external strategy, create a separate C# project, and report what changed during the port.
Development
How MCP connects an AI agent to a local XTester environment for projects, compilation, historical data, backtests and inspectable results.
Development
A short status update: a deterministic backtest engine, work on a realistic execution model, and plans for the next release.
Development