Pineify TradingView Extension: Grid Search and Recording

Pineify's TradingView extension offers two ways to retain strategy comparisons: an automated parameter grid and recording of manually chosen settings. Both collect information from TradingView's Strategy Tester. Neither supplies an independent execution model or proves that a strategy will work in live trading.

Choose the mode that matches the question

Workflow	Useful when	What it does not establish
Grid search	You have a predefined set of parameter combinations to compare	Whether untested values or future periods will perform similarly
Automatic recording	You are changing settings manually and want report snapshots	That every click or intermediate state was captured
Manual capture	You want to deliberately record selected completed tests	Exhaustive coverage of the parameter space

The recording implementation offers automatic observation and a manual capture button. Recording cannot start while optimization is active. Treat these as separate sessions and label their exports accordingly.

What a recorded snapshot contains

A captured row includes the current interval, collected strategy inputs, a recording timestamp, and available report metrics such as net profit, trade count, win rate, profit factor, maximum drawdown, and average trade. The timestamp is the capture time, not a trade execution time.

Automatic mode observes changes to the tester report and waits for a short quiet period before capturing. Repeated snapshots with the same interval, inputs, and selected metrics are deduplicated. As a result, the snapshot count is not necessarily the number of edits you made.

Wait for a visible completed report, capture it, and confirm that the resulting row contains the settings you intended. If the count does not increase, check whether the result is unchanged, the tester report is available, and recording is active. A captured summary does not include every historical trade or the full equity series.

When a grid is more suitable

A grid makes coverage explicit. Three parameters with five values each produce 125 combinations. Adding five chart intervals produces 625 tests. These are hypothetical workload counts; they do not imply a particular runtime.

The optimizer changes supported inputs and waits for TradingView calculations sequentially. Check the completed status and row count because interruptions and calculation failures can leave a partial dataset. Before a larger run, reproduce a small test manually to verify the selected controls and collected metrics.

For search design and combination arithmetic, see the parameter-grid workflow. Use a separate evaluation period after selecting parameters; the extension does not automatically perform walk-forward validation.

Export without losing context

The results page exports available rows to CSV. Grid exports can include a Parameters section with fixed or optimized settings before the Results table. Locate the actual table header when importing into Python, R, or a spreadsheet.

Save a companion record containing the script version, symbol and exchange, chart type, period, capital, position sizing, commission, slippage, and execution settings. A CSV of summary metrics alone cannot reproduce an experiment if those conditions are unknown.

Recording results are stored in the extension's local browser storage and opened through an extension result URL. That URL is not evidence of a public share link or cross-device backup. Export a copy before clearing extension data or removing the extension.

Installation, access, and data boundaries

Use the installation link on the Strategy Optimizer page. Installing the extension does not by itself grant every paid feature. Sign in and verify current plan entitlement; the documented optimizer access is Advanced or higher.

The click automation and local result storage do not make the entire workflow offline. TradingView performs its online platform functions, and the extension includes Pineify authentication requests and usage telemetry. Optional AI tools have separate data flows. Avoid assuming that a local extension means all associated content remains exclusively on the device.

The resulting metrics retain TradingView's data and broker-emulator limitations. Review its strategy documentation when comparing chart types, costs, and order timing. The extension does not place broker orders as part of the parameter-search workflow.

▶Does automatic recording save every input change?

It observes report changes, waits briefly, and deduplicates matching snapshots. Check the saved rows; the capture count can differ from the number of edits.

▶Is a recorded timestamp a trade timestamp?

No. It records when the report snapshot was captured. Trade-level history must be obtained separately.

▶Is the results URL a cloud backup?

The recording workflow uses local extension storage and an extension result URL. Export files for a separate durable copy.

▶How long does a grid take?

Runtime depends on the combination count, script, available data, browser state, and calculation response. No fixed minutes-per-grid benchmark is established here.