Charts can be laid out in a grid, and you decide where each one opens.

A region used to show a single chart, and a new one always opened in the top-left region — no matter where you were looking at that moment. Now each region has its own mode: the familiar tabs, or a grid where every chart in the region is visible at once. And panels, algorithms and regions carry a color or a letter tag — a chart goes to whichever one the tag matches.

Watchdog no longer answers "Active" about a dead core.

Profile status only updated when you pressed the button, so you learned about a problem indirectly — for example, from notifications that stopped arriving. Now the check runs on its own, the button shows a countdown, and you set the trigger delay after a core failure yourself instead of the hardcoded sixty seconds.

Second Stop Loss is calculated correctly.

We closed two critical calculation defects: the second stop took an incorrect base after a manual SL modification, and on Bybit it drifted to almost 5% instead of the configured 0.6%. And we added the "Ignore Initial SL Delay" option — previously, while the initial stop's timer was running, the price had time to reverse and the position closed at a loss instead of locking in profit.

Workspace

Grid Mode.

Each region now has its own display mode: Tabbed — one active chart with tab navigation, as before — or Grid, where every chart in the region is shown at once in a configurable grid.

Link Layout.

Panels, algorithms, regions and tabs are assigned a tag — a color or a letter from A to F. When a panel or an algorithm opens a chart, it lands in the region with the matching tag.

Charts set their own scale.

When a candle or mixed chart opens, roughly sixty candles are on screen — on any interval.

Monitoring

Automatic status check.

Watchdog checks profiles on its own, and the check button shows a countdown to the next cycle.

Your own trigger delay.

With periodic checks disabled, Watchdog waited up to sixty seconds after a core failure — that was hardcoded. Now you set the time.

Profiles are easier to manage.

They can be renamed right in the client and created in bulk from a local CSV — name, IP, port, token. This matters when you run dozens of cores.

You can see what you are managing.

The Watchdog version now appears on the client's main screen, next to the Watchdog toggle.

Restart from settings.

A restart button has been added to the Watchdog settings.

Also fixed: uncontrolled thread creation on API errors led to memory exhaustion and service instability; with Watchdog running, leverage change notifications were sent to Telegram despite being disabled in settings; after an OKX core crash Watchdog failed to cancel orders and the terminal fell out of sync with the exchange — the client showed no active orders while the balance stayed frozen.

Position protection

Second SL can ignore the initial stop's delay.

The initial SL has its own execution delay — a noise filter. While that timer runs, the second stop cannot be placed even when its conditions are already met. A new checkbox lets it fire immediately.

Auto Price Down can be disabled when the second stop triggers.

Auto Price Down pulls the take profit toward the market, and once the second stop has fired this produced underfills.

Second stop calculation fixed.

It took an incorrect base after a manual stop-loss modification before the second trigger activated, and on Bybit it did not follow trigger, distance and trailing logic: with 0.6% configured, the stop drifted to nearly 5%.

Depth TP is calculated the way it is drawn.

In Depth Shots the calculation ran from the current price, while the interface and the documentation describe a calculation from the shot's origin. In some cases the TP was placed at market. It is now calculated from the shot's origin to the entry point, exactly as the interface shows.

Also fixed: an unprocessed Binance timeout during order placement meant the take profit was never placed at all and the position was liquidated; fixed leverage was not lowered to the maximum value allowed by the exchange.

Choosing markets

A price filter inside Averages.

The Averages algorithm in Single mode has a built-in price filter: the algorithm starts and stops on its own when the configured price is reached.

Strict market window.

The Active Markets Filter now has a Strict market window checkbox. With it on, the algorithm runs only inside the window from Ignore First up to Max active markets: if a market inside the window fails the filters, the slot is left empty instead of being filled from outside the window. With it off, selection works as before — both schemes are available.

Timeframe selection in Trading Performance.

Metrics were calculated across every supported timeframe, including ones you never use — with a dozen algorithms running that is noticeable CPU and memory. Calculation across timeframes is now switched on by the Performance across timeframes checkbox, with a Max timeframe selector next to it. The All Time and Current Loss columns are one separate setting. The settings themselves were redesigned, and core resource usage reduced.

Also fixed: an algorithm could bypass the Mark Price filter and place an order outside the configured range; Averages handled filter state inconsistently after a manual order cancellation; an algorithm stopped by the Trading Performance filter kept showing as running.

Working with algorithms

Filter by coin type.

Coins carry a thematic category from the exchange — LAYER-1, MEME, DEFI, EQUITY and others. Algorithms now have an additional filter on that category, so you can trade a single narrative without picking coins by hand.

Moving multiple algorithms into a folder.

One action instead of moving them one by one.

Also: the algorithm working hours scheduler was reworked, and a minimum of 0.1 was introduced for the Frame parameter in Detect Shot.

Heads-up on Vector. The "Use detect shot" and "Shot direction" parameters will be removed in the next update — a warning now appears in the Vector configuration. Use the Shot Detect algorithm instead.

Control from Telegram

BotClient can edit Vector and Shot Detect.

Opening them previously returned "Is not valid: ALGORITHM".

Core list management by command.

Adding and removing pairs in the whitelist and blacklist — the same way it is done by hand in the client. This one waited 437 days.

Also: BotClient moved to the new Algorithms Requests System; exceptions when editing an algorithm, zeroed Market Watcher parameters and the ability to select all exchange types in the Balance section were fixed.

Blacklists and whitelists

The configuration moved.

Lists are no longer stored in profile settings — they have their own file.

Also fixed: temporary blocks are now marked with an icon in the Management tab, the current date is preselected when adding from there and is no longer lost after a client restart, temporarily blocked markets are moved to the core blacklist, and the remove-from-list button no longer disappears when editing the block period. Adding a market to the blacklist no longer breaks the default layout, and context menus close on scroll and after copying.

‍

Orders and positions:

1. a deleted algorithm no longer comes back after a core restart and places orders when auto-start options are enabled;
2. the "allow manual trading on overload" option now applies to algorithms, and TP/SL orders get priority;
3. a moved order no longer stays active after Vector is stopped on Bybit; runaway stop-loss price and size escalation in Shot Detect on Spot resolved;
4. emulated orders are cancelled after an application restart; the Trades & Positions tab clears after cancelling all positions and TP/SL and no longer loses the futures position checkbox on account switching; Risk Limit on OKX is shown in USDT instead of contracts; TP/SL can be edited manually again after moving a limit order via hotkey.

Algorithm parameters:

1. the 0.5 s order placement interval in Detect Shot is no longer ignored;
2. a 0.1 s minimum was introduced for Order Frequency, and the Max orders filter is disabled when Follow mode is enabled;
3. the client no longer allows 0 in "Filters → Check Frequency", where the core processes values from one second;
4. an exception when modifying Active Markets Filter parameters was resolved.

Exchanges:

1. the terminal is adapted to the Binance CM-UM architecture unification and handles the new serverShutdown event and the CANCEL_ONLY symbol status, and on OKX the WebSocket disconnect notice on the Business channel;
2. RestClient execution failures on OKX, Bybit and Hyperliquid fixed;
3. on Hyperliquid the QR code now appears after API key confirmation and the core no longer dumps when connecting on an Ubuntu server; SPOT commission calculation on Bybit fixed.

Under the hood:

1. memory usage of Shot Detect and Vector group algorithms optimized in start-stop and pause-run cycles;
2. memory growth from repeated connections resolved;
3. FPS drops and UI freezes on scroll caused by inconsistent leverage changes fixed. Core shutdown was parallelized, and group algorithms moved to a lazy sub-algorithm lifecycle.

Notifications:

1. display optimized for large numbers of notifications, the core restart notification is now sent when that setting is enabled, and Order Placed and Order Filled no longer go to the same Telegram chat when an order is filled immediately. Delta values in profiling mode are displayed as numbers instead of N/A.

‍