ollama - 💡(How to fix) Fix 使用ollama api调用qwen3.5时如何关闭思考模式 [4 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#14585Fetched 2026-04-08 00:34:06
View on GitHub
Comments
4
Participants
4
Timeline
6
Reactions
0
Timeline (top)
commented ×4closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse
<img width="910" height="930" alt="Image" src="https://github.com/user-attachments/assets/3947a315-954b-4673-b5f6-7be5b767d30d" />

qwen3.5的思考链和之前的不一样,之前的/no_think 不起作用

extent analysis

Fix Plan

The fix involves updating the thinking chain logic to accommodate the changes in qwen3.5.

Steps to Fix

  • Review the thinking chain logic in the codebase and identify areas that need updates.
  • Update the /no_think endpoint to handle the new thinking chain logic.
  • Add conditional statements to handle different thinking chain versions.

Example Code

# Updated thinking chain logic
def thinking_chain(version):
    if version == "qwen3.5":
        # New thinking chain logic for qwen3.5
        return new_thinking_chain()
    else:
        # Old thinking chain logic
        return old_thinking_chain()

# Updated /no_think endpoint
@app.route("/no_think", methods=["GET"])
def no_think():
    version = request.args.get("version")
    if version == "qwen3.5":
        # Handle new thinking chain logic
        return thinking_chain(version)
    else:
        # Handle old thinking chain logic
        return old_no_think()

Verification

  • Test the updated /no_think endpoint with different versions to ensure it handles both old and new thinking chain logic correctly.
  • Verify that the new thinking chain logic is correctly implemented for qwen3.5.

Extra Tips

  • Ensure to update documentation to reflect changes in the thinking chain logic.
  • Consider adding versioning to the API to handle different thinking chain versions more elegantly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING