The MetaTrader 5 AI Assistant is the agent built into the MT5 terminal since build 6060, and three later builds extend it into the Strategy Tester. Build 6140 (20 August 2026) added LLM providers. Build 6180 (3 September 2026) lets it read tester reports and logs and launch optimisation. Build 6230 (24 September 2026) lets it read Expert Advisor inputs, start or remove programs on charts and query the Economic Calendar. None of the three notes lists a change to MQL5 trade functions.
For a TradingView strategy executed through PineConnector's EA, the backtest stays in TradingView, and the new tester tools apply to MQL5 EAs tested in MT5. The changes closest to a live alert path are that the assistant can remove an EA from its chart and read EA logs. This page, part of the MetaTrader 5 updates library, explains each change and ends with a checklist.
What changed in builds 6140, 6180 and 6230
MetaQuotes introduced the AI Assistant and Model Context Protocol (MCP) support in build 6060 on 23 July 2026, as covered in the build 6060 guide.[4] The three builds below extend it. Dates and feature descriptions come from each MetaQuotes release note.
Scroll horizontally to read every column.
| Build and date | AI Assistant change | Tester and chart tools |
|---|---|---|
| Build 6140[1] 20 Aug 2026 |
New LLM providers. The built-in provider's context window falls from 1 million to 500,000 tokens. Chats can be deleted. | An MCP tool that stops the Strategy Tester. A fix for pending-order expiry when the assistant changed SL or TP. |
| Build 6180[2] 3 Sep 2026 |
More tools for EA analysis, testing and optimisation. | Reads tester reports, settings and the tester log. Helps launch optimisation. Adds indicators. Reads terminal and EA logs. |
| Build 6230[3] 24 Sep 2026 |
Can prepare more steps of a task within the terminal. | Reads EA inputs and prepares tester runs. Launches EAs and scripts; removes EAs and indicators. Reads the Economic Calendar. |
Build 6140, 20 August 2026
Build 6140 expanded the provider list, including Alibaba, Cerebras and z.ai, using the relevant provider credentials. It reduced the MQL5.community context window from 1 million to 500,000 tokens and added a tool that stops the Strategy Tester.[1]
Build 6180, 3 September 2026
Build 6180 lets the assistant retrieve test and optimisation results and help configure an optimisation run. It also provides access to tester settings, tester messages, terminal logs and EA logs.[2] Adding indicators to a chart had already arrived through MCP in build 6090.[5]
Build 6230, 24 September 2026
Build 6230 lets the assistant inspect EA inputs before preparing a test. It can launch EAs and scripts on charts, remove EAs and indicators, and read countries, events and values from the Economic Calendar.[3]
MetaQuotes presents the assistant's output as information that the user must evaluate, rather than investment advice.[4]
Can the MT5 AI Assistant read a Strategy Tester report?
Yes, from build 6180. MetaQuotes describes retrieving results to compare runs or investigate a strategy.[2] The report is the tester's Results tab, with figures such as History Quality, balance and equity drawdown, profit factor, recovery factor and Sharpe ratio.[6] The MT5 Strategy Tester report guide explains each figure.
A summary describes one run under one set of settings. A summary alone is not evidence of a new test. The linked release notes give no measured accuracy for these summaries. Check these points yourself before you rely on one:
- The settings behind the figures: symbol, period, dates, modelling mode, delay and deposit. Build 6180 lets the assistant retrieve them, so ask it to list them.[2] The modelling modes guide explains why the mode matters.
- History Quality: MetaQuotes derives it from the share of correct one-minute data, and the report shows intervals below 50% in red.[6]
- Costs: commissions are set in the tester's advanced settings. The profit-in-pips mode omits swap and commission calculations; it also skips margin control.[7]
- Every number quoted: compare each figure in a summary with the Results tab before you record it.
Why an AI-launched optimisation still needs an overfitting check
Optimisation repeatedly tests an EA with different input values to compare their results. The tester shows the total number of combinations beneath the input list.[7] Build 6180 lets the assistant help set up a run, and build 6230 lets it read the inputs first. Neither build changes what happens when you pick the best of many runs.
Illustrative example, not a recommendation. An EA has three inputs set to test 10, 10 and 5 values. Assume all combinations complete and are available for selection. The slow complete algorithm runs every combination: 10 × 10 × 5 = 500 passes.[8] With the Forward option on, the tester re-runs the best 10% of full-search passes on the later part of the history. Ten per cent of 500 is 50, below the documented floor of 256, so 256 passes are re-run. If fewer than 256 runs exist, all available runs take part.[7]
The Forward option reserves a later historical period to check the optimised settings.[7] The option is a hold-out: the later part of the history is kept back from the search. Bailey, Borwein, López de Prado and Zhu explain why repeated searches on the same data increase false-positive risk. They also identify a limitation of ordinary hold-out tests: the result does not account for how many configurations were tried.[9] Choosing among the 256 forward results also uses the forward period for selection. Record how many passes and optimisation sessions you ran, including those the assistant launched. The overfitting and curve-fitting guide covers the checks in detail.
What it means for a TradingView-to-MT5 workflow
In a PineConnector setup, a Pine strategy is backtested in TradingView's strategy report, formerly known as the Strategy Tester, where a broker emulator simulates the trades.[10][11] The MT5 Strategy Tester tests MQL5 Expert Advisors.[7] MetaQuotes' tester help describes no way to replay TradingView alerts or webhook messages in it, so the new tools do not test a Pine Script strategy. Why TradingView and MT5 backtest results differ covers that gap.
The assistant can still reach the terminal that runs the PineConnector EA. Three points matter:
- The EA's chart. PineConnector's MT5 guide attaches one EA to one chart for a normal single-account setup.[12] Build 6230 permits the assistant to remove an EA from its chart.[3] An EA removed from its chart cannot process alerts, so check the chart after any AI session.
- The logs. The PineConnector EA prints its processing and diagnostic messages in the Experts tab.[13] Build 6180 lets the assistant read EA logs,[2] so you can ask it to find an entry. PineConnector's docs compare the TradingView Alerts log, the Signals log and the MT5 Experts tab and order history, in that order. A marker or simulated fill alone does not establish what happened at the broker.[14]
- Trades the assistant places. Since build 6060 you can allow or prohibit AI-initiated trading operations, or require manual confirmation.[4] With Magic Restriction on, the documented default, the PineConnector EA manages only positions whose magic number matches its own. With it off, the EA can also manage positions opened manually or by another EA.[15] Which magic number an AI-initiated trade carries is not documented; test on demo.
PineConnector Edge hosts MT5 with the PineConnector EA and does not host third-party EAs.[16] PineConnector's docs do not mention the MT5 AI Assistant. The Economic Calendar tool reads data inside the terminal and does not change what a TradingView alert sends. For the TradingView side, see what TradingView's MCP server lets an AI assistant change.
What to check after updating to build 6230
- Read the terminal's build number. The MT5 updates hub lists the ways to find it.
- Open the AI settings and decide whether AI-initiated trading is allowed, prohibited or needs manual confirmation. Network requests and command-line operations have separate settings.[4]
- If you connect your own provider, note the provider and the label of the configured credential entry, without copying API keys, tokens or passwords into notes or logs. The release notes do not say what terminal data reaches a provider, so read that provider's data-handling terms before sharing account information.
- After an AI session, confirm the PineConnector EA is still on its chart and allowed to trade, then read the Experts tab.[13]
- For any report the assistant summarises, record the build, modelling mode, dates and History Quality beside its figures.
- For any optimisation, record the number of passes, the optimisation criterion and whether a forward period was used.
- After a change to the terminal, send a demo test alert and check the intended account's positions and history for the result.[17]
What these release notes do not tell you
Release notes describe features, not results. MetaQuotes gives no accuracy figures for the assistant, and this page makes no claim about its accuracy. The MetaEditor help page retrieved on 25 September 2026 describes a code-completion tool; it does not document the full terminal agent introduced in 6060.[18] Nothing on this page was installed, tested on a trading account or compiled.
An assistant that sets up optimisations on request makes it easy to run many of them. The count of runs matters whoever launched them. A tester report, an AI summary and an optimisation result all describe history, and none of them shows how a strategy will behave on new data.
Frequently asked questions
What is the MetaTrader 5 AI Assistant?
Build 6060, announced on 23 July 2026, introduced the MT5 terminal’s AI agent and expanded MetaEditor’s assistant beyond its earlier code-completion role. It uses MQL5.community as its default provider, or your own API key for supported providers. It can analyse markets, positions and trading history. Since builds 6180 and 6230 it can also work with the Strategy Tester, charts, logs and the Economic Calendar.
Can the MT5 AI Assistant use the Strategy Tester?
Yes. Since MT5 build 6180 (3 September 2026), the AI Assistant can retrieve Strategy Tester reports, settings and logs, and help configure optimisation criteria. Build 6230 (24 September 2026) lets it read an Expert Advisor's inputs to prepare a tester run. The MT5 Strategy Tester tests MQL5 Expert Advisors, so these tools do not backtest a TradingView Pine Script strategy.
What changed in MT5 build 6180?
MT5 build 6180, published by MetaQuotes on 3 September 2026, gave the AI Assistant tools to retrieve Strategy Tester reports, launch optimisation, read tester settings and logs, add indicators to charts, and read terminal and Expert Advisor logs. It also fixed a runtime error from key presses during visual testing and improved stop-level handling on netting accounts in the Web Terminal.
What changed in MT5 build 6230?
MT5 build 6230, published on 24 September 2026, lets the AI Assistant read Expert Advisor inputs and prepare Strategy Tester runs, launch EAs and scripts on charts, remove EAs and indicators, and query the built-in Economic Calendar. MQL5 gained vector and matrix sorting and .NET CoreCLR 8+ support. The release note lists no change to MQL5 trade functions.
What changed in MT5 build 6140?
MT5 build 6140, published on 20 August 2026, added new LLM providers for the AI Assistant, including Alibaba, Cerebras and z.ai. It cut the built-in MQL5.community provider's context window from 1 million to 500,000 tokens and added an MCP tool that stops the Strategy Tester. It also fixed pending-order expiry being reset when the assistant changed SL or TP.
Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account and no code was compiled.
Related reading
- MetaTrader 5 updates for automated traders: builds since June 2025
- The MT5 Strategy Tester report, explained
- Overfitting and curve-fitting in trading strategies
- MT5 build 6060: MCP, AI Assistant and passkeys
- Why TradingView and MT5 backtest results differ
Sources
- MetaQuotes – MetaTrader 5 Platform Update Build 6140: AI Assistant and Web Terminal Improvements, accessed 25 September 2026.
- MetaQuotes – New MetaTrader 5 Platform Build 6180: More AI Features, accessed 25 September 2026.
- MetaQuotes – New MetaTrader 5 Platform Build 6230: Expanded AI Capabilities, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Build 6060: AI Integration, Passkey, and Code Management Improvements in MetaEditor, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Platform Update Build 6090: General Improvements, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Testing Report, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Strategy Optimization, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Optimization Types, accessed 25 September 2026.
- Bailey, Borwein, López de Prado and Zhu – The Probability of Backtest Overfitting (revised February 2015), accessed 25 September 2026.
- TradingView – Pine Script release notes, accessed 25 September 2026.
- TradingView – Strategies, accessed 25 September 2026.
- PineConnector – Install the MT5 EA: attach the EA to one chart, accessed 25 September 2026.
- PineConnector – Frequently asked questions: the Experts tab, accessed 25 September 2026.
- PineConnector – Best practices: compare logs in the right order, accessed 25 September 2026.
- PineConnector – EA settings: Magic Restriction, accessed 25 September 2026.
- PineConnector – Connect your MT5 account (Edge), accessed 25 September 2026.
- PineConnector – Test your setup, accessed 25 September 2026.
- MetaQuotes – MetaEditor Help: AI Assistant, accessed 25 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
