Trader Signal Copier

Trader Signal Copier

Copy supported text signals from selected Telegram channels to assigned MetaTrader 5 accounts. One customer installation supports up to seven accounts and seven source channels. A required Windows companion handles the customer's Telegram connection and routing; the native Expert Advisor executes orders and manages signal-specific TP1 protection.

Requirements before purchase

• Windows 10/11 x64, Python 3.11 x64 with pip and Tcl/Tk, internet access and the version-matched Windows companion.
• Dedicated MT5 terminals on the same Windows computer and user account. Hedging accounts are required for separate target positions; MT4 and netting accounts are unsupported.
• The customer supplies their own Telegram account, API application, channel access and broker accounts. Signal subscriptions are not included.
• This is a copying utility. It does not generate trading signals or guarantee profit. It requires the complete Windows stack and is not a self-contained MetaTrader Virtual Hosting migration.

Trading and protection rules

• Assign every selected source and account to an explicit routing group. Routes can copy one or several channels to one or several accounts without overlap between groups.
• Multiple take-profit levels create separate positions. Each TP position targets 1% of current equity before costs and slippage. The 0.01-lot minimum is allowed even when it exceeds that target. Five target positions can therefore target roughly 5% combined stop risk or more with minimum volume. There is no aggregate portfolio risk cap.
• Contracts must support the 0.01-lot floor and compatible volume steps. Higher broker minimums are rejected rather than silently increasing volume.
• When TP1 is reached, remaining positions from that signal move SL to their own actual entry prices when broker rules permit. Their targets and more-protective stops are preserved. Manual positions and other signals are excluded.
• Attached receivers continue managing already-owned positions if Telegram or the companion disconnects. Power, a running terminal and broker connectivity are still required.
• Historical Telegram messages are not replayed. Unsupported or incomplete posts are skipped. Uncertain submissions are reconciled and never blindly resent.

Supported source policies

Complete signals require an explicit instrument, BUY or SELL direction, stop-loss, numeric targets and an entry range or price. Explicit ranges remain ranges. Optional per-route policies support fresh, complete BUY NOW or SELL NOW posts without an entry price. A final open target can use average spacing only for the supported explicit-reply format with verified instrument tick-size pins. Unlinked replies and ambiguous posts are skipped.

Customer installation

1. Install the purchased receiver through MT5 Market using the purchasing MQL5 account. Install a dedicated broker terminal for each account and sign in with the trading/master password, not an investor password.
2. Install the matching Windows companion and open Customer setup. Connect the customer's Telegram locally. Request the login code, enter it in Telegram login code and sign in locally; use the two-step password only if requested. Do not send credentials to the seller.
3. Select up to seven joined channels. Add account labels, exact terminal executable paths, logins, servers and broker symbol mappings. Start in demo mode, create routes and save settings; copying remains OFF.
4. Choose Prepare EA pairings. Attach the receiver to one chart per terminal. In Inputs, Load that account's generated SET file and click OK. Enable EA and toolbar Algo Trading. Keep DLL imports disabled. No WebRequest URL is required; the receiver uses local MT5 Common Files.
5. Run Verify accounts (no orders). Confirm the exact identities, hedging mode, fresh quotes, receiver pairing and trading permissions. Then start copying and check the advancing heartbeat and entry-ready routes.
6. Observe a complete demo signal, its SL/TP, sizing, TP1 stop move and restart behaviour before considering live use. Launch requested is not proof that the copier is ready.

Receiver inputs

• InpInstallationId: local installation identity from the companion's generated pairing file.
• InpReceiverId: receiver identity for this account and terminal.
• InpPairingKey: private local command-pairing key. Keep the SET file private; it is not a broker password or seller licence key.
• InpAllowLive: false by default. Live operation additionally requires explicit account-bound consent in the companion. A demo pin cannot attach to a live account.

Reports, Hermes and recovery

Optional PDF channel-performance reports can be delivered to the customer's Telegram Saved Messages Monday to Friday at 16:00 CAT while the computer and internet are running. Optional Hermes integration provides real status, verification and guarded start/stop tools. Hermes, Honcho and model services require the customer's own authentication; free-model availability is provider-controlled. LLM access is not needed for deterministic sizing or native TP1 management.

Recovery after Windows sign-in is opt-in and rechecks the approved identities. It never replays missed messages. During a power outage, broker-side SL/TP can remain, but no local TP1 stop move can run. Use a UPS or host the full Windows stack on a Windows VPS for continuity.

Support is provided through MQL5 product comments and private messages to jmakusha. Never send Telegram sessions, pairing files, account passwords or provider tokens in support messages.