Workspace and Tasks

The workspace brings together task selection, the conversation, source attachments and the model selector. Choose a task before preparing the request because it determines whether Xen expects a new specification, current MQL5 source, conversion source or a Strategy Tester report. The active task name appears above the conversation, while the composer shows the controls relevant to that work.

Keep unrelated programs in separate projects. A conversation with one clear purpose is easier to continue and verify. Clear Task starts fresh and is separate from deleting a saved project. Download important source first if you have not confirmed that it was saved.

Build, edit or convert

Build Expert Advisor and Build Indicator start from your description. The Existing tasks require a current MQL5 codebase added through Share source code. After adding it, you can attach another source to merge functionality or provide an example. These roles matter: an example should guide implementation without replacing the current program.

Conversion uses one complete source file and always targets MQL5. Use Convert Strategy for a trading system and Convert Indicator for a chart study. MQL4 also belongs here. Describe any deliberate changes in the optional notes; if no changes are needed, you can submit the attached source without additional wording after confirming permission to convert it.

Tools for checking the result

Fix compiler errors and behaviour bugs in the task you have selected. For your own source, choose Existing Expert Advisor or Existing Indicator, attach the complete file, then use Check Compile Errors. Fix Errors prepares the source and diagnostics in the same task; choose Send to request the repair. Generated responses can display an automatic build result, so read it before assuming the file is ready for your terminal.

Verify requirements compares complete generated source with reviewed requirements. It is a different check from compilation. Analyse Strategy reads an exported Strategy Tester workbook and discusses recorded performance; it does not run the EA or change its source. Choose the tool that answers the question you are investigating.

Models and saved work

Choose a model above the conversation before sending a request. Model Settings controls which generations appear. A reopened project can retain its saved model, so check the selection when returning to older work. Indicator screenshots require an image-capable model; the upload control explains when the current selection cannot use them.

The header opens Projects and History. Projects restore saved work, while History holds complete source snapshots. Response actions let you copy or download .mq5 code and review requirements. Keep downloaded source and custom dependencies together, and use Projects, History and Export when comparing or recovering revisions.