> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/guides/compatibility-and-retirements.md).

# Compatibility and Retirements

Find Classic integration guidance, migration instructions for retired Platform interfaces, and historical release records without mixing their scopes.

Use current contracts for a new integration and the owning migration page when maintaining an older client. Classic remains a separate documented API; a Classic integration is not automatically a retired integration.

## Classic Integrations

Start with [Classic authentication](/developer-guide/getting-started/authentication.md), [Classic API resources](/developer-guide/classic-api/core-api.md), and the [Classic SDKs](/developer-guide/classic-api/sdks.md). [Terminology Mapping](/developer-guide/operations/reference/terminology-mapping.md) and [Memory Architecture & API Mapping](/developer-guide/operations/reference/memory-architecture.md) identify their Classic-specific scope. Platform credentials and resource IDs are not interchangeable with Classic ones.

## Retired Platform Interfaces

| Former interface                          | Current guidance                                                                                                                                                                                             |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Remote desktop sessions                   | [Desktop Sessions retirement](/developer-guide/platform-api/conversations/desktop-sessions.md); use [Integrations](/developer-guide/platform-api/integrations.md) for supported external-system connections. |
| Hosted framework-run dispatch and polling | [Agent Runs retirement](/developer-guide/platform-api/functions/agent-runs.md); the unified [Runs inventory](/developer-guide/platform-api/conversations/runs.md) is a separate retained contract            |
| Native-agent definition registry          | [Agent Definitions retirement](/developer-guide/platform-api/functions/agent-definitions.md)                                                                                                                 |
| Standalone ringless voicemail             | [Voicemail retirement](/developer-guide/platform-api/conversations/voicemail.md); ordinary outbound-call voicemail handling has a different lifecycle                                                        |
| Standalone intake upload links            | [Upload-link retirement](/developer-guide/platform-api/data-world-model/intake-links.md); authenticated dataset intake remains current                                                                       |

The migration pages retain their existing URLs. A command or type in an older SDK or CLI does not make a removed server operation available.

## Release History

Use [Current Upgrade Guidance](https://docs.concurrence.com/api-reference/change-logs/upgrade-guide) for present compatibility decisions. [Release archives](https://docs.concurrence.com/api-reference/change-logs) record historical behavior and dates; evaluate current availability using the owning operation and workflow guide.


---

# 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.concurrence.com/developer-guide/guides/compatibility-and-retirements.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.