XTesterSet up XTester with an AI agent
Install XTester Studio, connect your AI client and run a first test in a separate project. You approve installation, launch and project access.
The current website version, including alpha.5, does not establish whether the alpha.4 issue is fixed or still present. This guide records no alpha.5 installation, host startup, initialize, tools/list or backtest verification. Obtain fresh approved evidence for the actual artifact and mode. Canonical technical source and evidence boundaries.
Observed release blocker: Apple Silicon Macs
XTester Studio 1.0.0-alpha.4 could not connect on an Apple Silicon Mac in the October 6, 2026 check. The process exited with code 3 before the MCP connection. Wait for a corrected build for this release; installing an SDK or changing the config will not fix startup. Keep OS security protections enabled.
Check the current release before installing. Windows, Linux and Intel Macs were not run in that check. The technical guide retains the exact error, commands, file hash and platform details.
2. Check your installation
If XTester Studio is already installed, check its version and location before downloading another copy. Otherwise, choose the official package for your OS and processor from the download page. Verify its size and SHA-256 against the current manifest before opening it. Keep existing projects and settings backed up; install into a separate folder.
3. Install XTester Studio
Follow the platform instructions on the download page. Approve installation and OS dialogs yourself. If an OS security check blocks the app, review the publisher and signing information before deciding what to do. Do not disable security checks or install extra toolchains in advance.
Expected path after installation
The website generator suggests a path; it cannot find installed files or detect your username or CPU. Replace the example with the real absolute path from XTester Studio. Use the complete engine folder for your installed architecture. You can copy, download or edit the config without granting project access.
6. Connect your AI client
Open XTester Studio and create a separate C# project. Go to Settings → External agents and copy the configuration for your client. Back up the client config, merge the new entry without removing other servers, then restart the client.
The XTester Studio connection uses --studio. Approve access in the XTester Studio window and ask the agent to check initialize and tools/list. Read-only access does not allow compilation or project changes. Use the connected tool schemas: the Windows --mcp catalog has different parameters. XTester Studio backtests use depositUsdt and confirm; reports require the returned runId.
8. Run your first test
Start with the C# template and compile it. Check the available data tools before importing or downloading data. A small generated dataset is suitable for learning the controls if the runtime supports it; otherwise choose available local history. Agree to any new download separately. Keep generated prices labelled as generated.
Run one short test and open its trades, equity chart and report. Save the source, settings and result together so you can compare the next version. Broker API keys and live orders are not needed for this test. Historical results do not guarantee future returns.
12. Troubleshooting
If startup, connection or permissions fail, stop at that step and use the exact error to choose the next action. On Apple Silicon, the alpha.4 startup problem above requires a corrected publisher build. A generated configuration alone does not establish a connection.
Your AI client may send code and results to its model provider, even when MCP runs locally. Choose the provider and access level accordingly.
Full commands and troubleshooting · MCP setup · Security · Russian guide