-
Notifications
You must be signed in to change notification settings - Fork 11.6k
feat: add responses support for cloudflare #1569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Calcium-Ion
merged 1 commit into
QuantumNous:alpha
from
duyazhe:codex/cloudflare-responses
Aug 12, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Avoid cross-channel coupling; consider moving Responses handlers to a neutral package
Importing the openai channel from the cloudflare adaptor couples providers. It works, but increases the risk of import cycles and makes layering less clean. Prefer extracting OaiResponses* handlers into a shared helper package (e.g., relay/channel/responses or relay/common/responses) and depend on that from both channels.
Run this to ensure there’s no import cycle from the openai package back to cloudflare:
🏁 Script executed:
Length of output: 964
Decouple Response Handlers into a Shared Package
I ran ripgrep against the OpenAI channel and confirmed that
relay/channel/openai/relay_responses.godefines bothOaiResponsesHandlerandOaiResponsesStreamHandler, and that it does not import the Cloudflare channel (no import cycles detected). To keep clean layering and avoid cross-channel coupling, please extract these handlers into a neutral package (e.g.relay/channel/responses) and update both adaptors to depend on that.Key locations to update:
relay/channel/cloudflare/adaptor.go• Remove
import "one-api/relay/channel/openai"• Import
one-api/relay/channel/responsesinstead• Change calls to
openai.OaiResponsesHandler→responses.OaiResponsesHandler(and likewise for the stream variant)relay/channel/openai/relay_responses.go• Move this file (or its handler functions) into
relay/channel/responses• Update package declarations and imports accordingly
Example diff for the Cloudflare adaptor:
This refactor preserves functionality, prevents accidental import cycles, and promotes better separation of concerns.
🤖 Prompt for AI Agents