feat: Add Poe Provider (Closes #9512)

[faf0]

Related GitHub Issue

Closes: #9512

Description

Add a provider for Poe (https://poe.com/) which offers an OpenAPI compatible API: https://creator.poe.com/docs/external-applications/openai-compatible-api

• Add provider type definitions with multiple models
• Implement PoeHandler extending BaseOpenAiCompatibleProvider
• Add UI component for API key configuration
• Add validation logic for API key
• Add to provider settings schema and constants
• Add translations
• Add poeApiKey to SECRET_STATE_KEYS for proper storage
• Add Poe provider documentation
• Default model: gpt-5.1-codex-mini

Similar to #9461.

Test Procedure

• Build and run the extension from the faf0/add-poe-provider branch.
• Open the Roo Code extension view.
• Navigate to the Settings panel.
• In the "Providers" section, select "Poe" from the "API Provider" dropdown.
• Verify: The label for the API key input field reads "Poe API Key" and the button below it reads "Get Poe API Key".
• Run Roo Code.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Does this PR necessitate updates to user-facing documentation?

• No documentation updates are required.
• Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs repository).

---

Important

Add Poe provider integration with API handling, UI components, and validation logic.

• Behavior:
  • Add PoeHandler in poe.ts extending BaseOpenAiCompatibleProvider for Poe API integration.
  • Add Poe to providerSettingsSchemaDiscriminated and modelIdKeysByProvider in provider-settings.ts.
  • Add Poe API key validation in validate.ts.
• UI:
  • Add Poe API key input in ApiOptions.tsx.
  • Add Poe to provider dropdown in constants.ts.
• Translations:
  • Add Poe API key translations in multiple locale files.
• Misc:
  • Add poeApiKey to SECRET_STATE_KEYS in global-settings.ts.
  • Add Poe export in providers/index.ts.

^{This description was created by for 46a87c2. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Re-review complete. No new issues found.

The changes since the last review consist only of a merge commit from main (e60c463). The Poe provider implementation itself has not changed and remains correctly implemented.

Previous reviews

• 46a87c2: Review #1

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[neslot]

Poe is not an option in the drop down

[faf0]

Poe is not an option in the drop down

Have you rebuilt the extension and installed it from this branch?

[neslot]

No i didn't realise i had to do that, thanks

…

On Wed, 10 Dec 2025, 12:07 pm Fabian Foerg, ***@***.***> wrote: *faf0* left a comment (RooCodeInc/Roo-Code#9515) <#9515 (comment)> Poe is not an option in the drop down Have you rebuilt the extension and installed it from this branch? — Reply to this email directly, view it on GitHub <#9515 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMANJLJVIJ55PKMUJDOUD7L4A5W6FAVCNFSM6AAAAACM6NVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMZUHEZDSNJXGQ> . You are receiving this because you commented.Message ID: ***@***.***>