fix(sse): route Poe API-key traffic through DefaultExecutor (#8969) - #9014
Merged
diegosouzapw merged 1 commit intoAug 6, 2026
Merged
Conversation
…zapw#8969) Stop aliasing canonical `poe` to PoeWebExecutor so API-key requests hit api.poe.com Chat Completions / Responses / Claude-only Messages instead of the web GraphQL path that returned HTTP 405.
Prudhvivuda
force-pushed
the
fix/8969-poe-api-executor
branch
from
August 5, 2026 14:29
b4767d2 to
60299ad
Compare
diegosouzapw
merged commit Aug 6, 2026
701d60d
into
diegosouzapw:release/v3.8.50
9 of 16 checks passed
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.
Summary
poetoPoeWebExecutorso API-key connections useDefaultExecutoragainstapi.poe.cominstead of the web GraphQL/api/gql_POSTpath that returned HTTP 405./v1/messages.Closes #8969
Test plan
node --import tsx/esm --test tests/unit/poe-api-executor-regression.test.tsnode --import tsx/esm --test tests/unit/chatcore-execution-credentials.test.tsnode --import tsx/esm --test tests/unit/executor-poe-web.test.tsnode --import tsx/esm --test tests/unit/poe-provider-models-baseurl.test.tsnode --import tsx/esm --test tests/unit/web-cookie-providers-new.test.tspoe-webstill usesPoeWebExecutor/ cookie GraphQL pathpoe/<model>Chat Completions with a real API key returns 200 (not 405)