The questions that should be asked

No. Routing is disabled by default, requires an active pairing and an explicit typed confirmation to enable, and only sends orders for signals that arrive after the gate is on. Anything received earlier stays review-only and is never executed retroactively.

Yes. Routing is not restricted by account type, so a live MetaTrader account works the same way a demo one does. That also means the software will happily send real orders once you enable the gate, so verify the whole pipeline on a demo account first, with the smallest volume you can set. One caveat: the MetaTrader 4 connector is shipped and installed by the app, but it has not yet been live-fired against a real MT4 terminal, so MT5 is the verified path today.

Yes, per destination (each broker account), and off by default. The daily loss limit is an amount in the account's currency or a percentage of the day's starting balance, and the day starts at the broker server's midnight or at a UTC hour you pick, for firms that reset differently. The maximum drawdown is a percentage from the highest equity reached, or a percentage from a starting balance you enter, prop-firm style. You can also cap how many copier trades are open on the account and on each symbol; a signal that would go over a cap is refused, and a signal split across several take-profits counts each position. The daily loss limit and drawdown are checked by the MetaTrader EA on the terminal on every tick, so they hold while the desktop app is closed and survive a terminal restart, and deposits, withdrawals and credit are not counted as losses. When a limit is reached, new entries stop: the daily limit until the next trading day, the drawdown until you resume from the app. A manual Resume restarts the limits from the current equity. Optionally, every copier position is closed and its pending orders cancelled at that moment; only trades the copier opened are touched, never your own, and the channel's trade-management instructions for trades already open still apply. The app shows today's result against the limit, alerts you when a limit is reached and lists it on the Activity page, and the dashboard's Accounts page shows whether entries are stopped, with today's result and the limits. It is fail-closed: until the terminal confirms it is guarding with the settings you saved, new entries on that account wait. A destination on an older connector can't turn on the daily loss limit or drawdown and is asked to update the connector; the open-trade caps work with any connector. It helps you stay inside limits you set, but it is not a copy of any firm's rules and it does not guarantee passing a challenge.

Yes, and all of it is off by default. Trading hours are weekday and time windows in your computer's local time, set per destination, per channel, or both; an entry has to fall inside every set of hours that applies, and a window that ends at or before its start runs past midnight into the next day. Per channel you can also take only the symbols you list, or every symbol except them, matched as the channel writes them before any symbol mapping. A maximum spread in pips can be set per destination, and a symbol mapping can set its own. A price-moved limit compares the entry the signal stated with the price you would get (the ask for a buy, the bid for a sell). Both are checked by the MetaTrader EA on the terminal against the live price just before a market order is sent, because only the terminal has the live quote. When the price has moved more than your limit, the destination either skips the trade or, if you choose, places a limit or stop order at the stated entry, with the signal's stop loss and targets and the same size, and the app records it as a pending order. A signal that states no entry is traded at market with only the spread checked, and pending-order signals are not spread-checked. Every pending order a destination places can expire after a number of hours you set, up to 720. Refusals carry their reason, and instructions for trades already open (close, break-even, move SL) are never filtered. The spread and price-moved limits need the updated connector (EA 0.13.0); a destination on an older connector refuses to save them and asks you to update the connector. Trading hours, symbol lists and the pending expiry work with any connector. Pips follow the same automatic pip size as break-even, with a per-symbol override.

Yes, per destination (each broker account), and off by default. The app downloads the public ForexFactory economic calendar for the current week and refuses new entries from a number of minutes before a high-impact event until a number of minutes after it, up to four hours each side; you can include medium-impact events too. A symbol is paused only for its own currencies: EURUSD for euro and US dollar news, gold, oil and US indices for US dollar news, GER40 for euro news, UK100 for pound news, and so on. It is fail-closed: if the calendar cannot be downloaded or does not cover the current week, or the app can't tell which currency a symbol trades in, entries on that account are refused with the reason rather than taken blind. Optionally, a destination closes its open copier positions and cancels their pending orders a set number of minutes before a matching event; only trades the copier opened on the affected symbols are touched, never your own, a failed close is retried a few times, and each close shows its reason in the app's Activity list. Instructions from the channel for trades already open (close, break-even, move SL) still apply during the pause. The news filter is run by the desktop app, so it works with any connector version, but the app has to be running for it (as it does to copy at all). The calendar request carries no account data, and nothing is downloaded while no destination uses the filter.

Yes, per destination (each broker account), and off by default: until you choose otherwise a signal such as "BUY XAUUSD 2350-2345" trades as one entry, exactly as before. The app reads a zone written after an entry label, after "@" or "at", or straight after the symbol, including a short second price such as "2350-45", and only treats it as a zone when the stop loss and the first target are outside the whole of it. You can then trade a zone as one limit order at its middle, or as several orders spread across it: the first enters at market and the rest wait as limit orders further into the zone, the last at its far end. The lot size or the risk is divided equally between the orders and each is split over the take-profits you trade, and orders times take-profits stay within a per-signal limit you set (six by default), so fewer layers are used when a signal has many targets. Prices are placed at the precision the signal was written in. When the channel closes the trade, or any of its positions reaches its target, the orders still waiting are cancelled; "TP2 to …" moves the second target of every layer. A limit order at a price the market has already passed is refused by the broker and reported. Everything is ordinary MetaTrader orders, so it works with any connector.

