feat: provide Modelfile to fix Ollama Web Search structured parsing with Gemma 4 (Fixes #372)#402
Open
Paramveersingh-S wants to merge 2 commits into
Open
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
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.
Description
This PR addresses Issue #372 where Gemma 4 fails to see or recognize web search tool results when running via Ollama.
Gemma 4 relies on a strict formatting structure (
<|tool_call|>and<|tool_response|>). When Ollama's default templates omit or strip these tokens during a web search callback, the context is dropped by the model.Key Changes
apps/Ollama_Gemma4_WebSearch/Modelfilethat injects the required structured tags directly into the template.README.mdguide for users to build this fixed model (ollama create gemma4-search-fixed -f Modelfile) so they can successfully execute web searches via OpenWebUI/Ollama.Fixes #372.