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

# 6.5

### Migration guide

Version 6.5 is compatible with 6.4. It operates on the same stack and custom components should function without modification.

{% hint style="warning" %}
The **Insights Chart Editor** and **Insights Dashboard** SDK widgets (`appmixer.ui.InsightsChartEditor`, `appmixer.ui.InsightsDashboard`) were [removed](/changelog/version-6/6/6.5/6.5.0.md#removed) in this version. If your embedded application uses these widgets, remove them before upgrading. The Charts REST API remains available for existing chart data.
{% endhint %}

{% hint style="info" %}
Flow validation now reports components that require authentication but have no connected account. When validation before flow start is enabled (`FLOW_VALIDATE_BEFORE_START`), flows with unauthenticated connectors are rejected at start instead of failing at runtime — previously such flows started and failed with "Missing access token".
{% endhint %}

{% hint style="warning" %}
Appmixer widgets now render thin, theme-coloured scrollbars instead of native ones. If your host application styles `::-webkit-scrollbar` inside Appmixer widgets, those rules are ignored in Chromium from 6.5 onwards — the SDK's standard `scrollbar-width` / `scrollbar-color` properties switch Chrome and Edge to the standard scrollbar rendering path. Migrate them to the standard properties, or restore the native scrollbars. See [Custom Theme → Scrollbars](https://docs.appmixer.com/6.0/6.5/customizing-embedded-ui/custom-theme#scrollbars).
{% endhint %}

{% content-ref url="/pages/Hc3lGwqzGDWJwGBX9da5" %}
[6.5.5](/changelog/version-6/6/6.5/6.5.5.md)
{% endcontent-ref %}

{% content-ref url="/pages/yyH8kbQuwbkNRR2k7aDq" %}
[6.5.4](/changelog/version-6/6/6.5/6.5.4.md)
{% endcontent-ref %}

{% content-ref url="/pages/XZnFWZy8TwuqpDvv1saG" %}
[6.5.3](/changelog/version-6/6/6.5/6.5.3.md)
{% endcontent-ref %}

{% content-ref url="/pages/LdncNuKUpACzCkp7xFD1" %}
[6.5.2](/changelog/version-6/6/6.5/6.5.2.md)
{% endcontent-ref %}

{% content-ref url="/pages/OC5ixzkSiZM1hymIucF2" %}
[6.5.1](/changelog/version-6/6/6.5/6.5.1.md)
{% endcontent-ref %}

{% content-ref url="/pages/Jbs0Z2LNBRJo7RDYu8GT" %}
[6.5.0](/changelog/version-6/6/6.5/6.5.0.md)
{% endcontent-ref %}


---

# 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.appmixer.com/changelog/version-6/6/6.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.