Automation modes
Change which new bot requests may proceed without confusing the mode with account state.
Automation mode is a control on the running session. It affects requests through the shared execution gates; it does not rewrite the saved strategy or automatically clear existing orders and positions.
Mode behavior
| Mode | Bot placement/modification | Bot cancellation |
|---|---|---|
auto | Entries/adds and exits may proceed | May proceed |
entry | Entries/adds may proceed; exits are blocked | May proceed |
exit | Opposite-side exit requests may proceed; entries/adds are blocked | May proceed |
off | Blocked | Blocked |
“May proceed” means this control permits the request. Warmup, L3 review, eligibility, simulator, and broker checks still apply.
How entry and exit are classified
The shared classifier examines the matching position side. No position or a same-side order is an entry/add; an opposite-side request is an exit. Quantity is not independently used to classify a partial close versus an oversized reversal.
An exit mode is therefore not a substitute for verifying close quantity. Follow closing positions and keep strategy-side checks explicit.
What changing a mode does not do
Switching to off does not cancel existing broker orders or flatten positions. It also blocks bot cancellation through this control. Use the appropriate explicit account/order actions when those are the intended operations.
The mode is in-memory session state. Confirm it again after a fresh session or restart; do not assume a previous change persisted in the saved app.
Manual and L3 requests
Manual-source requests bypass the automation-mode choice in the normal path, but do not bypass warmup or every other runtime/broker constraint. L3-originated requests still pass automation checks, even though they bypass the L3 intent hook's own review.
Do not change a strategy's source label to evade controls. Use the execution-controls guide when tracing a blocked request.
Continue with stopping and restarting.