Yes, per channel, and off by default: until you turn it on, a post that is only a screenshot is skipped, exactly as before. With "Read signals posted as images" on for a chat, a Telegram photo or image file, or a Discord image attachment, is downloaded to your computer and read there with the text recognition built into Windows, and the text goes through the same parser as a typed message, with the caption first. Nothing is uploaded: the image never leaves your computer, and Telegram's downloaded copy is deleted once it has been read. The text it reads is kept like any message text, locally and for seven days. If an image cannot be read (an unreadable picture, no text-recognition language installed in Windows), the post shows in the Signal inbox with the reason and is never traded; when it had a caption, the caption is still read. Recognition works best on clean signal cards and screenshots of text; a chart with the levels drawn on it has no text to read. Windows 10 and 11 include English text recognition; other languages can be added in Windows settings.

Yes, if you want it, and it is off by default. In Settings you can choose an AI provider (OpenAI, Anthropic Claude, Google Gemini, or any OpenAI-compatible server, including one running on your own computer) and enter your own API key. When the parser finds no signal in a message, the message is sent from your computer straight to that provider, never through our servers, and each message it reads is billed to your key under the provider's terms. The AI's answer is never traded as it stands: it is written out as a plain signal and has to pass the same parser rules as a typed message (stop on the safe side of entry, targets on the right side, a symbol you have mapped), then every routing check. It can only read new entries; closing or changing trades stays with the parser and your per-channel consent. By default an AI reading waits in the Signal inbox, marked as read by AI, until you press Trade, and it is still refused if the signal is older than your maximum signal age by then; you can choose to have AI readings traded automatically instead. You also choose whether images are sent: never (the default), only when the text read from them on your computer did not parse, or instead of reading them locally. A Test button sends a sample message so you can check your key and model first. The key is stored with Windows data protection and is never shown again.

Because it arrived before routing was enabled. That is deliberate: the gate is fail-closed and non-retroactive. Send a new signal after enabling routing to see an order move through the pipeline.

Your source sessions live on your Windows machine. Signal messages (Telegram chats, Discord channels) are read locally, and the trade path goes to MetaTrader over a loopback connection on that same machine. No one else's server is on the execution path, and source message bodies are never uploaded. Your account dashboard does mirror structured data from the agent: signals, trades, account snapshots, journal notes, and symbol mappings, so you can review them in the browser. It holds metadata, never message text.

Messages are deduplicated so the same signal is not handled twice, and only new messages are read: text, and image posts on channels where you turn image reading on. History before the chat was selected is not imported. Edited messages are handled deterministically rather than treated as fresh orders.

No. AutoSignalCopier installs its packaged EA (MT5 `.ex5`, MT4 `.ex4`) into a detected installation for you. The EA communicates only with the loopback address on your computer. No DLL imports are required.

We do not publish latency numbers yet. The desktop agent has a latency benchmark in progress, and this site will only state figures once they come from a measured run. Claims you see here are about what the software does, not how fast it claims to do it.

Yes, the machine running the app needs to stay on: reading, parsing, and routing all happen locally on that PC, so there is nothing in the cloud to carry on without it. A Windows VPS works fine for this. Every plan includes 3 paired Windows devices, and a desktop, a laptop, and a VPS together count as three devices at no extra cost.

It reads new text messages, and the text in image posts on chats where you turn that on, and classifies each one with parser version 3 as an entry, a management instruction, or chatter. By default, an entry that names no stop is refused (a routing setting you can change, though a destination sized by risk always refuses one) — and results-style recaps fall to ignored rather than parsing as fresh orders. Chat history is never imported. A message that does not fully match the expected shape is held for review in the inbox instead of being guessed at: nothing partial is ever ordered. If you turn on AI reading (off by default), such a message can be read by an AI you choose, and its reading still has to pass the same parser rules. Management instructions such as close or move SL act only on channels where you have turned trade management on, which is off by default.

When a provider replies “close half” or “move SL to entry”, parser version 3 classifies the message as a management instruction and turns it into protocol commands: close, partial close, break-even, move SL, move TP, cancel pending, or close all — one message can become two commands. Nothing runs automatically: each channel needs its own explicit consent, and consent is off by default. Binding follows a strict ladder — the reply link first, then the named instrument against that channel's open trades — and anything that matches nothing is refused with a reason rather than guessed at. Close-all wording only ever touches positions the copier itself opened, a lapsed subscription stops new entries without trapping you in open trades, and an edit made after routing is stored and shown while the trade itself is left alone. On a signal split across several take-profits, close, close half, break-even and move SL apply to every open position of that signal, while “TP2 to X” moves only the second position's target. Separately from the channel, a destination can move stops by its own break-even and trailing-stop rules, which are off by default.

