Skip to content

Xen AI Developer Mode for cTrader Code

What the Mode Toggle Does

Xen includes a Developer Mode toggle in the top menu. This setting controls how code is returned, not what Xen builds. The selected mode determines whether Xen returns a full, compile-ready file or targeted code snippets with placement guidance. Choosing the right mode depends on how much control you want over the code and how you prefer to work.

Watch Video Explainer

Watch this video to learn how to use the developer mode of Xen AI.

Tip: Set the video quality to HD (1080p) for the best viewing experience.

Standard Mode

What Standard Mode Does

Standard Mode is the default workflow. In this mode, Xen returns a complete updated source file whenever code is generated or modified. This approach is designed for simplicity. You receive a full file that can be copied, compiled, and tested without needing to merge changes manually.

When to Use Standard Mode

Standard Mode is best when you want speed and minimal effort. It is well suited to building new tools or making straightforward updates without worrying about code structure.

Use Standard Mode when:

  • you want a full working file returned each time
  • you are building a new cBot, indicator, or plugin
  • you prefer a simple workflow with minimal manual editing
  • you want to avoid merging snippets

How Standard Mode Works

Xen generates a baseline implementation once requirements are clear, then continues returning full updated files for each change. This keeps the process simple and consistent, especially for users who are not editing code manually.

Typical use cases include building new trading robots, creating indicators, converting tools between platforms, and making direct changes where a full file is preferred.

Developer Mode

What Developer Mode Does

Developer Mode changes how Xen returns code. Instead of generating a full file, it provides targeted code snippets for specific changes.

Each snippet includes:

  • a short description of the change
  • the exact location where it should be applied
  • the code required for the update

This allows you to apply changes manually and maintain full control over your code.

When to Use Developer Mode

Developer Mode is designed for incremental development and is better suited to users who are comfortable editing code.

Use Developer Mode when:

  • you want to apply changes manually
  • you prefer smaller, controlled edits
  • you are extending an existing file step by step
  • you want to avoid unnecessary full file rewrites
  • you need clear separation between logic changes

How Developer Mode Works

Xen returns only the code required for the requested change. If multiple updates are needed, they are split into separate sections with clear placement instructions. This approach is more controlled and is particularly useful when debugging or adding features gradually.

First Build vs Later Changes

A practical way to use the two modes is to separate initial builds from later modifications. For the first implementation, a full working file is often required to establish a baseline. Standard Mode is usually the easiest way to achieve this. Once a working file exists, Developer Mode becomes more useful. It allows you to add features, adjust logic, and test changes incrementally without replacing the entire file.

Choosing the Right Mode

The choice between Standard Mode and Developer Mode depends on how you prefer to work.

Choose Standard Mode if:

  • you want a complete source file returned
  • you prefer a simpler workflow
  • you do not want to merge code manually

Choose Developer Mode if:

  • you want snippet-based updates
  • you prefer full control over code changes
  • you want to build and test in smaller steps

A structured workflow improves results regardless of the mode you choose.

A typical approach is:

  1. Start with a working baseline
  2. Compile and test the result
  3. Add one feature at a time
  4. Compile and test after each change

Standard Mode Workflow

Use this approach when you want Xen to manage the full file:

  1. Describe the tool you want to build
  2. Xen returns a complete file
  3. Compile and test
  4. Request another change
  5. Xen returns the updated file

Developer Mode Workflow

Use this approach when you want controlled edits:

  1. Start from an existing working file
  2. Request a single feature or modification
  3. Xen returns code snippets
  4. Apply the snippets in the correct locations
  5. Compile and test before continuing

What Developer Mode Does Not Change

Developer Mode does not affect the task you are using or how Xen interprets your request. It also does not change the selected AI model or the rules of the cTrader platform. It only changes how code is returned.

Common Mistakes to Avoid

Most issues come from using the wrong mode for the task or combining too many changes at once.

Avoid these common mistakes:

  • using Developer Mode when you expect a full updated file
  • adding multiple features before testing
  • forgetting to apply all returned snippets
  • making vague requests without defining the change clearly
  • switching modes without understanding the difference

A controlled, step-by-step approach produces the most reliable results.