Supported features
Check native Pine capabilities without assuming full language or strategy-tester parity.
The native runtime supports practical Pine calculation, plotting, and strategy-intent workflows. Support is incremental; verify a script through the native runtime rather than assuming that a version declaration establishes complete compatibility.
Verified building blocks
The runtime's fixtures cover history references such as close[1], persistent var state, common technical calculations, conditional signals, and indicator/strategy declarations. The getting-started example uses EMA, crossover/crossunder, integer inputs, confirmation, and named plots.
Plot support includes practical paths for plot, plotshape, plotarrow, plotbar, plotcandle, fill, barcolor, and bgcolor, along with supported drawing cleanup and options such as hidden display, offsets, and limited visible history. Cosmetic behavior is not guaranteed to match every TradingView rendering detail.
Explicit unsupported features
| Feature | Current behavior |
|---|---|
request.security() | Unsupported cross-symbol or multi-timeframe request |
request.security_lower_tf() | Unsupported lower-timeframe request |
Pine import | Unsupported library import |
ticker.new() / ticker.modify() routing | Unsupported cross-symbol ticker routing |
| Full TradingView strategy tester metrics | Not provided by the native intent bridge |
STX owns data routing and the selected bar stream. Do not work around an unsupported request by assuming that changing a Pine symbol string creates a new engine subscription.
Partial compatibility still needs testing
Broader Pine v6 parity, input override UI, full strategy-tester behavior, and exact partial/limit/stop strategy semantics are not established by the current integration.
The native unsupported-feature detector reports known unsupported constructs, but passing that check is not proof that every other script feature is implemented. Read compile/runtime diagnostics and validate the resulting plots and intents.
Port incrementally
Start with the core calculation and one plot. Add the input declarations, state, signals, and execution intents separately. Keep a small source revision that reproduces any compatibility problem.
Continue with inputs and configuration.