Start with exchange permissions
A bot workflow should never require withdrawal access. Read and trade permissions are enough for connected execution, while demo and testnet modes are better for validating logic.
The web command center follows that pattern by exposing a safe Binance testnet restart flow for DCA and grid bots, while live connected-exchange execution remains a deliberate advanced step.
Budget is a risk setting
DCA and grid strategies can quietly expand exposure if budgets, levels, and price steps are chosen casually. The first review should show budget per level, expected order count, and whether the symbol duplicates existing portfolio risk.
SignalPilot keeps bot controls next to active reports, exchange state, and order diagnostics so the trader can see the plan and the consequences together.
Reports need to refresh close to execution
A bot report from yesterday is not an execution signal today. Before restarting a strategy, refresh active reports, open orders, and recent events.
This is why the web AI Bot workspace includes report refresh actions and record-level bot actions alongside the shared portfolio and signal data.