Skip to main content
Vulcan’s strategy command group hosts long-running execution loops that are too stateful for one-shot orders. Each run is ledger-backed, supports pause / resume / finalize lifecycle commands, and can be started in detached mode so the runner keeps ticking in the background. Tick logs and ledgers are persisted under ~/.vulcan/strategy-runs. Three runners ship today:
  • TWAP — split a target size across timed slices.
  • Grid — maintain layered limit orders across a price band.
  • TA — rule-based runner over technical indicators for entry and exit.

Execution modes

Every strategy accepts --mode. Pick the one that matches your tolerance for live risk while testing:

Margin mode

For TWAP and grid runs, --margin-mode selects how collateral is held:

Guardrails

All three runners accept the same safety flags. Any breach pauses the run and records the reason in the ledger:

TWAP

TWAP slices a target size across N equally spaced intervals so each fill nudges the average price toward the time-weighted mean.

vulcan strategy twap start

Plus the guardrail flags above.

vulcan strategy twap resume

Resume a paused or incomplete TWAP run, optionally starting at a specific step.

Example

Grid

Grid trading lays buy levels below the mark and sell levels above the mark, then maintains the ladder as fills happen. The runner can either be bounded by --ticks or run indefinitely with --run-until-stopped.

vulcan strategy grid start

Plus the guardrail flags above.

vulcan strategy grid resume

Resume a paused or incomplete grid run.

Example

TA

The TA runner evaluates rules of the form (condition, action) over indicator values on a chosen timeframe. Conditions reference indicators like rsi, macd, ema, etc.; actions place or close positions when triggered. Configs are JSON, supplied inline or via a file. TA margin settings are part of that JSON config (margin_mode and isolated_collateral), not separate CLI flags.

vulcan strategy ta start

Plus the guardrail flags above.

vulcan strategy ta resume

Resume a paused or incomplete TA strategy run.

Example

For ad-hoc indicator queries outside the strategy framework, use the top-level vulcan ta commands.

Lifecycle commands

These apply to any strategy run, regardless of type. Most take the <run-id> returned by start (runs and preflight do not). List recent run IDs with vulcan strategy runs.

Typical operating loop