docs: correct Responses stream diagnosis - #150
Merged
Merged
Conversation
Contributor
|
🎉 This PR is included in version 0.10.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
Correct the public diagnosis of the OpenCode V2 Responses failure. The supplied session's actual invalid chunk was
response.output_item.added; itsfunction_callitem omitted the requiredargumentsstring. The earlier annotation-event wording was wrong.Document the shared endpoint policy and its real scope: current catalog models with both Chat and Responses use Chat; Messages-only models keep Messages; the current catalog has no Responses-only entries. Only the DeepSeek V4.1 Flash
#maxResponses tool-call failure was observed, so the docs avoid claiming every model's Responses stream was tested.Validation:
bun run checkpassed: 235 tests and 671 expectations.printf TOOL_CALL_SMOKE_OKtool call passed with the local checkout on installed V2.0.18 and official V1.18.30/V2.0.18 Docker images.