Autopilot: arming, guards and the STOP button
Autopilot runs one of your saved strategies on the connected broker account, one decision per closed bar, with real orders. Nothing leaves until you arm it by typing ARM, and arming is never persisted across restarts.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Broker account panel → Autopilot; the armed panel is repeated at the top of the panel
- Arming word
- ARM, typed exactly
- Persistence
- Strategy, guards and the acknowledgement are saved; the armed state never is
- Default guards
- Max daily loss 500, max contracts 2, no session window, flatten at session end on
- Decision cadence
- One per newly closed bar; never on the bar in formation
- Journal
- Up to 200 entries kept, the 12 most recent displayed
What it does
The panel states its own contract: it runs one of your strategies on this account, one decision per closed bar, with real orders; nothing leaves until you arm it, and STOP disarms and flattens. The strategy list only offers scripts saved as strategies on the scripting page; with none saved the selector reads "no strategy saved".
A decision from the strategy never becomes an order directly. It passes through a pure planner that confronts it with every guard in turn: armed, not stopped, acknowledged, daily loss, session window, contract cap. The planner returns a plan — skip, flatten or enter — and the execution layer only obeys it.
There is no pyramiding: a buy while already long does nothing. A reversing signal turns the position in a single order carrying the closing quantity plus the opening quantity, so there is no window where the account is unintentionally flat. There is no automatic retry either: a refused order disarms, and the journal records why.
Once armed the panel switches to a live view with a decision counter, the last decision, the last error, a Disarm button that keeps positions, and the STOP button. An armed autopilot is also rendered as a band at the top of the account panel so the STOP is reachable without scrolling.
Settings
| Setting | Default | What it changes |
|---|---|---|
| Strategy | none selected | Which saved strategy script produces decisions; arming is refused without one |
| Max daily loss ($) | 500 | Minimum 1, step 50. Reaching it flattens any position and disarms |
| Max contracts | 2 | Minimum 1, whole numbers. Caps both the order quantity and the resulting position |
| Session from (local) | empty | HH:MM local time; empty means all day. An unreadable value closes the window entirely |
| Session to (local) | empty | HH:MM local time; a window may cross midnight |
| Flatten when the session window closes | on | Flattens an open position on leaving the window instead of only blocking entries |
| Automated trading acknowledgement | off, per connection | Confirms your firm allows automated trading on this account; arming is refused without it |
| Arm word | empty | Must read ARM exactly; anything else is refused with a message |
How to use it
- Write and save a strategy on the scripting page, then select it in the panel.
- Set the daily loss and contract caps before anything else; both are validated and block arming when they are not a positive amount and a whole number of at least one.
- Tick the acknowledgement only if your own contract allows automated trading. The label names firms that forbid it on funded accounts.
- Type ARM and press the Arm button. Use Disarm to stop taking decisions while keeping positions, and STOP to disarm and flatten.
- After a STOP, the panel demands a broker-side check: confirm you have inspected positions and working orders on the original account before releasing it.
Limits and pitfalls
Arming is volatile. Restarting the application, closing the chart or changing its symbol disarms, and the state is never restored from disk.
Unknown risk data blocks new exposure: when the daily profit and loss is unavailable for the armed account, no entry is planned, while an explicit close decision still goes through so the risk-reduction path is never lost.
Each execution belongs to an arming session. If the session changes while an order is in flight, no new entry and no stop or target is placed on the stale decision — a stop placed after a flatten would be an entry order, not a protection.
Releasing the STOP does not confirm any broker state and does not restart trading. The application cannot prove what the gateway did with a lost acknowledgement or a late fill, so it asks for a human check instead of implying a clean account.
Related pages
This page in other languages
Frequently asked questions
- Does autopilot come back armed after a restart?
- No. The armed flag, the armed symbol, the armed account and the arming session are deliberately excluded from persistence. Only the strategy choice, the guards and the per-connection acknowledgement survive a restart.
- What happens when a broker rejects an autopilot order?
- The autopilot disarms and the refusal is written to the journal. It never resends: an automatic retry is exactly what a prop firm reclassifies as uncontrolled automated trading, and it is also how a position gets doubled unnoticed.
- Why can the STOP button be greyed out?
- It is disabled while stop requests are still pending, so a second flatten cannot be fired blindly at an account that may have changed in the meantime.