koni-ea

Build a trading bot for Senti — starting from a template that already gets the hard parts right.

You write MQL5 source. Senti compiles it and runs it. No MetaEditor, no .ex5, no Windows machine — paste your .mq5 into Senti's Author Studio, press Compile, press Save as EA, deploy. It then runs on Senti's terminals against your linked broker account, 24/5, whether your computer is on or not. Read this first →

Two things ship from this repo:

• templates/ — a complete, correct MQL5 Expert Advisor skeleton. Copy it, replace one function, compile, deploy.
• skills/ — agent skills that teach an AI assistant the MQL5 standard, so it writes correct EA code with you instead of plausible-looking code.

---

Quick start

git clone https://github.com/Koniverse/Koni-ea.git
cp -r koni-ea/templates/mql5/STARTER_EA  my-bot

Replace Signal() with your entry logic, then paste the .mq5 into Senti's Author Studio and press Compile. The full loop is in the template README.

Working with Claude? Install the skills and it applies the MQL5 standard as it writes:

npx skills add Koniverse/Koni-ea --skill koni-ea-dev --skill koni-ea-ops

Working with an AI assistant? Point it at AGENTS.md and it will pick up the workflow and the rules.

---

How it works

You write MQL5 source. Senti compiles it. Four steps in the browser:

YOU                            SENTI — Author Studio
  write MQL5                     ① + New draft
  (Claude, the built-in          ② paste .mq5 → Compile
   assistant, or by hand)             safety scan → headless MetaEditor → 0E 0W
        │                        ③ Save as EA  → private EA + preset
        └── copy source ───────▶ ④ Deploy      → runs on a Senti terminal, 24/5

You do not need MetaEditor, an .ex5, a .set file, or a Windows machine. You need a browser. Senti compiles the source, builds the preset from your input defaults, stores the binary, attaches it to one of its terminals against your linked account, and restarts it if the terminal goes down. Your bot lands in your private catalog — only you see it.

Warning

If you do compile locally, keep that MT5 on a demo account. The same bot running on your machine and on Senti against one broker account doubles every position and leaves each instance managing trades the other opened. Silently.

The full model — the safety scan, what it rejects, and why Senti runs the bot instead of you — is in docs/RUNNING-ON-SENTI.md.

---

Why start from the template

An Expert Advisor is mostly not the strategy. It is the chassis around it: order placement, position sizing, stop distances, restart recovery, risk cut-outs. Get any of those wrong and the failure is silent — the code runs, the backtest is green, and the loss shows up on a live account.

The template implements that chassis correctly, so the only thing left for you is the part that is actually yours:

int Signal(...)
{
   //=================== REPLACE FROM HERE ==========================
   // your entry logic — return +1 long, -1 short, 0 stand aside
   //==================== REPLACE TO HERE ===========================
}

Already handled for you: signals on closed bars so nothing repaints · position sizing that respects the risk budget · SL/TP clamped to the broker's minimum stop distance · a latched equity circuit breaker · a daily loss limit · a margin pre-check · state that survives a restart · positions filtered by symbol and magic.

Each of those is a specific production bug documented in mql5-pitfalls.md.

---

Available skills

Install into your own project so your AI assistant applies the standard as it works:

npx skills add Koniverse/Koni-ea --list                  # browse
npx skills add Koniverse/Koni-ea --skill koni-ea-dev     # install one
npx skills add Koniverse/Koni-ea --skill '*' --agent '*' # install all, all agents

Skill	What it does
koni-ea-dev	Programming a correct MQL5 EA — lifecycle and event model, order placement and signal timing, position sizing and SL/TP, risk and money management, and the production pitfalls that only bite live
koni-ea-ops	The lifecycle of a released EA — v<X.YY> versioning and bump rules, MagicNumber registry, deployment to an MT5 terminal, release backtest requirements, per-version documentation

---

Documentation

Doc	For
docs/RUNNING-ON-SENTI.md	Where your bot runs, and why it is not your machine
templates/mql5/STARTER_EA/README.md	Building your first bot, step by step
docs/SETUP.md	Full setup, including the MetaTrader side
AGENTS.md	AI assistants — the workflow and the rules
REPO_STRUCTURE.md	Where things live and how to add one
CONTRIBUTING.md	Sending a template or skill back upstream
SUPPORT.md	Getting help, and what this project does not cover
SECURITY.md	Reporting a vulnerability, and the threat model
CODE_OF_CONDUCT.md	Community standards
docs/CHANGELOG.md	Release history

Everything in this repository is written in English — code, comments, docs, and commit messages. CI enforces it.

---

Requirements

• A Senti account with a linked broker account. That is the runtime, and Author Studio is where you compile.
• A browser. That is the whole toolchain.
• Optionally, a local MetaTrader 5 — only if you want to run the Strategy Tester yourself. It is not needed to build, compile, or ship. If you do run one, keep it on a demo account (why).
• No build tooling for this repo itself; it is markdown and MQL5 source.

---

Risk

Automated trading can lose money faster than manual trading, and on a leveraged account it can lose more than you deposited.

The templates here are not profitable strategies. Their shipped strategy stubs are deliberately naive and documented as such — they exist to show you where your logic plugs in. Nothing in this repository is financial advice. Test on a demo account first. You own what your bot does.

---

License

MIT — use it, modify it, ship commercial bots with it. No warranty.