Documentation
Strategy Workflow (Build, Review, Save, Deploy)
1) Build In Chat
The fastest way to get good results is to be explicit: tell Astral the asset(s), timeframe, entry condition, exit condition, and risk rules. You can also ask it to revise an existing strategy rather than starting over.
"Build a strategy for SPY on 15m. Enter when [condition]. Exit when [condition]. Add a stop loss and a take profit. Show me the backtest."
"Keep the same strategy but reduce overtrading," "change timeframe to 1h," "add a volume filter," or "tighten stop loss."
2) Review Code and Backtest
Astral can generate code and backtest outputs into the main panel. Use the code view to sanity-check strategy logic and the backtest view to decide whether a strategy is worth saving or deploying.
- Check return, drawdown, win rate, and trade count together (not in isolation).
- Look for suspiciously low trade counts or unrealistic performance spikes.
- If results look wrong, ask Astral to explain the current logic before changing it.
3) Save and Reopen
Saved strategies are surfaced in the strategies flows (modal/dashboard widgets). You can reopen strategy details, inspect metrics, and run another backtest from detail views.
4) Deploy For Alerts
Deployment is how you operationalize a strategy. In current app behavior, deployment always requires a notification profile, and alert-driven monitoring is the default safe path for most users.
Deployment Modes in the UI
The deploy modal exposes an alert-only mode and a connected mode (with broker/account/cash allocation fields). Connected execution availability may depend on your backend/account rollout. If you are unsure, use alert-only.