Skip to content

Improve Ollama provider compatibility for v0.2.2 - #12

Merged
HuRuilizhen merged 2 commits into
mainfrom
feat/0.2.2-provider-compatibility
Apr 13, 2026
Merged

Improve Ollama provider compatibility for v0.2.2#12
HuRuilizhen merged 2 commits into
mainfrom
feat/0.2.2-provider-compatibility

Conversation

@HuRuilizhen

Copy link
Copy Markdown
Owner

Summary

This PR is a focused follow-up for v0.2.2 provider 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

    • adds reasoning_effort: "none" to Ollama chat-completions payloads
    • keeps the existing OpenAI-compatible provider path intact
    • does not change request payloads for OpenAI, Mistral, or Qwen
  • adds focused regression coverage

    • verifies Ollama requests include reasoning_effort: "none"
    • verifies cloud-provider requests do not pick up the Ollama-specific field

Validation

Repository checks:

  • ruff check .
  • pyright
  • pytest -q

Observed local-model check:

  • reran examples/llm_extraction.py against a local Ollama service
  • confirmed the example now completes successfully with qwen3.5:4b

Notes

  • this PR intentionally keeps the compatibility fix local to the Ollama path
  • it does not change the cloud-provider request contract for OpenAI, Mistral, or Qwen

@HuRuilizhen
HuRuilizhen merged commit 572c55d into main Apr 13, 2026
1 check passed
@HuRuilizhen
HuRuilizhen deleted the feat/0.2.2-provider-compatibility branch April 14, 2026 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant