Pine Script v6 compatibility subset.

Not a complete Pine implementation

The public engine supports a restricted Pine Script v6 strategy subset. It is not a complete implementation of every TradingView Pine language, visual, data-request, and broker-emulation feature.

Common single-position strategies using one symbol and one chart timeframe are the best fit. Unsupported behavior is rejected instead of being silently approximated.

Supported

Supported with constraints

• One simple qty_percent partial exit followed by a full exit of the remainder
• One absolute-quantity TP1 exit followed by one runner exit
• A single full-position trailing exit
• A simple strategy.oca.cancel long/short pending-order pair
• strategy.order() used like an entry only when the position is flat
• A very simple close_entries_rule = "ANY" structure
• Reissuing a full-position strategy.exit for the same entry ID
• strategy.cancel and strategy.cancel_all

Not supported

• request.security(), request.security_lower_tf(), multi-timeframe data, and other-symbol requests
• Live-tick behavior, unfinished-bar state, Bar Magnifier, and lower-timeframe fill reconstruction
• Pyramiding, DCA, scale-in, and repeated position increases
• Multiple entry IDs in the same direction
• Multiple partial exits, OCA Reduce, or partial-exit and trailing combinations
• Complex ANY exits, reversal lifecycles, and broker-state combinations
• strategy.order() used for manual reduce or scale-in behavior
• Partial strategy.close behavior

Restricted language and visual surfaces

Compatibility is broader than order logic. Depending on the script, the public subset may reject user-defined types, enums, imports, exports, methods, maps, matrices, complex object arrays, advanced array mutation or search, and some dynamic-length ta.* calls.

Chart-only objects and handle-based behavior can also be outside the subset, including labels, lines, boxes, tables, polylines, stored plot or hline handles, and handle-based fill().

How compatibility is checked

The GPT inspects known compatibility surfaces before submission. The execution engine then performs the authoritative compile, runtime, strategy-setting, and broker-state checks. Unsupported behavior is rejected with the smallest relevant correction instead of being silently approximated.