[GH-ISSUE #14029] The Hall Of Shame #34929

Closed
opened 2026-04-22 18:55:52 -05:00 by GiteaMirror · 16 comments
Owner

Originally created by @techie-learner on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14029

Resolved

Originally created by @techie-learner on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14029 Resolved
GiteaMirror added the appfeature request labels 2026-04-22 18:55:52 -05:00
Author
Owner

@ryanmon1 commented on GitHub (Feb 2, 2026):

Can't you use /set nothink from the CLI to fix this?

<!-- gh-comment-id:3837208940 --> @ryanmon1 commented on GitHub (Feb 2, 2026): Can't you use /set nothink from the CLI to fix this?
Author
Owner

@rick-github commented on GitHub (Feb 2, 2026):

Can't you use /set nothink from the CLI to fix this?

No. That only affects API calls made from the ollama CLI client, what the OP wants is the ability to control think from the ollama GUI client. An alternative is to use a different client, for example OpenWebUI has a browser-based GUI and the ability to set the value of think.

<!-- gh-comment-id:3837489485 --> @rick-github commented on GitHub (Feb 2, 2026): > Can't you use /set nothink from the CLI to fix this? No. That only affects API calls made from the ollama CLI client, what the OP wants is the ability to control `think` from the ollama GUI client. An alternative is to use a different client, for example OpenWebUI has a browser-based GUI and the ability to set the value of `think`.
Author
Owner

@techie-learner commented on GitHub (Feb 3, 2026):

Can't you use /set nothink from the CLI to fix this?

Well I will use Ollama GUI app and that why I want that "Thinking" button in Ollama GUI to disable or enable. Ah wait I tried /set nothink even on CMD one and Ollama GUI , and it didn't not worked. It just keeps thinking, so that why I requested a "Thinking" button for ollama GUI.

<!-- gh-comment-id:3839066767 --> @techie-learner commented on GitHub (Feb 3, 2026): > Can't you use /set nothink from the CLI to fix this? Well I will use Ollama GUI app and that why I want that "Thinking" button in Ollama GUI to disable or enable. Ah wait I tried /set nothink even on CMD one and Ollama GUI , and it didn't not worked. It just keeps thinking, so that why I requested a "Thinking" button for ollama GUI.
Author
Owner

@Nikorasu commented on GitHub (Mar 24, 2026):

I second. Would be nice to have a button somewhere, in that default Ollama GUI, which I actually end up using a lot. (Course the GUI could also use better editing and chat management, but that's not as important as simply being able to disable thinking.)

Alternatively, doing it at the modelfile level would be acceptable. Being able to disable thinking, then /save that to a new modelfile, so we can just use that modelfile in the GUI or other purposes, with thinking disabled by default, would be even more useful.

<!-- gh-comment-id:4119362329 --> @Nikorasu commented on GitHub (Mar 24, 2026): I second. Would be nice to have a button somewhere, in that default Ollama GUI, which I actually end up using a lot. (Course the GUI could also use better editing and chat management, but that's not as important as simply being able to disable thinking.) Alternatively, doing it at the modelfile level would be acceptable. Being able to disable thinking, then /save that to a new modelfile, so we can just use that modelfile in the GUI or other purposes, with thinking disabled by default, would be even more useful.
Author
Owner

@rick-github commented on GitHub (Mar 24, 2026):

The GUI supports thinking control, but it currently only works for deepseek-v3.1 models.

Image

#10961 for controlling it at the Modelfile level.

<!-- gh-comment-id:4119781023 --> @rick-github commented on GitHub (Mar 24, 2026): The GUI supports thinking control, but it currently only works for deepseek-v3.1 models. <img width="483" height="142" alt="Image" src="https://github.com/user-attachments/assets/04e66826-e87a-4108-aea4-a3599c93c2a6" /> #10961 for controlling it at the Modelfile level.
Author
Owner

@forbiddenPHP commented on GitHub (Apr 2, 2026):

BUMP! It's a pain in the a to have loops of thinking from whatever model! PLEASE hear us! <3

<!-- gh-comment-id:4174270343 --> @forbiddenPHP commented on GitHub (Apr 2, 2026): BUMP! It's a pain in the a to have loops of thinking from whatever model! PLEASE hear us! <3
Author
Owner

@Rastafabisch commented on GitHub (Apr 2, 2026):

This would really useful for the QWEN 3.5 models! :)

<!-- gh-comment-id:4176146513 --> @Rastafabisch commented on GitHub (Apr 2, 2026): This would really useful for the QWEN 3.5 models! :)
Author
Owner

@dhirajlochib commented on GitHub (Apr 2, 2026):

Implemented in PR #15217.

Two-file frontend change:

  • useModelCapabilities.ts: added useHasThinkingCapability hook (mirrors the existing useHasVisionCapability / useHasToolsCapability pattern — checks for 'thinking' in the capabilities API response)
  • ChatForm.tsx: replaced selectedModel?.model.toLowerCase().startsWith('deepseek-v3.1') with useHasThinkingCapability(selectedModel?.model)

The modelSupportsThinkingLevels check (gpt-oss low/medium/high) is left as-is since that's a separate product feature.

<!-- gh-comment-id:4178494154 --> @dhirajlochib commented on GitHub (Apr 2, 2026): Implemented in PR #15217. Two-file frontend change: - `useModelCapabilities.ts`: added `useHasThinkingCapability` hook (mirrors the existing `useHasVisionCapability` / `useHasToolsCapability` pattern — checks for `'thinking'` in the capabilities API response) - `ChatForm.tsx`: replaced `selectedModel?.model.toLowerCase().startsWith('deepseek-v3.1')` with `useHasThinkingCapability(selectedModel?.model)` The `modelSupportsThinkingLevels` check (gpt-oss low/medium/high) is left as-is since that's a separate product feature.
Author
Owner

@zamiere commented on GitHub (Apr 3, 2026):

Creating a fake deepseek-v3.1-something model doesn’t solve the problem with the gemma4 model. The button appeared, but it doesn’t work. (0.9.0 ollama version)

<!-- gh-comment-id:4183578384 --> @zamiere commented on GitHub (Apr 3, 2026): Creating a fake deepseek-v3.1-something model doesn’t solve the problem with the gemma4 model. The button appeared, but it doesn’t work. (0.9.0 ollama version)
Author
Owner

@techie-learner commented on GitHub (Apr 7, 2026):

Creating a fake deepseek-v3.1-something model doesn’t solve the problem with the gemma4 model. The button appeared, but it doesn’t work. (0.9.0 ollama version)

@zamiere Obviously. Renaming a model doesn't rewrite its architecture. You just tricked the UI into showing a button that the backend doesn't know how to use for Gemma yet. We are waiting for an actual code implementation, not a nickname change. So if you change a car named "Buggati"(Gemma4) to "Lamborghini"(deepseek-v3.1-something model name) and painted it in "Lamborghini" style, the person(The thinking toggle button) who knowns to use Lamborghini will come to use because he is tricked but he will always failed at fake lamborghini style buggati as they are different to each other. Basic common sense.

<!-- gh-comment-id:4196991794 --> @techie-learner commented on GitHub (Apr 7, 2026): > Creating a fake deepseek-v3.1-something model doesn’t solve the problem with the gemma4 model. The button appeared, but it doesn’t work. (0.9.0 ollama version) @zamiere Obviously. Renaming a model doesn't rewrite its architecture. You just tricked the UI into showing a button that the backend doesn't know how to use for Gemma yet. We are waiting for an actual code implementation, not a nickname change. So if you change a car named "Buggati"(Gemma4) to "Lamborghini"(deepseek-v3.1-something model name) and painted it in "Lamborghini" style, the person(The thinking toggle button) who knowns to use Lamborghini will come to use because he is tricked but he will always failed at fake lamborghini style buggati as they are different to each other. Basic common sense.
Author
Owner

@techie-learner commented on GitHub (Apr 7, 2026):

This would really useful for the QWEN 3.5 models! :)

@Rastafabisch The logic we're discussing covers all models with thinking architectures. Once the PR is merged, it won't matter if it's Qwen, Gemma, or DeepSeek—the toggle will work for everything capable of reasoning. We're fixing the engine, not just one engine's piston that only support one model type.

<!-- gh-comment-id:4197020976 --> @techie-learner commented on GitHub (Apr 7, 2026): > This would really useful for the QWEN 3.5 models! :) @Rastafabisch The logic we're discussing covers all models with thinking architectures. Once the PR is merged, it won't matter if it's Qwen, Gemma, or DeepSeek—the toggle will work for everything capable of reasoning. We're fixing the engine, not just one engine's piston that only support one model type.
Author
Owner

@techie-learner commented on GitHub (Apr 13, 2026):

BUMP! It's a pain in the a to have loops of thinking from whatever model! PLEASE hear us! <3

@forbiddenPHP Bruh , bumping on a thread like little derps and making face like "<3" does not make you great, it makes you a egg with 5 sticks with "<3" fake that means too make you cute but makes you systematically downgraded dumb , you didn't start doesn't make you a polite and respectful users; it makes you a nuisance and mannerless derp. You spent the whole time shouting and throwing a tantrum for a toggle button you didn't even have the brain cells to help developers of Ollama team to understand the issue. You contributed exactly zero to the logic and 100% to the stupidity.. You aren't a contributor—you're just a loud glorified lagging beggar parasite that I'm tired of supporting. Go ahead, have some manners.

