Ollama think=false breaks format structured output silently

What this error means

think=false with format parameter causes format constraint to be silently ignored — outputs plain text instead of JSON is a Ollama failure pattern reported for developers trying to fix ollama structured output being ignored when think=false is set. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Ollama issue #15260: Setting think=false with format= parameter causes the format constraint to be completely ignored for gemma4 models. Model outputs plain text instead of requested JSON. Server returns HTTP 200 with no errors logged. Same bug class as qwen3.5 series (#14645). Category mapped to Ollama per approved list.

Common causes

• Ollama issue #15260: Setting think=false with format= parameter causes the format constraint to be completely ignored for gemma4 models. Model outputs plain text instead of requested JSON. Server returns HTTP 200 with no errors logged. Same bug class as qwen3.5 series (#14645). Category mapped to Ollama per approved list.

Quick fixes

1. Confirm the exact error signature matches think=false with format parameter causes format constraint to be silently ignored — outputs plain text instead of JSON.
2. Check the Ollama account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/ollama/ollama/issues/15260

Evidence note: Ollama issue #15260: Setting think=false with format= parameter causes the format constraint to be completely ignored for gemma4 models. Model outputs plain text instead of requested JSON. Server returns HTTP 200 with no errors logged. Same bug class as qwen3.5 series (#14645). Category mapped to Ollama per approved list.

Related errors

• Ollama

FAQ

What should I check first?

Start with the exact think=false with format parameter causes format constraint to be silently ignored — outputs plain text instead of JSON text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Ollama workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without think=false with format parameter causes format constraint to be silently ignored — outputs plain text instead of JSON.