Open
Conversation
ollama.ResponseError carries a status_code, so 4xx errors like "model not found" (404) should surface as actionable errors rather than being misreported as connectivity failures. Only 5xx errors are now mapped to ConnectionError, matching the pattern used by the Anthropic and OpenAI providers. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
ollamaLLM provider using Ollama's Python client and/api/chatWhat changed
anton/llm/ollama.pyfor native Ollama inference and model listinganton/llm/openai_compat.pyanton/llm/setup.pyand reused them from CLI setup and/setupANTON_OLLAMA_BASE_URLsettings support and scratchpad Ollama propagationVerification
pytest -q(411 passed)qwen3:0.6bstreamed reasoning progress through the new Ollama pathministral-3:8breturned normal native Ollama responsesChatSession.turn(...)completed successfully with Ollama configured as both planning and coding provider