Skip to content

Developer Mode

What the Mode Toggle Does

Xen includes a Developer Mode toggle in the top menu.

This toggle controls how Xen returns code, not what task Xen performs.

The selected mode affects whether Xen returns:

  • a full compile-ready file
  • or targeted code snippets with placement guidance

This helps you choose the right workflow for your level of control.

Standard Mode

What Standard Mode Does

Standard Mode is the default workflow.

In this mode, Xen is designed to return a complete updated source file whenever code is generated or modified.

This is useful when you want Xen to handle the full implementation for you.

Best For

Use Standard Mode when:

  • You want a full working file returned each time
  • You are building a new cBot, indicator, or plugin from scratch
  • You want the simplest workflow with less manual editing
  • You prefer to copy, compile, and test a complete file

How Standard Mode Works

In Standard Mode, Xen will generally:

  • Generate a baseline implementation when requirements are sufficient
  • Return a full updated file for requested changes
  • Keep the workflow simple for non-developer users
  • Reduce the need to manually merge snippets

Typical Use Cases

Standard Mode works well for:

  • Building a new trading robot
  • Building a new indicator
  • Building a plugin
  • Converting a cBot or indicator
  • Making straightforward code changes where a full file is preferred

What Developer Mode Does

Developer Mode changes Xen output from full files to targeted code snippets for additional features and modifications.

Instead of rewriting the entire file, Xen focuses on the specific code required for the requested change.

Each snippet is returned separately and includes:

  • a short description of the change
  • the exact location where the code should be added or modified
  • the code block itself

Best For

Use Developer Mode when:

  • You want to make changes manually
  • You want smaller, controlled edits
  • You prefer to review and merge code yourself
  • You are extending an existing file one feature at a time
  • You want to reduce unnecessary code repetition

How Developer Mode Works

In Developer Mode, Xen will generally:

  • Return snippets only for additional features or modifications
  • Split changes into separate sections when multiple edits are required
  • Tell you exactly where each snippet belongs
  • Avoid returning the full file unless you explicitly ask for it

This makes Developer Mode better suited to iterative development.

First Build vs Later Changes

A useful way to think about the two modes is:

First Implementation

For the first implementation of a tool, Xen may still need to generate a full working baseline so there is a complete starting point.

Later Feature Requests

After a working file exists, Developer Mode is intended for smaller feature additions and modifications using snippets.

This is especially useful when building gradually and testing after each change.

When to Use Standard Mode Instead of Developer Mode

Choose Standard Mode if:

  • You do not want to merge snippets manually
  • You want one full updated file after each request
  • You are working on a simpler workflow
  • You want Xen to handle the whole file structure for you

Standard Mode is usually the best choice for users who want speed and simplicity.

When to Use Developer Mode Instead of Standard Mode

Choose Developer Mode if:

  • You want tighter control over edits
  • You prefer smaller changes instead of full rewrites
  • You want to apply and test one feature at a time
  • You are already comfortable editing C# code manually
  • You want clearer separation between parameters, methods, helpers, and logic changes

Developer Mode is better for careful, incremental development.

For most projects, the best 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 when you want Xen to manage the whole file.

Typical flow:

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

Developer Mode Workflow

Use this when you want small changes only.

Typical flow:

  1. Start from an existing working file
  2. Request one new feature or modification
  3. Xen returns separate snippets
  4. Add the snippets in the stated locations
  5. Compile and test before the next change

This workflow is more controlled and usually better for debugging.

What Developer Mode Does Not Do

Developer Mode does not change:

  • the selected task
  • the AI model you use
  • the cTrader platform rules Xen follows
  • whether Xen builds a cBot, indicator, or plugin

It only changes how code changes are returned.

Common Mistakes to Avoid

  • Using Developer Mode when you really want a full updated file
  • Adding multiple features at once before testing
  • Forgetting to apply all returned snippets
  • Requesting vague changes without naming the feature clearly
  • Switching modes without understanding the effect on output format

The cleanest workflow is to make one change at a time and validate it before continuing.

Which Mode Should You Choose

Choose Standard Mode if:

  • You want a full source file returned
  • You want the easiest workflow
  • You do not want to merge snippets manually

Choose Developer Mode if:

  • You want snippet-based updates
  • You want manual control over edits
  • You want to build and test in smaller steps

You may also want to explore: