Once a strategy is live, you mostly watch — but you need to know where to look.
BlaveClaw sends Telegram messages to your bot when strategies take action. You'll receive a notification when:
You will not receive a notification on every scheduled run — only when there's a position change. A 1h strategy that stays long for a week will produce no notifications during that week until it exits.
Each strategy has its own folder under strategies/. Inside:
| File | What it contains |
|---|---|
state.json | Current position state: what position the strategy thinks it's in, entry price. Updated every run. |
strategy.log | Full log of every execution — each run is timestamped. If something went wrong, start here. |
stats.json | Backtest performance metrics and daily returns. Updated each live run to include live data. |
pnl.png | Equity curve chart, updated each run. Shows combined backtest + live performance. |
orders.jsonl | (In manager/ folder) Every order placed by the reconciler, one JSON per line. |
Open any of these via the Web IDE, or ask the agent to read them:
"show me the current state of btc_sma_cross" "btc_sma_cross 現在的部位是什麼"
The most reliable check is strategy.log. Each run appends a timestamped line. If the last entry is more than 2× the strategy's interval ago, something has stopped.
You can also ask the agent:
"幫我確認 btc_sma_cross 有沒有在跑" "check if the cron job for btc_sma_cross is still active"
All strategy activity is logged automatically. If you want to review past trades, position changes, or order history, just ask the agent:
"Show me the trade history for btc_sma_cross" "How many trades did btc_sma_cross make this month?"
The agent will read the log files and summarize what it finds.
Strategy ran but no order was placed. Normal — this means the signal didn't change from the previous run. The strategy is running correctly; it just didn't need to do anything.
Telegram alert: reconciler restarted. The reconciler crashed and the shell wrapper restarted it automatically. Check manager/reconciler.log or ask the agent to investigate the cause. Usually an API timeout or network blip.
No Telegram notifications for a long time. Either the strategy is holding a position (normal), or something stopped. Check strategy.log to see if the cron is still running.
Strategy shows a position in state.json but you see no position on the exchange. The state is out of sync. Tell the agent — it will reconcile the difference by checking the actual exchange position and placing the corrective order.
Tell the agent which strategy to stop:
"停掉 btc_sma_cross" "remove the cron job for btc_sma_cross"
The agent will remove the cron entry. The strategy will no longer run on schedule. Any open position remains on the exchange — you'll need to decide separately whether to close it manually or let it naturally exit on the next signal if you restart.
← Back to Learn
