Making indicators

Ask Quant, our coding agent, for the study you want. It writes a Pine Script® indicator, plots it on the active chart in Vela, our next-generation charting platform, and marks it in the legend so you can tell it apart from Library and built-in studies. Every script is real code you can open in the Pine editor, and Pine Script® runs on LuxAlgo through PineTS, our open-source runtime.

Quant can also add scripts from the LuxAlgo Library when you ask for them in chat. To browse Library studies or add built-in and order-flow indicators yourself, use the Indicators picker. For a markup of the chart as it is now rather than a script, see Draw or write a script?

How a script lands on the chart

1. The chart comes first. If your request names a market or timeframe, Quant sets the chart up before it writes, so the script runs on the data you meant.
2. The code is checked. Quant validates the script before anything changes. If it doesn't compile, the chart stays as it was and Quant fixes the errors.
3. It runs on the active chart. New scripts go on the active chart, marked in the legend.
4. Quant sees how it ran. After writing or editing, Quant gets any runtime error and, for a strategy, a one-line backtest summary: net P&L, profit factor, trades, and max drawdown. It fixes runtime errors in code it wrote. When an error comes from data the market doesn't have, such as Orderflow on forex, Quant says so instead of rewriting the script.

Several scripts in one chat

One chat can create, edit, and remove several indicators and strategies. Starting another script doesn't need a new chat.

• "The script" means the chat's latest. When you ask to change "the script" or "my indicator" without naming one, Quant changes the latest script this chat created. Name a script to work on another one.
• Something new is a new script. Ask for something in addition to what's on the chart and Quant creates a separate script.
• Quant can edit scripts it didn't write: your own scripts and free Library indicators. It reads the current code first, so its edit matches what's on the chart. Customizing a Library indicator saves the result as your own script.
• Removing is on request. Quant takes a script off the chart only when you ask. A saved script stays in My Scripts; built-in and Library indicators come off with their settings.

Keep it on the workspace

Scripts Quant creates are saved to your account and stay on the chart until removed. There is no separate Add to workspace or commit step to keep them there.

Find them in Indicators, under My Scripts. It lists the scripts Quant wrote and the ones you saved from the Pine editor, newest first. Filter by All scripts, Quant scripts, or User scripts, sort by Newest first, A–Z, or Favorites first, and use Open code on a row to load its source in the Pine editor. A script Quant wrote also has Open chat, which returns to the chat that wrote it.

To keep code you write or paste yourself, use the editor's Save control or Ctrl+S / ⌘S; see Pine editor.

Add to chart

Add to chart adds the latest script created during the chat session to the active chart. It does not select the latest script merely because you edited it.

For example, if you create an RSI indicator, then create a moving average, then edit the RSI, Add to chart selects the moving average. To choose a specific Quant-created script, use My Scripts in the Indicators picker.

When you reopen a chat whose script isn't on the current chart, the chat offers Add to chart.

Starring a Quant script is separate: Favorites follow your account, so you can find starred scripts in the picker on any workspace.

LuxAlgo Library indicators

Ask Quant to add a Library indicator ("add LuxAlgo's fair value gap indicator") and it finds it in the Library and adds it beside your scripts, as published, without rewriting it.

• Free indicators are available on every plan. Paid Library indicators need a plan that includes them; see Plans.
• A paid Library indicator's source code is protected. Quant can add it, change its inputs, and remove it, but it can't read or edit its code.
• If a Library indicator fails on Vela, Quant doesn't edit it. It tells you what failed and offers an alternative.

From a screenshot

Quant can reverse-engineer an indicator or chart markup from an image.

Ways to hand it one:

• Upload or paste into the chat, or Attach files from the +
• From a screenshot under the prompt on an empty chat, then pick the image
• Attach chart screenshot from the + — choose Entire layout or Active chart when several charts are visible

To save an image for a post, presentation, or review, use Screenshots from the right-hand rail. That export workflow is separate from attaching an image to a Quant message.

Images also work as a target: instead of describing the visual result you want, show it. "Make it look like this" with a screenshot is often more precise than a paragraph of styling instructions.

From a region on the chart

When you only care about part of the chart — a pattern, a label, a stretch of candles — use Capture area for Quant on the left drawing toolbar, above Measure.

1. Click the tool. The chart dims.
2. Drag a rectangle around what you want Quant to see. Resize from the handles, or drag the box to move it.
3. Type (or speak) in the prompt on the selection, then send. Quant gets the crop plus your message.

This is not a drawing: it does not save with the workspace and it does not sit in the Object tree. Exit capture, Escape, right-click the chart, or a click outside the box leaves the tool.

Use it to ask about markup already on the chart ("what is this ABCD"), or to point at the thing you want changed ("add a bgcolor to the ratio labels").

Writing good prompts

• Start simple. "An RSI oscillator with signals" is a better opening than a full specification. Get a working base, then refine.
• Say what done looks like. Below the chart or overlaid on price, colors, line styles, and how it should behave in a specific case (e.g. "when price gaps, the band should not reset").
• Build in small steps instead of asking for a full toolkit at once. Each request should add or change one thing.
• For something large, ask for a plan first. Have Quant propose the structure, agree on it, then implement step by step.
• After the first output, request one change per message. Batched change lists tend to get partially applied. Name the script you want to change when a chat contains several.

When something breaks

Two kinds of errors can occur:

• Syntax errors: the script fails to compile and nothing plots.
• Runtime errors: the script compiles, but fails while running over history or on new bars. These appear as a message at the bottom of the chart.

Quant code repair is included with Premium, Ultimate, and AI Ultra. See Plans for feature access.

For either, Fix with Quant feeds the error back to Quant and asks it to repair the script. If a script runs but doesn't visibly plot, inspect Pine editor: the plot calls may be conditioned on something that never happens on this symbol or timeframe.

What runs on Vela

Quant writes Pine Script® v6. Most of the language runs through PineTS, with some exceptions:

• library() scripts and import statements can't run on a chart, so Quant writes helper functions inline.
• A few request.* data calls aren't supported, and some behaviors differ from other platforms. A script that compiles can still fail on the chart, which is why Quant checks how each script ran.

See the PineTS docs for what the runtime covers.