Repository navigation
docs(vllm): document opt-in assistant reasoning history - #1456
Open
jibanez-staticduo wants to merge 4 commits into
Open
jibanez-staticduo wants to merge 4 commits into
jibanez-staticduo wants to merge 4 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
3 of 6 tasks
This branch was successfully deployed
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.
Document opt-in assistant history forwarding for hosted vLLM and the outgoing
reasoning_content_fieldselector for hosted vLLM and OpenAI-compatible Chat CompletionsExplains precedence for existing, empty, and null values, independent forwarding permission and template policy, Responses-to-Chat routing, cache isolation, and the vLLM Chat Completions versus tokenize normalization difference. Requires the release containing BerriAI/litellm#41050 and makes no performance claim
Validation: writing-style and documentation-structure checks pass for docs/providers/vllm.md