feat: add support for reasoning_content field in OpenAI provider #1294
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.
This change adds support for handling the 'reasoning_content' field in streaming responses from custom OpenAI-compatible APIs, allowing models that return reasoning content in this field to display their chain of thought in Crush UI.
Previously, Crush only handled the 'reasoning' field but not the 'reasoning_content' field used by some custom servers.
CONTRIBUTING.md.