docs(configuration): note url accepts base URL or full /responses endpoint - #623
Merged
lizhengfeng101 merged 1 commit intoJul 31, 2026
Merged
Conversation
…point Follow-up to alibaba#562 (which documented the openai-responses protocol). Adds the one clarification alibaba#562 lacked: for openai-responses, the `url` field accepts either the API base URL or the full `/responses` endpoint, since ensureResponsesEndpoint normalizes both forms. Added in en/zh/ja. Signed-off-by: FenjuFu <92919259+FenjuFu@users.noreply.github.com>
Contributor
|
✅ OpenCodeReview: No supported files changed. |
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.
What
Follow-up to #562 as suggested by @lizhengfeng101 in #563.
#562 already documented the
openai-responsesprotocol across all three locales. This adds the one incremental clarification #563 had that #562 lacked: foropenai-responses, theurlfield accepts either the API base URL or the full/responsesendpoint.Added one sentence right after the
openai-responsesexample inen,zh, andja.Why it's accurate
internal/llm/responses_client.go→ensureResponsesEndpointnormalizes both forms. Its own contract comment states:So a user can supply either shape and it resolves the same way — worth stating so people don't guess.
Scope
Docs-only, +2 lines per locale (the sentence + a blank line), no other changes. Rebased on current
mainso it sits cleanly on top of #562.Refs #556, #563