> 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.3/version-6.3.2.md). # Version 6.3.2 Released on 15th of September 2026 This release introduces [Frends MCP, which lets AI assistants such as Claude Code work with your Frends Tenant](/release-notes/frends-6.3/new-features.md#frends-mcp). Frends MCP is off by default and is enabled per deployment. This release also includes the new features released with Frends 6.3, listed in [New Features](/release-notes/frends-6.3/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 10.0.7 or newer to be installed. The Windows Agent and Management Web Portal require the .NET 10 hosting bundle to be installed. Cloud Agents and Compliant Cloud images include .NET 10 out of the box. {% endhint %} {% hint style="warning" %} Remember to check the [Breaking Changes](/release-notes/frends-6.3/breaking-changes.md) for this version of Frends before updating. {% endhint %} ## Process and Subprocess ### Improvements * The Process editor has a new **Auto layout** button that re-arranges the whole diagram in one undoable step. * The diagram editor library has been updated: the shape replace menu looks different, external labels can be resized and a Cut shortcut is available. * Processes are now compiled with optimisations on, which makes large scopes with many dynamic expressions lighter to run. ### Bug fixes * Fixed custom shape colours hiding the added, removed, moved and edited markers in the Change Log diff view. ## API Management and API Policies ### Bug fixes * Fixed the Modifier of an API specification not changing when another user edits it. ## Agent ### Improvements * Settings changes made while an Agent is offline, such as OAuth applications and API keys, are now delivered automatically when the Agent reconnects. ### Bug fixes * Fixed the cross-platform Windows Agent crashing with a stack overflow in Processes with many dynamic expressions. * Fixed schedule Triggers never launching on Agents with SQLite stores after an upgrade from 6.2.x. * Fixed the per-Process start and finish messages of the cross-platform Agent never reaching the Process log file. * Fixed one misconfigured OAuth application disabling all OAuth authentication on the Agent, including portal-issued tokens and the MCP endpoint. Invalid signing certificate details are now rejected when saved. * Fixed API Triggers failing to start when the endpoint's request body schema uses `allOf`. * Fixed a Kubernetes Deployment-mode Agent failing to start again after a restart under the same name. ## AI Connector and MCP ### Bug fixes * Fixed searching AI models by display name. ## UI and Web Portal ### Bug fixes * Fixed long HTTP Trigger API paths overflowing the Trigger details on the Environment Agent page. ## Security and Authentication ### Improvements * Agent passwords, Agent Group connection strings and OpenID Connect client secrets are now redacted in the audit log. ### Bug fixes * Fixed users restricted by Allow tag rules not seeing drafts they saved for a new Process. ## Log Service and Observability ### Improvements * Log retention on S3 storage now uses lifecycle rules by default; see the upgrade notes. ## Infrastructure, Build, and Dependencies ### Improvements * The S3 client can now be configured for object stores that differ from AWS defaults, which adds support for Oracle OCI Object Storage for both the Log Service and the built-in NuGet server. --- # 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.3/version-6.3.2.md?ask=&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.