feature

FAQ

Short answers to the questions people ask most about scripting — whether you need code at all, indicator vs definition, emits, pins, and budgets vs credits.

Do I need to write code?

No. Visual builders, Conductor, and manual editors cover most workflows. Use Scripting when you want precise control, review agent diffs, or debug runtime errors.

Indicator vs definition — which do I want?

Indicator — paint series on the chart.
Definition — mark setups in history for Collect / study (kind: "flow").

See Choose your DSL.

Can Conductor write pins?

Conductor can start Put on chart, which routes to the pin orchestrator. The study authoring agent should not write pin_cell. See Pin orchestrator.

Why was my emit dropped?

Usually a missing label, unknown event id, or oncePer suppression. See Emit and labels and Emit not collected.

Why is my study empty?

Definition not Collected for that instrument / range
ctx.event.flow compared to slug instead of as alias
Filters too strict in onEvent
Upstream emits dropped (labels)

Are budgets the same as AI credits?

No. Budgets are runtime safety for scripts. AI credits bill model usage. Broker Capacity is account connectivity.

Can I use npm packages in scripts?

No. Relative ESM modules inside the package only (definitions). Indicators / studies follow their single- or multi-file rules in the Code tab — no bare package imports.

← Previous Next →