GUIDE · QUANT

Pine copilot

The copilot writes TradingView indicators and strategies in Pine v6 with you rather than at you. It asks what should fire before it writes a line, and what comes back is checked — it compiles, it reads the bar it says it reads, and it does not repaint. You paste it into TradingView and it works.

How a build goes

Describe the tool in a sentence. The copilot does not immediately produce 200 lines — it comes back with the decisions your description left open, as a short numbered list with a sensible default beside each one.

  1. Say what you want
    “A squeeze breakout on NVDA, confirmed on close.” One line is enough; the copilot will find the gaps.
  2. Answer the questions, or take the defaults
    What should it fire on? A close above the upper band, the first candle back inside, band width at a 20-bar low? Every question carries a default, and “Build with defaults” skips the lot.
  3. Read the script on the chart, not in your head
    The workbench runs the script on real bars beside the code, so plots and entries appear where they would appear in TradingView. CHART and CODE are the same object.
  4. Change it in words
    “Make the filter weekly”, “add an alert on the flip”. Each accepted change files a new version against the same script rather than starting over.

Blueprint

If you know you want something but not what, start a Blueprint. It is a three-step guided pass — instrument and horizon, the behaviour you are trying to catch, then what the tool should print — and it ends in a build-ready spec rather than a vague prompt. From there it is the ordinary build flow.

Building from a screenshot

Attach a chart image and the copilot reads what is actually visible: lines, bands, marks, tables, and where those marks print. It describes only what it can see and names the interpretation it picked where the mechanism is ambiguous, instead of inventing hidden logic.

A screenshot of one of our own indicators is a special case. The copilot will not reconstruct IQ Bands, the IQ Oscillator or IQ Structure — it specs a companion that reads their output through input.source and says so.

What it costs

One credit per question, two if you attach a screenshot. The allowance resets at midnight, and the count sits under the composer as you work. Builds that come straight from the concept library are free — those scripts are pre-checked, so no model runs.

What it will not do

It writes Pine v6 and nothing else, and it will not hand you the internals of the commercial indicators. Scripts are yours: they save to your account, keep every version, and follow you between devices. The copilot is a beta surface — it checks the code it gives you, but a script that trades your money deserves your own read of it before it does.