Describe your MetaTrader 4 logic in plain English. Review one complete MQL4 artifact, run a single-file MetaEditor syntax check, and keep revising the source before you test it in MT4.
Open the Coding Agent, then choose MQL4 from the language menu.
Generate code you can inspect, check, and keep editing
Describe an Expert Advisor, custom indicator, or utility script. The agent produces one editable MQL4 artifact with the helpers and event handlers kept in the same source file.
A versioned reference derived from official MQL4 documentation keeps common signatures, parameter order, event handlers, and classic order APIs separate from MQL5 patterns.
Send the current single-file source to the independent MT4 syntax service. Source-located diagnostics give the agent a concrete next repair instead of a guessed rewrite.
Save MQL4-specific naming, risk defaults, and source conventions without mixing them into the memory used for MQL5 or other coding languages.
Generation, source review, static diagnostics, and platform testing are separate gates.
Choose MQL4 in the Coding Agent, then state whether you need an Expert Advisor, custom indicator, or script. Include inputs, timeframe, signal, order, and risk rules that must stay explicit.
Write one MQL4 EA that enters on a closed-bar EMA crossover, limits spread, and exposes lot size, stop loss, and take profit as inputs.
Inspect the event handlers, indicator calls, order selection, price normalization, and error paths. Ask the agent to explain or change a specific block without starting over.
Explain the one-order-at-a-time guard, then add a magic-number filter without changing the crossover rule.
Use the static syntax checker for compiler diagnostics. After the source is clean, compile it in the target MetaEditor and test behavior in MT4 Strategy Tester or a demo account.
Fix each compiler diagnostic, then list the broker, data, spread, and execution assumptions that still require platform testing.
The source stays readable. Static diagnostics catch compiler issues; MT4 remains the authority for execution and tests.
#property strict
#property indicator_chart_window
#property indicator_buffers 1
#property indicator_color1 clrDodgerBlue
input int InpPeriod = 14;
double OutputBuffer[];
int OnInit()
{
if(InpPeriod < 2)
return(INIT_PARAMETERS_INCORRECT);
if(!SetIndexBuffer(0, OutputBuffer, INDICATOR_DATA))
return(INIT_FAILED);
ArraySetAsSeries(OutputBuffer, true);
SetIndexStyle(0, DRAW_LINE, STYLE_SOLID, 1, clrDodgerBlue);
SetIndexEmptyValue(0, EMPTY_VALUE);
SetIndexLabel(0, "Simple MA");
IndicatorShortName("Simple MQL4 MA");
return(INIT_SUCCEEDED);
}
int OnCalculate(const int rates_total,
const int prev_calculated,
const datetime &time[],
const double &open[],
const double &high[],
const double &low[],
const double &close[],
const long &tick_volume[],
const long &volume[],
const int &spread[])
{
if(rates_total < InpPeriod)
return(0);
int limit = prev_calculated == 0
? rates_total - InpPeriod
: rates_total - prev_calculated + 1;
if(limit > rates_total - InpPeriod)
limit = rates_total - InpPeriod;
for(int index = limit; index >= 0; --index)
OutputBuffer[index] = iMA(NULL, 0, InpPeriod, 0,
MODE_SMA, PRICE_CLOSE, index);
return(rates_total);
}Compiler diagnostics for the submitted source, including line and column locations when MetaEditor provides them.
Terminal compilation, chart behavior, Strategy Tester results, broker permissions, fills, and demo or live execution.
One self-contained .mq4 file. Multi-file projects, DLLs, private libraries, compiled EX4 output, and resources are outside this workflow.
The difference is the connected artifact, MQL4 context, diagnostics, and memory. Platform testing remains required.
| Workflow area | Pineify MQL4 Agent | General AI chat |
|---|---|---|
| MQL4 language context | Versioned reference derived from official MQL4 documentation | Depends on the model, prompt, and current context |
| Code output | Editable, single-file .mq4 artifact | Usually an isolated chat response |
| Syntax feedback | Source-located MetaEditor diagnostics in the workflow | Usually requires manual copy and paste |
| Language preferences | Dedicated MQL4 memory | Varies by product and session |
| Runtime and trading validation | Still requires MT4 compilation, testing, and review | Still requires MT4 compilation, testing, and review |
Turn explicit entry, exit, order ownership, spread, lot-size, stop-loss, and take-profit rules into inspectable MQL4 source.
Generate a single-file indicator with inputs, buffers, plots, closed-bar calculations, chart objects, or alerts.
Continue from an existing .mq4 artifact, inspect compiler diagnostics, and apply a focused fix while preserving intended behavior.
Translate the intended behavior of Pine Script or MQL5 into MQL4 APIs, then review platform differences instead of relying on a literal syntax swap.
One-time payment · No subscriptions · Lifetime updates included
We're moving to annual subscriptions soon. This is your last chance to lock in a one-time payment and keep every future update at no extra cost.
💡 Once we switch, lifetime access will no longer be available
MQL4 generation and syntax checking are development aids. MT4 compilation and testing remain part of your release process.
Each agent keeps its language context and validation boundary separate.
Generate MetaTrader 5 indicators, Expert Advisors, and scripts in MQL5.
View agentGenerate editable TradingView indicators and strategies in Pine Script.
View agentGenerate cTrader C# cBots and indicators with compiler diagnostics.
View agentDefine the MT4 behavior, inspect the generated .mq4 source, use diagnostics to repair it, and validate the result in your own MetaTrader 4 environment.
Select MQL4 in the language menu after the Coding Agent opens.