Skip to main content

Running Multiple Strategies

One signals process can evaluate several strategies, accounts, timeframes, market universes, and deployments declared in tradejs.config.ts.

How Setups Are Separated​

For each enabled strategy, TradeJS resolves:

  • strategy name, version, and complete configuration;
  • timeframe and market universe;
  • connector and trading account;
  • deployment-level symbols and any strategy-specific selection.tickers;
  • risk and policy settings.

Each unique combination is evaluated independently. A command-line filter can narrow the current run, and --tickers can temporarily replace its resolved symbol set.

If a removed symbol still has an open position, it remains active for exit and position-management decisions.

Decisions on the Same Symbol​

Every applicable strategy evaluates the same latest closed candle and records its own decision. Separate strategies may produce opposing signals. TradeJS does not assume that these signals form a portfolio decision: account-level risk rules and project hooks must define net exposure, position limits, hedging, and conflict handling.

Two enabled instances of the same strategy cannot target the same account in one process because their positions and decisions would be ambiguous. Use a different account or disable one instance.

Examples​

Evaluate every enabled setup once:

npx @tradejs/cli signals --user root

Run one deployment continuously:

npx @tradejs/cli signals-daemon \
  --user root \
  --deployment production \
  --notify \
  --makeOrders

Run a narrow diagnostic pass without placing orders:

npx @tradejs/cli signals \
  --user root \
  --universe crypto \
  --timeframe 15 \
  --account bybit-main \
  --tickers BTCUSDT,ETHUSDT \
  --cacheOnly

See How live signals work and Validate live decisions with replay.