> For the complete documentation index, see [llms.txt](https://docs.developers.symphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developers.symphony.com/admin-guide/change-log/api-agent/archives/agent-23.6-lts.md).

# Agent - 23.6 (LTS)

## Agent Download

{% hint style="info" %}
To download the Agent, click [here](https://storage.googleapis.com/sym-platform/developers/rest-api/agent-23.6.6.zip).

For a list of Agent x SBE compatibilities, click [here](/admin-guide/agent-guide/sbe-x-agent-compatibility-matrix.md).
{% endhint %}

## Agent Changes

### Agent 23.6.6

* Fixed security vulnerabilities.

### Agent 23.6.5

* Fixed security vulnerabilities.

### Agent 23.6.4

* Fixed security vulnerabilities.
* Fixed Cross-Origin Resource Sharing (CORS) issue on allowed domains check.

### Agent 23.6.2

* Fixed security vulnerabilities.

### Agent 23.6.1

* Enable OBO for the [Message Update](https://developers.symphony.com/restapi/main/messages/update-message-v4) endpoint.
* Enable OBO for the [Blast Message](https://developers.symphony.com/restapi/main/messages/blast-message) endpoint.
* **Enable the datafeed bridge by default**.
  * This means that if you dont have a value set in your config file for the property `df1ToDf2Bridge`, then your bots that are still using the Datafeed v1 APIs will transparently start using the Datafeed v2 service. You can still disable this behavior by setting the `df1ToDf2Bridge` parameter to false.
  * **Important**: If you copied over your previous Agent config file, then the bridge may still be disabled because the bridge's default value was false in previously provided config files. In order to ensure that the bridge is enabled please check that the `df1ToDf2Bridge` parameter is either absent, or set to true. It is important to start testing your bots with the bridge enabled to discover issues before the bridge is enforced in a subsequent version.
* Fixed security vulnerabilities.
* Changes since last LTS release (23.3)
  * Added support of new crypto-packs to allow customers to migrate their HSM integrations to the latest firmwares (HSM 7). If you are interested in this new capability, please get in touch with your Symphony representative. Moving to HSM 7 has dependencies on other components than the agent.
  * Fixed `/agent/actuator` endpoints so they work even if the Agent runs with same `management.server.port` than `server.port`


---

# 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.developers.symphony.com/admin-guide/change-log/api-agent/archives/agent-23.6-lts.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.