> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/release-notes/frends-6.0/version-6.0.6.md).

# Version 6.0.6

Released on 11th of September 2025

This release includes the new features released with Frends 6.0, listed in [New Features](/release-notes/frends-6.0/new-features.md), as well as improvements and bug fixes from the earlier releases.

{% hint style="info" %}
On-premise Cross-platform Agents require .NET Runtime 8.0.21 or newer to be installed.
{% endhint %}

## **UI**

### **Bug fixes**

* Fixed issue with AI assistant for code shape not being able to take generated code into use sometimes after updating the model
* Fixed issue with editing API Policies targeting Agent group not working after deleting the Agent Group

## **Agent**

### **Bug fixes**

* Fixed issue with API Passthrough All endpoints not expanding path parameters correctly
* Fixed issue with non-standard HTTP methods (e.g. PROPFIND) causing a lot of errors in the Agent log


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frends.com/release-notes/frends-6.0/version-6.0.6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.