Improve Ollama provider compatibility for v0.2.2 - #12
Merged
Conversation
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.
Summary
This PR is a focused follow-up for
v0.2.2provider compatibility.The main goal is to make the local Ollama path usable by default for reasoning-capable local models without changing the request behavior for the existing cloud providers.
Included
disables reasoning by default for Ollama requests
reasoning_effort: "none"to Ollama chat-completions payloadsadds focused regression coverage
reasoning_effort: "none"Validation
Repository checks:
ruff check .pyrightpytest -qObserved local-model check:
examples/llm_extraction.pyagainst a local Ollama serviceqwen3.5:4bNotes