> For the complete documentation index, see [llms.txt](https://gunthy.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gunthy.gitbook.io/wiki/about/whats-new/new-in-v16.7+.md).

# New in v16.7+

Gunbot v16**.**9 adds several new features and fixes known issues.

## **Upgrading**

**There are no config changes for v16.9 In case you are upgrading from v16, replacing only the executable file** (gunthy-win.exe / gunthy-linux / gunthy-macos / gunthy-arm) **is all that's needed to upgrade.**

In case you are upgrading from an older version, refer to the changelogs of previous versions for instructions, or start with a fresh installation.

\*\*\*\*[**Download release**](/wiki/setup-and-general-settings/installation/download.md)\*\*\*\*

## New features / changes in v16.9

* **Support for our exchange:** [**Gunthy**](https://exchange.gunthy.org)\*\*\*\*
* **New partner exchange:** Binance
* **New Autoconfig features:** 
  * New filter: linear regression channel
  * Option to filter on pair variables from another exchange
* **Support for Bittrex credits:** automatically used when enabled at Bittrex and there is a balance for BTXCRD

## New features / changes in v16.7

* **New partner exchange:** Kraken Futures partnered with Gunbot and is now fully supported in Gunbot.
* **Many new Autoconfig features:**
  * Reduce average processing time for jobs with ticker filters.
  * Add an option to reset user variables, without having to create a separate job for it.
  * New filter types: 
    * bearishStandardDeviationChannel (+ \*History variants)
    * many time based filters
    * filters based on last order type for specific pairs
    * strategy name filter
    * variableNotExist: to check if a variable is not set
    * allowsHedging: only add pairs that allow for direct hedging between a specified hedge pair
  * Per pair user variables, allowing you to create pair specific interactions between jobs.
  * Option to disable Telegram notifications per job.
  * Option to change exchange delay with a manageOverrides job.
  * New job types:
    * manageBotSettings: to make changes in global bot settings
    * hedgeGB & hedgeGB2 allow for hedging with Gunbot

## **Gunbot core bugfixes**

Notable fixes:

* Fix UTA for H20/M20 pair on Bitmex.
* Better tuning for timely fetching Kucoin tickers.
* Fix many profit calculations in CryptoSight, fix admin rights issue.
* Add support for ALGO and USDC pairs on Kraken.
* Fix TV being stuck after an incoming close alert when there is no position to close.
* Better handling of DU count.
* Fix an issue with TakeProfit that sometimes made it falsely trigger when prices moved up.
* Autoconfig fixes: 
  * Fix backtesting for jobs using \*History filters.
  * Fix issue with processing Huobi tickers in case new pairs are introduced on the exchange.
  * Better handling of removing the last pair on an exchange.
  * Fix parsing of markdown elements in telegram alerts.
  * Automatically purge old history data when history value in config gets reduced.
  * Also look for mvts value in pair overrides.
* Various fixes that improve performance on Kraken Futures


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gunthy.gitbook.io/wiki/about/whats-new/new-in-v16.7+.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.