Skip to content
TradingTune
Comparison

Kioseff alternative: how TradingTune compares

TradingTune automates TradingView strategy optimization for strategies you already have.

On this page

Key takeaways

  • TradingTune is a Chrome and Brave extension that automates TradingView strategy optimization for strategies you already have.
  • A search method determines which parameter combinations a run tests during optimization.
  • A result from historical data needs context before it can be interpreted.
  • TradingTune gives each numeric input its own range and an enabled setting.

Starting with your own strategy

TradingTune is a Chrome and Brave extension that automates TradingView strategy optimization for strategies you already have. A backtest applies a strategy’s rules to historical data to examine how they behaved. Optimization tests settings for those rules, so the starting point is an existing strategy and the inputs available in its settings.

The other tool’s official page, checked on 2026-11-14, says: “You need to follow the AI’s guidance through an iterative process to discover the optimal settings for your strategy.” TradingTune is better suited to a hands-off run, because TradingTune automates TradingView strategy optimization.

Open your strategy settings. Set minimum, maximum and step ranges. Start the optimization, then read the live results. Numeric inputs are values you can change in the strategy settings. The strategy itself supplies the rules being tested, while the ranges describe the values the search may try.

A useful first question is which parts of the strategy those inputs control. An entry condition describes when a strategy enters a position during a test. An exit condition describes when it leaves. Inputs can affect either kind of rule, so a test is easier to interpret when you know what each enabled input changes.

Keep a note of the strategy version and the chart used for a run. That context makes the results easier to revisit if the script or its settings change later. The getting started guide covers the site’s basic workflow for a trader setting up a run.

Setting the search ranges

A parameter is an input whose value can change within the strategy settings. A range gives that input a minimum, a maximum and a step. The step is the interval between values available to the search. TradingTune stores each numeric input as minimum, maximum, step and enabled.

The bounds matter because a search cannot examine values outside the range it receives. A narrow range asks a focused question about a small part of the available values. A wide range asks a broader question, but leaves more possible combinations for the search to consider. Neither choice establishes that a setting will work on data outside the test.

A profit target is an exit level set for a favorable price move. A stop loss is an exit level set to limit exposure to an adverse move. TradingTune gives each numeric input in the strategy settings its own range, so these exit levels are not the only values a search can vary.

Because each input also has an enabled setting, you decide which inputs the search varies in a run.

Record the range and step along with the result for each run you review. A result without those details does not show which neighboring values were available for testing. The guide to choosing parameter ranges explains the setup in more detail.

TradingTune for Chrome

Stop tuning your strategy's inputs by hand.

Add to Chrome, it's free

Free tier, no API keys. A free account is required to run. Not affiliated with TradingView, Inc.

Choosing a search method

A search method is the rule a tool uses to choose which parameter combinations to test. TradingTune offers seven optimization methods. Each uses the same setup: give each numeric input a range, pick a target metric and run.

The methods ask the search to explore the available combinations in different ways. A grid search tries every combination of the values in the ranges. Random search draws independent parameter sets. A Bayesian sampler builds a model from previous trials and uses it to choose later trials. These descriptions concern the search process, not a promise about a strategy’s outcome.

An optimization cycle is a trial in which a parameter combination is tested. The cycle budget is the amount of testing available for a run.

TradingTune picks one of these for you automatically the first time it sees a strategy. You can override it any time. The methods page lists the search methods used to tune TradingView strategies. The guide to choosing a method provides context for matching a search to the size of the ranges and the cycle budget.

The choice is part of the record of a test and helps explain its scope. When revisiting a run, the method helps explain how the tested combinations were selected. The ranges alone do not show that sequence, and the top row alone does not describe the search.

Picking what a run measures

A metric is a measurement used to describe a backtest and its results. A target metric is the measurement an optimization run uses to rank settings. Every TradingTune method shares the same setup: give each numeric input a range, pick a target metric, then run.

The target frames the question asked of the data during the search. A search focused on one measurement can put a setting at the top without explaining every aspect of the test. Other measurements may describe different parts of the same history, so a rank is a starting point for reading the result, not a complete description of it.

A target metric also needs the context of the data used to calculate it. The market, chart timeframe and test period define the history being examined. If those change, a reader is looking at a different test, even when the input values remain the same.

The guide to reading backtest metrics explains what common measurements do and do not show. It is useful when a table presents several measurements and the target alone does not answer the question being asked.

Reading the live results

TradingTune shows live metrics for each tested parameter combination. The results are sorted, filtered, and ranked automatically. Live results let a reader inspect the table as the search progresses, without waiting for the run to finish.

A row represents a tested combination, not a separate strategy in isolation. Its meaning depends on the rules, the enabled inputs and the test conditions. Reading across a row connects the values selected by the search with the measurements produced under those conditions.