<!-- gh-comment-id:4236880060 --> @techie-learner commented on GitHub (Apr 13, 2026): > BUMP! It's a pain in the a to have loops of thinking from whatever model! PLEASE hear us! <3 @forbiddenPHP Bruh , bumping on a thread like little derps and making face like "<3" does not make you great, it makes you a egg with 5 sticks with "<3" fake that means too make you cute but makes you systematically downgraded dumb , you didn't start doesn't make you a polite and respectful users; it makes you a nuisance and mannerless derp. You spent the whole time shouting and throwing a tantrum for a toggle button you didn't even have the brain cells to help developers of Ollama team to understand the issue. You contributed exactly zero to the logic and 100% to the stupidity.. You aren't a contributor—you're just a loud glorified lagging beggar parasite that I'm tired of supporting. Go ahead, have some manners.
Author
Owner

@techie-learner commented on GitHub (Apr 13, 2026):

I second. Would be nice to have a button somewhere, in that default Ollama GUI, which I actually end up using a lot. (Course the GUI could also use better editing and chat management, but that's not as important as simply being able to disable thinking.)

Alternatively, doing it at the modelfile level would be acceptable. Being able to disable thinking, then /save that to a new modelfile, so we can just use that modelfile in the GUI or other purposes, with thinking disabled by default, would be even more useful.

It's pure comedy seeing this 'bug' report. While technical logic and image breakdowns were provided weeks ago, some were too busy 'seconding' and asking for GUI fluff like 'better editing' to notice the engine was heading for a crash.

Asking for a 'button somewhere' instead of understanding the backend architecture is why 0.20.6 is a disaster. Those who spent 3 weeks on a wish-list instead of reading the provided logic didn't help—they just added to the bloat. Now that you're forced back to 0.20.5, enjoy the downgrade; the logic provided here is as broken as the update itself.

<!-- gh-comment-id:4237168224 --> @techie-learner commented on GitHub (Apr 13, 2026): > I second. Would be nice to have a button somewhere, in that default Ollama GUI, which I actually end up using a lot. (Course the GUI could also use better editing and chat management, but that's not as important as simply being able to disable thinking.) > > Alternatively, doing it at the modelfile level would be acceptable. Being able to disable thinking, then /save that to a new modelfile, so we can just use that modelfile in the GUI or other purposes, with thinking disabled by default, would be even more useful. It's pure comedy seeing this 'bug' report. While technical logic and image breakdowns were provided weeks ago, some were too busy 'seconding' and asking for GUI fluff like 'better editing' to notice the engine was heading for a crash. Asking for a 'button somewhere' instead of understanding the backend architecture is why 0.20.6 is a disaster. Those who spent 3 weeks on a wish-list instead of reading the provided logic didn't help—they just added to the bloat. Now that you're forced back to 0.20.5, enjoy the downgrade; the logic provided here is as broken as the update itself.
Author
Owner

@techie-learner commented on GitHub (Apr 13, 2026):

@Nikorasu
It’s hilarious how you 'second' a request you clearly don't understand. Using phrases like 'I second' doesn't make you an engineer; it just makes you a parrot.

While you were busy wishing for 'better editing' and 'GUI fluff,' I was actually providing the logic for the "Thinking" toggle. You aren’t here to help; you’re just a bloated derp with a wish-list and zero technical contribution. You’re acting like a parasite—waiting for someone else to build the engine so you can steal the idea and complain about the paint job.

Enjoy the mess of 0.20.6. Some of us are here to build; you’re just here to be a notification-clutterer. Stay in the loop of your own nonsense, I’m moving on to actual code.

<!-- gh-comment-id:4238011400 --> @techie-learner commented on GitHub (Apr 13, 2026): @Nikorasu It’s hilarious how you 'second' a request you clearly don't understand. Using phrases like 'I second' doesn't make you an engineer; it just makes you a parrot. While you were busy wishing for 'better editing' and 'GUI fluff,' I was actually providing the logic for the "Thinking" toggle. You aren’t here to help; you’re just a bloated derp with a wish-list and zero technical contribution. You’re acting like a parasite—waiting for someone else to build the engine so you can steal the idea and complain about the paint job. Enjoy the mess of 0.20.6. Some of us are here to build; you’re just here to be a notification-clutterer. Stay in the loop of your own nonsense, I’m moving on to actual code.
Author
Owner

@techie-learner commented on GitHub (Apr 14, 2026):

@Nikorasu Bruh, it's actually impressive how you managed to turn a technical thread into a personal wishlist circus. While I was doing the architectural heavy lifting and building the foundation, you were just notification-cluttering with unnecessary talk. Your bio says you 'find your own way,' but your behavior proves you're just a logic thief—a total logic-leech trying to weaken the host of the thread just to feel relevant.

You didn't have the technical depth to contribute, so you resorted to begging and then tried to dump the guilt on the community when you got exposed? You never actually supported the work; you just liked the idea so you could attach your unnecessary wishlist to it. Even your own 'LiveWhisper' repo is just a 4-year-old collection of wrappers for other people's work—basic scripts that you’re still using to beg for Ko-fi donations?

Asking for coffee money when you can't even grasp the backend logic of a current thread is the ultimate 'Egg' move. See the reality now: you tried to take over a technical space you don't understand, and you got dismantled for justice. The thread is finally clean without your 'GUI fluff' noise and your compulsive begging.

<!-- gh-comment-id:4245208827 --> @techie-learner commented on GitHub (Apr 14, 2026): @Nikorasu Bruh, it's actually impressive how you managed to turn a technical thread into a personal wishlist circus. While I was doing the architectural heavy lifting and building the foundation, you were just notification-cluttering with unnecessary talk. Your bio says you 'find your own way,' but your behavior proves you're just a logic thief—a total logic-leech trying to weaken the host of the thread just to feel relevant. You didn't have the technical depth to contribute, so you resorted to begging and then tried to dump the guilt on the community when you got exposed? You never actually supported the work; you just liked the idea so you could attach your unnecessary wishlist to it. Even your own 'LiveWhisper' repo is just a 4-year-old collection of wrappers for other people's work—basic scripts that you’re still using to beg for Ko-fi donations? Asking for coffee money when you can't even grasp the backend logic of a current thread is the ultimate 'Egg' move. See the reality now: you tried to take over a technical space you don't understand, and you got dismantled for justice. The thread is finally clean without your 'GUI fluff' noise and your compulsive begging.
Author
Owner

@techie-learner commented on GitHub (Apr 16, 2026):

@dhirajlochib @rick-github

It’s truly impressive to watch the 0.20.6 disaster unfold in real-time. While you were busy 'viewing' the comments of Parrot-beggars and notification-clutterers, you ignored the architectural logic and photo evidence I provided weeks ago.

@dhirajlochib: Thinking Quantity = Quality is your first error. Submitting 7 PRs in 24 hours while most of them crash isn't 'learning'—it’s a Logic DDoS on the repository. Claiming a 'Two-file frontend change' while injecting a 23-file bloat-fest of 157 additions is pure System Dishonesty. You didn't fix the engine; you just spammed the UI with 'Spaghetti Code' and prayed the maintainers wouldn't notice the bloat. You’re like someone who paints a broken car and calls the engine 'server-driven.' The 'Hearts' you collected are just tokens for a logic-loop you didn't even write yourself. Status: 404 Logic Not Found.

@rick-github: Being a 'Collaborator' should mean maintaining code integrity, not just the size of your ego. You spent more time 'viewing' the comments of 'Stray Dog' beggars than you did fixing the Gemma4 and Qwen3 failures I documented on a silver platter. You act like a Senior Admin, but you’re managing the repo like a circus ringmaster—focusing on 'GUI fluff' while the backend is literally rotting. A real engineer respects the Root User (the Author); a Parrot-Manager just waits for the thread to crash so they can panic-release v0.20.7. Status: System Overheated by Ego.

The "Root User" Summary:
While the two of you were busy 'seconding' nonsense and hiding 157 lines of bloat, a teenager on an i3-2120 provided more architectural depth than your entire 'Pattern-driven' update. My 'Feature Request' was actually a request for you to install some Basic Human Features like logic and integrity. Enjoy your 'Hearts' and your 'Collaborator' badges—the rest of us will stick to Efficiency First while you guys finish drowning the repo in your own circus.

<!-- gh-comment-id:4260681754 --> @techie-learner commented on GitHub (Apr 16, 2026): @dhirajlochib @rick-github It’s truly impressive to watch the 0.20.6 disaster unfold in real-time. While you were busy 'viewing' the comments of Parrot-beggars and notification-clutterers, you ignored the architectural logic and photo evidence I provided weeks ago. @dhirajlochib: Thinking Quantity = Quality is your first error. Submitting 7 PRs in 24 hours while most of them crash isn't 'learning'—it’s a Logic DDoS on the repository. Claiming a 'Two-file frontend change' while injecting a 23-file bloat-fest of 157 additions is pure System Dishonesty. You didn't fix the engine; you just spammed the UI with 'Spaghetti Code' and prayed the maintainers wouldn't notice the bloat. You’re like someone who paints a broken car and calls the engine 'server-driven.' The 'Hearts' you collected are just tokens for a logic-loop you didn't even write yourself. Status: 404 Logic Not Found. @rick-github: Being a 'Collaborator' should mean maintaining code integrity, not just the size of your ego. You spent more time 'viewing' the comments of 'Stray Dog' beggars than you did fixing the Gemma4 and Qwen3 failures I documented on a silver platter. You act like a Senior Admin, but you’re managing the repo like a circus ringmaster—focusing on 'GUI fluff' while the backend is literally rotting. A real engineer respects the Root User (the Author); a Parrot-Manager just waits for the thread to crash so they can panic-release v0.20.7. Status: System Overheated by Ego. The "Root User" Summary: While the two of you were busy 'seconding' nonsense and hiding 157 lines of bloat, a teenager on an i3-2120 provided more architectural depth than your entire 'Pattern-driven' update. My 'Feature Request' was actually a request for you to install some Basic Human Features like logic and integrity. Enjoy your 'Hearts' and your 'Collaborator' badges—the rest of us will stick to Efficiency First while you guys finish drowning the repo in your own circus.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#34929