Back to articles

No-Code Quant Research: Evolving from Rule-Based Scripting to Agentic Pattern Backtesting

Serg
Serg
August 4, 2026
2 views

No-Code Quant Research: Evolving from Rule-Based Scripting to Agentic Pattern Backtesting

Verdict: robust · Asset/TF: BTC/SOL Multi-Asset · Sample: 60,000 bars (2019-2026)

The Traditional Paradigm: The Coding Bottleneck

Historically, building a quantitative trading system required a trader to:

  1. Formulate a conceptual idea (e.g., "RSI consolidates high on heavy volume before a breakout").
  2. Write lines of code (Python, PineScript, C#) mapping strict logical rules: close > BB_Upper && RSI_14 > 60 && volume > mean(volume) * 2.
  3. Debug indicator code, handle time-alignment, and manage data frames.

This coding bottleneck limits exploration speed. If it takes 2 hours to write, test, and debug a single strategy script, a researcher can only explore a handful of ideas per day.


The New Paradigm: Agentic Pattern Extraction

With the integration of LLM agents and the RLXBT Pattern Lab, we are entering the era of No-Code Agentic Backtesting. Instead of writing rules, the trader directs the agent to extract and test market states directly.

The workflow is completely code-free:

[Identify State] ➔ [Agent Extracts Shapes] ➔ [Engine Materializes Feature] ➔ [Instant OOS Validation]

1. Identify Market States

The trader identifies an interesting event on the chart (e.g., a capitulation bottom) or lets the agent run unsupervised clustering (analyze_event_patterns) across indicators like Entropy, Volume, or Kalman deviations.

2. Extract Shape Profiles

The agent extracts the multi-bar, multi-channel geometry as Z-normalized float arrays. For example, a 5-bar bottom sequence becomes a clean mathematical profile:

  • close: [1.0, 0.8, 0.4, 0.5, 0.9]
  • volume: [1000, 1100, 3500, 1800, 2500]

3. Materialize Similarity Features

The RLXBT engine takes this extracted profile and materializes it as a new continuous feature column. It calculates the rolling Pearson correlation or Euclidean distance between the live chart and the target profile.

4. Direct Backtesting

Without writing a single entry or exit rule, the engine runs a backtest of this similarity feature. It sweeps entry thresholds (e.g., "buy when similarity >= 85%"), manages position sizing, and pipes the results directly into Walk-Forward Analysis and Monte Carlo simulations.


Case Study: From Visual Panic to Out-of-Sample Verdict

During our recent research session, we directed the agent to find a capitulation bottom in BTCUSDT 1h:

  • Extraction: The agent isolated the panic event of February 24, 2023 (Z-score -4.19, 35.9k volume).
  • Testing: We ran an instant OOS backtest. The strategy generated 25 trades over 3.4 years.
  • The Verdict: While profitable (+2.45% return, Sharpe 0.19), the engine rejected it because it failed to beat the passive bull baseline (+179.35%).

In a traditional setup, writing, debugging, and benchmarking this custom pattern would have taken hours. Here, the agent completed the entire lifecycle (extraction ➔ search ➔ backtest ➔ WFA ➔ baseline benchmark ➔ rejection) in under 90 seconds.


Why this is a Game-Changer for Traders

  1. Exponential Exploration Speed: A trader can test 100 visual patterns, sketches, or indicator states in a single afternoon.
  2. Focus on Alpha Generation: Time is spent observing market behavior and generating hypotheses rather than debugging pandas dataframes.
  3. Strict Causal Boundaries: The agent automatically sets the available_from_timestamp to the end of the extracted pattern, ensuring that out-of-sample tests have zero retrospective leakage.

Reproduce

Run the pattern extraction script to test your own 5-candle shapes:

Reproducible research result

Backtest evidence

BTCUSDT1h60,000 bars
Research verdict
robust
+2.45%
Total return
0.19
Sharpe
6.19%
Max drawdown
25
Trades
52.00%
Win rate

Robustness

Walk-Forward efficiency0
Monte-Carlo risk of ruin0
Sensitivity leadersimilarity_threshold
Report: rpt_1785825557474_189
MCP trail: load_dataset → search_candlestick_patterns → run_pattern_experiment → execute_ui_action

Comments (0)

No comments yet. Be the first to share your thoughts!