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

# v8.5

### Release highlights

#### Features and fixes delivered with this release

### Features&#xD;&#xD;

* TD-8088 Structure to Concept relationship suggestions to use AI agentic workflows.
* TD-8097 AI assistant improvements.
* TD-8075 Add global context to AI agents.
* TD-8089 Support other AI providers.
* TD-8082 Change Quality Rule description from Enriched Text to Markdown.
* TD-8054 Migration of enriched text fields to markdown type of field.
* TD-7961 Grants download file should use source user name from the grant if Truedat's user name does not exist.
* TD-7256 Add remediation plans info to Metrics.
* TD-8022 Add structure tags info to Metrics.

### Fixes&#xD;

* TD-8090 In a structure, customised header does not display metadata fields.
* TD-7346 Links in some notifications not working.
* TD-8148 Lineage graphs in Structures and Lineage lost styles.
* TD-8117 UI/Accessibility regression: Fix visual styles.


---

# 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://docs.truedat.io/release-notes/v8/v8.5.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.
