feat: add Poe provider support #9513
Open
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.
This PR attempts to address Issue #9512. Feedback and guidance are welcome.
Summary
Adds support for Poe (poe.com) as a provider in Roo Code, leveraging their OpenAI-compatible API.
Changes
PoeHandlerusingBaseOpenAiCompatibleProviderTesting
Related
Closes #9512
Previously requested in #6594
Important
Adds support for Poe provider with multiple models, integrating it into the provider registry and configuration system.
PoeHandlerinsrc/api/providers/poe.tsusingBaseOpenAiCompatibleProvider.provider-settings.tsandindex.ts.PoeModelIdandpoeModelsinproviders/poe.ts.claude-3-5-sonnet.poeSchematoproviderSettingsSchemaDiscriminatedinprovider-settings.ts.ProfileValidatorto handle Poe inProfileValidator.ts.PoeHandlerexport insrc/api/providers/index.ts.buildApiHandlerinsrc/api/index.tsto include Poe.This description was created by
for 3552782. You can customize this summary. It will automatically update as commits are pushed.