The top-ranked row answers a narrow question: which tested combination ranked highest on the chosen target at that point in the run. It does not show what would have happened for every possible value outside the search. It also does not establish how the same settings will behave on new data.

Nearby settings can help put a row in the context of the search. Parameter sensitivity means how much a result changes when an input changes. A cluster of similar readings and an isolated peak tell different stories about the area explored by the search. The parameter sensitivity guide discusses that distinction.

TradingTune sends the best settings back to your strategy. The applied values are still the result of a historical test. Keeping the run’s ranges and target alongside those values preserves the question that produced them.

Separating fitting data from a later test

Fitting is the process of using data to select settings. In-sample data is the history used for that selection during the search. Out-of-sample data is held aside for a later test of the selected settings. The distinction matters because the search has already used the fitting period to choose among combinations.

A high rank on the fitting period describes that period and that search. It does not by itself establish that the chosen values capture a pattern that persists. The held-out period asks a separate question: how the selected settings behave on history that did not guide their selection.

The boundary between the periods is part of the test record. So are changes to the strategy, ranges or target after looking at the held-out data. Once those observations inform a new selection, the same period no longer has the same role as untouched data for that selection.

This distinction also helps explain overfitting. Overfitting is a close fit to features of the test history that may not persist in other data. Searching many settings can make it easy to focus on a result that reflects the particular period examined. A held-out test offers another view, but it cannot remove uncertainty.

The in-sample and out-of-sample guide explains the split between selection and later testing. The overfitting guide covers why a compelling historical fit calls for careful interpretation.

Keeping test conditions in view

A backtest depends on the conditions used to model trades as well as the strategy rules. Commission is a charge associated with a trade and is part of trading costs. Slippage is the difference between an expected price and the price used for a fill. These assumptions affect how a historical test represents a trading process.

The assumptions belong beside the parameter values in any record of a run. A change to a cost assumption changes the question being tested, even if the chart and strategy remain the same. Without that context, a reader cannot tell whether a change in the result came from settings or from the test conditions.

The chart timeframe is another part of the context for interpreting a test. It is the interval represented by each bar on the chart. Rules applied to one interval examine data at that resolution, so the same input values need not describe the same behavior on a different interval.

The selected date range also determines which historical conditions appear in the test. A result describes the data included in that range, not every market condition that could occur. Recording the start and end of the period helps make a later review understandable.

For more on these choices, see the guides to slippage and commission, timeframe-specific optimization and choosing a backtest date range.

Saving and revisiting a run

TradingTune can export and import runs in ZIP and CSV. A ZIP is an archive that groups files for storage or transfer. A CSV is a text format for tabular data, with values arranged in rows. Each TradingTune run exports a ZIP of metadata.csv, params.csv, settings.csv and results.csv.

An export can preserve the record of a particular search. The parameter file and settings provide context for the result rows, while metadata helps identify the run. The files are useful together because a result value alone does not describe the inputs and conditions that produced it.

A separate note can capture the reason for the test. For example, it can identify the strategy version, the target metric and the question the chosen ranges were meant to explore. If a later run changes those choices, the note makes that change visible during review.

TradingTune can retest the same settings across assets. An asset is the instrument represented by a chart used for the test. Retesting keeps the selected values in view while examining another set of historical data. It is a separate check, not proof that a setting will hold across markets.

The multi-asset retesting guide explains the idea. The strategy versioning article covers why changes to a script belong in the test record.

Browser, account and access

TradingTune is a free Chrome and Brave extension that automates TradingView strategy optimization. Optimization runs in the browser, and no TradingView API keys are needed. An API key is a credential used to access a software interface. A free TradingTune account is required.

Your strategies and results stay in your browser. Your cycle count and review request dates sync to your account. That distinction separates the test material kept locally from the account data used for the free allowance and for spacing review requests.

Pro has unlimited optimization cycles per day. The plans in the pricing section of the home page list the available access options and their terms.

The browser setting is relevant when reviewing how a workflow is organized. The chart, strategy settings and result table provide the context for the search, while the account handles access to optimization. Keeping a record of the test still matters: local storage and an export answer different questions about where information is kept and how a run can be revisited.

For the method descriptions and shared setup, see TradingTune methods. For the broader choice of tools, the alternatives hub is the site’s starting point.

Sources

Quoted from Kioseff

Checked on

You need to follow the AI's guidance through an iterative process to discover the optimal settings for your strategy.

Source: tradingview.com

TradingTune for Chrome

Stop tuning your strategy's inputs by hand.

TradingTune runs systematic parameter searches on your own TradingView strategy, right inside the chart page. You keep the strategy, you read the results.

Free tier, no API keys. A free account is required to run. Not affiliated with TradingView, Inc.

Share this post