Skip to content
chartgen

Trading

--trade starts a live engine: a Binance WebSocket kline feed, a rolling 200-bar indicator state manager, an order tracker, and an alert engine — and serves them over the same HTTP + OAuth stack as --serve, exposing 12 extra MCP tools on top of the 3 charting tools.

Terminal window
chartgen --trade --testnet \
  --symbol BTCUSDT --interval 1h \
  --port 9315 -p cipher_b -p rsi_mfi_stoch

--trade and --serve are mutually exclusive — mode dispatch in src/main.rs picks the first match and returns. Don’t combine them; --trade alone does everything --serve does plus the trading engine.

What the engine runs

Section titled “What the engine runs”
  • WebSocket feed (src/feed.rs) — streams 1-minute klines for the configured symbol and reconnects on drop, backfilling via REST.
  • Bar aggregator (src/feed.rs) — derives 5m, 15m, 1h, and 4h bars from the 1-minute stream so alerts can fire on higher timeframes without a second subscription. src/mtf.rs provides the generic multi-timeframe primitives (1m → 5m/15m/30m/1h/4h/1d/1wk) the aggregator is built on.
  • Indicator state (src/indicator_state.rs) — keeps a rolling 200-bar window per (symbol, interval) and recomputes indicators on every closed bar.
  • Alert engine (src/trading/alert.rs) — evaluates registered alerts against each new bar + indicator result.
  • Order tracker (src/trading/order.rs, position.rs) — local state machine (Pending → Open → Filled/Cancelled/Rejected) and unrealized-PnL tracking.
  • Audit log (src/trading/persistence.rs) — append-only trades.log.

All state lives under ~/.chartgen/. See the persistence reference for on-disk formats.

Orders

Section titled “Orders”

Place a market order:

{
  "name": "place_order",
  "arguments": {
    "symbol": "BTCUSDT",
    "side": "buy",
    "type": "market",
    "quantity": 0.01
  }
}

Limit orders require a price. cancel_order takes the order_id returned by place_order. get_orders lists tracked orders (filter open or all); get_positions reports open positions with unrealized PnL; get_balance returns exchange balances (requires credentials).

Every order state transition is appended to ~/.chartgen/trades.log:

2026-04-19T12:34:56Z SUBMITTED buy BTCUSDT 0.01 market id=abc123
2026-04-19T12:34:57Z FILLED   buy BTCUSDT 0.01 @ 67432.5 id=abc123

Alerts

Section titled “Alerts”

Alerts are one-shot: the first matching bar triggers the alert, enqueues a notification, and removes the alert from the active list. The persistent state in ~/.chartgen/alerts.json is rewritten atomically only when an alert fires or is added/removed — idle bars cost zero writes.

Three condition types:

{ "price_above": 50000 }
{ "price_below": 45000 }
{ "indicator_signal": { "indicator": "cipher_b", "signal": "gold_buy" } }

Signal labels

Section titled “Signal labels”

indicator_signal alerts match against a fixed label registry in src/trading/signals.rs. Using anything else will never match. Current labels:

GroupLabels
Sharedbuy, sell, rsi_oversold, rsi_overbought
Cipher Bbuy_small, sell_small, wt_bull_div, wt_bear_div, rsi_bull_div, rsi_bear_div, stoch_bull_div, stoch_bear_div, any_bull_div, any_bear_div, gold_buy
RSI/MFI/Stoch combostoch_oversold, stoch_overbought
WaveTrendcross_up_os, cross_down_ob, cross_up, cross_down
Custom (Supertrend / Chandelier / Heikin-Ashi / momentum)flip_up, flip_down, buy_oversold, sell_overbought

Consuming alerts

Section titled “Consuming alerts”

Two styles, pick one:

  • Poll with get_notifications — drains the triggered-alert queue on each call.
  • Push via subscribe_notifications over the SSE stream. Subscriptions persist and have an offline queue (default TTL 1 h).

Triggered alerts are also logged to trades.log as ALERT_TRIGGERED lines.