Per destination, in one of three modes, alongside an explicit mapping from the provider's symbol to your broker's symbol (EURUSD to EURUSD.a, for example). Fixed lots is the default and sends exactly the volume you set. The two risk modes size each trade to risk either a percentage of balance or equity (up to 20%) or a fixed amount in the account's currency: the MetaTrader EA computes the lot at execution time from the live price, the signal's stop-loss distance and your broker's tick value, rounds it down to the broker's volume step so it never risks more than you set, and caps it at your own max lot for that symbol mapping and at the broker's maximum. Risk sizing is fail-closed. A signal with no stop loss is refused on a risk-sized destination rather than given a guessed volume. A lot that rounds below the broker's minimum is refused, unless you opt in to trading the minimum instead, which can risk more than you set. A destination still on an older connector refuses risk sizing and asks you to update the connector. An optional per-channel risk weight (0.5× for a provider you trust less, say) scales the risk, and the app previews what one trade risks from the terminal's last reported balance or equity. On a destination that uses every take-profit, the fixed volume or the risk is divided across the positions, never applied to each one.

Your choice, per destination. The default is TP1 only: one position with the first target, as before. Switch a destination to every take-profit, split equally or by your own shares (50/30/20, say: 2 to 10 shares adding to 100%), and an entry that lists several targets opens one position per target, each with its own take-profit and the entry's stop loss. On fixed lots the volume is divided by the split and each part is rounded down to the broker's volume step, so the total is never more than you set. If a part would fall below the broker's minimum, the last targets are dropped and their share is spread over the rest: the trade still goes on with fewer targets, and the signal records how many were opened. On a risk-sized destination the risk per trade is divided the same way and the EA sizes each position; one that sizes below the broker's minimum is refused, unless you opt in to trading the minimum. A custom split with fewer shares than the signal has targets uses only the first targets, and one with more shares than targets is rescaled over the targets present. Trade management from the channel (close, close half, break-even, move SL) applies to every open position of that signal, “TP2 to X” moves only the second position's target, and the dashboard's Trades page groups the positions under their signal.

Yes, per destination, and off by default: nothing changes until you opt in. Break-even has four settings. Off is the default. After TP1 is hit needs the destination to use every take-profit: when the first position of a split signal closes at its target, the other positions of that signal move their stop to entry. The desktop app makes that move, so it has to be running. After X pips in profit, and after a multiple of the stop (R), run inside the MetaTrader EA; 1R is the distance from entry to the signal's stop loss, so on a destination set to R a signal without a stop is refused. An optional offset locks in a few pips past entry in the trade's favour, to cover spread or commission; it defaults to 0. The trailing stop starts after X pips in profit, keeps the stop Y pips behind price and moves in steps of at least Z pips, and it only ever tightens the stop, never loosens it. The pip and R rules and the trail run in the EA on the terminal (MT5 and MT4), so they keep working while the desktop app is closed. They are saved in the terminal's files and survive a terminal restart, and a pending order's rule starts when it fills. Pip size is automatic: 0.1 for gold, 0.01 for silver, 10 points on 3- and 5-digit quotes, otherwise 1 point, and you can set a pip size on a symbol mapping where your broker differs. Broker stop-level and freeze-level limits are respected: a stop that can't be placed yet is retried on the next ticks. These rules need the updated connector (EA 0.11.0); a destination on an older connector refuses to save them and asks you to update the connector. Each move appears in the app's Activity list as “Stop moved by rule”, and the channel's own management messages (move SL to entry, for example) still apply where that channel's trade-management consent is on.

Yes. AutoSignalCopier signs into your own account using Telegram's standard login (QR code or phone number) from the app on your PC. There is no separate bot to add and no token to copy between devices.

From $10 a month for one trading account, live or demo, plus $5 for each additional account. Paying quarterly takes 10% off, and paying yearly is ten months for twelve. The 7-day trial runs on the quarterly and yearly plans with no payment method; the monthly plan has no trial.

The trial runs for 7 days on the quarterly and yearly plans, with the full pipeline and up to 3 trading accounts, and asks for no payment method. The monthly plan has no trial: a month at a time is billed from the start. After the trial you pay per trading account: $10 a month covers one, and each additional account adds $5. A demo account counts the same as a live one. Paying quarterly takes 10% off, and paying yearly is ten months for twelve. Every plan includes 3 paired Windows devices. Choose a cadence and an account count on the pricing page and check out from your dashboard; payments are processed securely by Stripe, subscriptions renew automatically, and you can cancel any time from the billing portal.

Password resets are support-assisted for now. There is no self-service reset link on the login screen. Email us from the address on your account and we will reset it for you. The same goes for cancelling a plan or deleting an account: contact support and we will handle it.