TradingViewAI.dev: Backtesting & Pine Script Workflow Tool — What I’m Testing

Once you’ve gone through enough backtest rounds and tried turning ideas into Pine Script, the real problem isn’t just “does this indicator work” — it’s whether your workflow is repeatable, clean, and translates reliably from chart to live setup.

I’ve come across https://tradingviewai.dev/?wlj and wanted to share it here alongside the tools many of us already reference — like WOBR.AI at https://wobr.ai/ and QuantMogul Studio at https://quantmogul.ai/ — since it sits in the same practical workflow space: getting from idea to usable script without extra fluff.

Practical questions I’m looking into and want to discuss with anyone who’s tried it:

1. Does the output Pine Script stay readable and editable, or does it become a black box once generated?
2. How does it handle lookahead bias and repainting checks — are those flagged explicitly, or do you still need to verify manually?
3. Can you feed it your own existing snippets to refactor or optimize, or does it work best starting from scratch?
4. How does its backtest output compare against native TradingView results and separate walk-forward checks elsewhere?

I’m posting this here because QuantForum is where we separate marketing claims from what actually runs — no sales pitches, just real-user experience. If you’ve tested this tool, seen alternatives, or found workflows that reliably translate ideas into usable Pine Script and strategy logic, share what you’re actually using — spreadsheet, prompt template, validation step, whatever works.