Appearance
AI commands & examples
Use AI recognition to translate supported trading instructions into the same RFC commands used by the EA. This reference shows what to send as a standalone Telegram message and what to send as a reply to an original signal.
Configure Signal parsing & AI recognition first. Parser + AI uses AI when the current parser cannot read a message; Try AI lets you inspect AI-derived results without executing them. Messages already understood by the current parser still follow its normal execution path.
Prices and volumes below illustrate syntax only. Preview examples with your profile before using them in an execution-enabled channel.
Choose the command scope
- Standalone message: specify
ALLor a source symbol such asGOLD.closealone does not meanclose all. - Reply to the original signal: targets the tracked trade group belonging to that signal.
close allsent as a reply still means that group, not all groups. - Account and EA controls: commands such as
start,stop, andallow buydo not become group-specific when sent as a reply. Send these independently.
ALL uses the existing RFC scope on each account receiving the command through channel routing. It can cover multiple signal groups tracked by that EA; it is not limited to the signal most recently received. It does not select every account in the workspace or include unrelated manual positions outside the EA's tracked groups.
Symbol names refer to the source symbol in the signal. Symbol mapping resolves that symbol to the broker's instrument.
Close positions and cancel pending orders
| Intended action | Standalone message | Reply to the original signal |
|---|---|---|
| Close the full selected scope | close all | close or close all — only the replied group |
| Close a source symbol | close GOLD | close — the replied group identifies the target |
| Close only BUY or SELL targets | close BUY GOLD or close SELL GOLD | RFC CLOSE BUY or RFC CLOSE SELL |
| Close half the volume | close HALF GOLD | close half |
| Close a percentage | close 35%GOLD | close 35% |
| Close a specified lot volume | close 0.10 GOLD | close 0.10 |
| Close a particular TP leg | Requires a reply | RFC CLOSE TP2 HALF or RFC CLOSE TP3 0.05 |
| Cancel pending orders | cancel all or cancel GOLD | cancel |
Percentages and specified lot volumes apply to each selected position according to the EA's close rules, not to one combined group volume. The broker's minimum volume and volume step still apply. close also cancels selected pending orders; cancel affects pending orders only.
The following complete phrases are supported equivalents:
| Message | RFC equivalent |
|---|---|
close all | RFC CLOSE ALL |
please close all positions | RFC CLOSE ALL |
đóng tất cả vị thế | RFC CLOSE ALL |
cancel all pending orders | RFC CANCEL ALL |
hủy tất cả lệnh chờ | RFC CANCEL ALL |
AI must preserve an explicit symbol, side, percentage, or lot volume. It cannot widen close GOLD into close all or turn a partial close into a full close.
Update SL/TP and add an entry
| Intended action | Standalone message | Reply to the original signal |
|---|---|---|
| Move SL to entry | SL ENTRY GOLD or SL ENTRY ALL | RFC SL ENTRY or move SL to entry |
| Move TP to entry | TP ENTRY GOLD or TP ENTRY ALL | RFC TP ENTRY |
| Set a new SL | Use a reply | SL: 2500 or RFC UPDATE SL TO 2500 |
| Update a particular TP | Use a reply | TP2: 2520 or RFC UPDATE TP2 TO 2520 |
| Remove SL or a TP | Use a reply | SL: 0 or TP2: 0 |
| Add an entry using the original signal | Requires a reply | layer or layer now |
Use a reply when setting a new numeric SL/TP on an existing trade group. Although SL GOLD TO 2500 is recognized as an RFC-style SL update, a new standalone message does not identify the original signal group for this edit and can be rejected because the target is not found. Prefer SL: 2500 or RFC UPDATE SL TO 2500 as a reply.
A reply update can contain several SL/TP fields, one per line:
text
SL: 2500
TP1: 2510
TP2: 2520TP indices remain unchanged: updating TP2 does not rename or update TP1. An explicit 0 clears the specified level; omitting a field leaves it unchanged. A layer command uses the original tracked signal and remains subject to the applied profile's entry and risk rules.
Moving SL or TP to entry uses the opening price. It does not account for fees or guarantee a final net result of zero.
EA controls and information requests
Use these complete commands independently. An optional RFC prefix uses the existing structured grammar directly, for example RFC STOP.
| Message | Meaning |
|---|---|
start | Clear the EA runtime's stopped state. Other execution permissions still apply. |
stop | Set the EA runtime's stopped state. This is not a request to close existing positions. |
allow buy | Allow the BUY direction through the EA runtime's direction control. |
allow sell | Allow the SELL direction through that control. |
allow all | Allow both BUY and SELL directions through that control. |
status | Request runtime status. |
account | Request account information, including balance, equity, free margin, and currency. |
listorder | List active orders and positions tracked by the EA. |
market GOLD | Request a quote for the source symbol after broker mapping. |
help | Request the supported command list. |
These commands retain their RFC scope even when sent as replies. A reply does not limit stop or allow buy to the original signal. start and allow all do not override permissions or other execution restrictions.
New opening signals
Send opening signals as standalone messages. Examples include:
text
BUY XAUUSD SL 2490 TP1 2510text
SELL LIMIT EURUSD ENTRY 1.10 SL 1.11 TP1 1.08AI also recognizes a minimal market signal such as xauusd @ mua as BUY XAUUSD. Entry, SL, TP, and lot may be absent at the recognition stage; the applied profile and account rules decide whether execution is permitted. Pending orders still require an explicit entry price. STOP LIMIT orders are not supported.
See Supported signal text for entry layouts, pip distances, and original-message edits.
Messages that need review or cannot execute
Send one clear command per message. Several fields in one SL/TP update count as one update, but separate actions such as close all and start must not be combined.
| Message or situation | Expected handling |
|---|---|
close without a reply or target | Needs a target; it must not become close all. |
close all except GOLD | Unsupported exclusion; it must not become an unrestricted close. |
do not close all or if price falls, close all | Must not become an unconditional close. |
TP hit, SL hit, or a report that positions were already closed | A result report is not a fresh trading command. |
| An unclear target, conflicting instructions, or invented prices/symbols | Requires review or is rejected. |
| Editing an old message into a close, layer, or account-control command | Does not replay that command. Send a new message instead. |
| Editing a reply command | Is not treated as a newly executable command. |
Recognition does not confirm execution. Commands still pass channel routing, profile and account permissions, ownership checks, runtime restrictions, and broker validation. Inspect Signal log and Execution for the recorded outcome.