feat(perplexity): deprecate chat completions clients - #2392
Draft
andrewmadson-pplx wants to merge 1 commit into
Draft
feat(perplexity): deprecate chat completions clients#2392andrewmadson-pplx wants to merge 1 commit into
andrewmadson-pplx wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 1759a0a The changes in this PR will be included in the next version bump. This PR includes changesets to release 39 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The Node Perplexity integration still presents Sonar Chat Completions as the primary path even though the plugin already includes an Agent API Responses client. Its Responses README example also passes the Chat Completions model name
sonar-pro, while both legacy TypeScript entry points offer no actionable migration warning and the OpenAI compatibility helper defaults to a retired model.What changed
responses.LLMwithperplexity/sonarthe primary Perplexity README example.openai.LLM.withPerplexity().withPerplexity()to the supportedsonar-procompatibility default and replace retired Perplexity model literals with current Sonar model IDs.Behavior and scope
This is a soft deprecation. Explicit Sonar Chat Completions configurations continue to construct and now emit an actionable warning. The dedicated
responses.LLMremains unchanged: it defaults toperplexity/sonar, useshttps://api.perplexity.ai/v1, disables WebSocket transport, readsPERPLEXITY_API_KEY, and sends the LiveKit attribution header.Coordinated Python change: livekit/agents#7069.
Coordinated Perplexity guide: ppl-ai/api-docs#807.
Tracking: Sonar to Agent migration, API-3590, and API-3389.