docs(go): ask clients to reuse one session ID across all endpoints - #48981
Open
IsmaelMartinez wants to merge 1 commit into
Open
IsmaelMartinez wants to merge 1 commit into
IsmaelMartinez wants to merge 1 commit into
Conversation
Requirement 3 did not say the same ID must be reused on every request and sent on every endpoint, which is how a client can set it in one SDK's middleware and miss the others. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019u64ksoe2v3xjdRe4uBMhX
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
1 participant
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.
Issue for this PR
No issue; documentation clarification.
Type of change
What does this PR do?
Requirement 3 under "Where can I use it?" asks for a stable session ID per conversation, but it does not say the same ID has to be reused on every request and sent on every endpoint. That gap is easy to fall into: Docker Agent's first implementation (docker/docker-agent#4190) only set the header in its OpenAI SDK middleware, so
/messagesrequests went without it, and the DeepSeek Harness row in the table describes the same shape. This adds one clarifying sentence to requirement 3 in English and the 17 locale copies. The translations follow the English wording; happy to adjust any of them.How did you verify your code works?
bunx prettier@3.6.2 --checkon the 18go.mdxfiles passes. Docs-only, no site build.Screenshots / recordings
N/A, no UI change.
Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_019u64ksoe2v3xjdRe4uBMhX