Documentation
This documentation covers usage: how to submit scripts, how to configure execution, how to read status, and how to deploy the output in TradingView.
Quick Start
- Go to Generate Strategy
- Paste your Pine Script v6 (full script)
- Configure execution and risk settings
- Click Generate
- Copy the delivered strategy into TradingView
Submitting a Script
Paste the entire Pine Script file into the input field.
- Use Pine Script v6
- Submit the full script, not fragments
- Remove anything unrelated to the script (notes, URLs, extra text)
Configuration Overview
Pine Engine converts your signals into a structured execution framework based on your configuration.
Your configuration is grouped into:
When to Trade
- Date range
- Session window (optional)
- Direction control (long / short / both)
- Cooldown and discipline toggles
Capital Guardrails
- Daily profit target (optional)
- Max daily loss (optional)
- Max strategy drawdown (optional)
- Drawdown percent limits (if enabled)
Trade Risk and Exits
- Risk model (currency or percent)
- Stop loss
- Break-even trigger (optional)
- Take-profit settings
- Trailing stop settings (if enabled)
Status Pipeline
During generation you will see a live status sequence:
VALIDATING
CLEANING
COMPILING
REVIEWING
DELIVERED
FAILED
If a run fails, you will see the failure status and a classified error type.
Output: Using the Generated Strategy in TradingView
- Open TradingView Pine Editor
- Paste the delivered strategy
- Save
- Add to chart
- Configure inputs if needed
- Backtest or create alerts based on your workflow
Common Errors
If a run fails, you will see a classified error type.
Typical examples:
Signal interpretation issue — we couldn’t read a clear trading signal from your script
Signal processing issue — the system had trouble processing your signal for execution
Strategy assembly issue — we had trouble assembling your execution strategy
Automated review issue — the automated review step flagged a problem
Delivery issue — delivering the final script failed
Reporting a Bug
If something looks wrong with the output:
- Use the Report Bug page
- Include your submission ID
- Describe what you expected vs what happened
- Include symbol and timeframe if relevant
This is the fastest path to a reproducible fix.
