> 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/client-2.0-apis/client-2.0-23.02.md).

# Client 2.0 - 23.02

### Enhanced tags

* **Important**: The introduction of the new enhanced tags that will replace the existing $cashtags may have an impact on your existing bots and apps. More information available [here](/bots/messages/overview-of-messageml/messageml-basic-format-tags/shorthand-tags/enhanced-tags-notice.md).

### Desktop interop

* **View Chat**: Display an existing chat conversation in Symphony, identified by its streamID or list of participants.
* **FDC3 configuration through user settings**. End users can configure their desktop provider directly from the settings in their Symphony client, thanks to the new Interoperability tab.
* **ECP support for FDC3**: It is possible to enable FDC3 on ECP (Embedded Collaboration Platform), so Symphony can interoperate with local apps, even when Symphony is embedded in another web application.

**Important**: As we add support for new intents in Symphony, please keep the Symphony app directory entry in your DIP up-to-date, as the desktop agent may block intents if they are not listed as supported by Symphony in the application directory.

Refer to the [documentation on desktop interoperability](/embedded-modules/desktop-interoperability.md) for more information.


---

# 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/client-2.0-apis/client-2.0-23.02.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.