fix(models): correct sonar-deep-research model name in Perplexity config#6069
Merged
HenryHengZJ merged 1 commit intoMar 31, 2026
Conversation
The sonar-deep-research entry under chatPerplexity had its name field incorrectly set to 'sonar' instead of 'sonar-deep-research'. This caused two issues: 1. Users selecting sonar-deep-research in the UI would hit the regular sonar API endpoint instead of the deep research endpoint 2. A duplicate name collision with the existing sonar entry, causing incorrect cost lookups
HenryHengZJ
approved these changes
Mar 31, 2026
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
2 participants
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.
The
sonar-deep-researchentry underchatPerplexityinmodels.jsonhad itsnamefield incorrectly set to"sonar"instead of"sonar-deep-research".Impact
This fix addresses two significant issues:
sonarAPI endpoint, resulting in lower-quality search results than expected.namecollision with the existingsonarentry at line 1608, which led to incorrect cost calculations and model lookups within themodelLoader.Changes
packages/components/models.jsonto change thenamefield for thesonar-deep-researchlabel from"sonar"to"sonar-deep-research".Bug Reproduction
The video below demonstrates the issue, when selecting
sonar-deep-researchfrom the model dropdown, the API request is sent with"sonar"as the model identifier instead of"sonar-deep-research":Screen.Recording.2026-03-28.013644.mp4