marius851000 65107c90b1 ollama: Fix thinking being also sent as content (#55540) ... "msg.string_contents();" return more than just content. It also return tool result (which need special handling, and should be emitted from the tool role) and thinking (which need already implemented special handling). This resulted in thinking being sent as content, which apparently ollama’s gemma4 parser didn’t handled well, and caused a number of issue that manifested by 1. outputting end of though token where unappropriate and 2. repeating things endlessly Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [ ] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) (no UI/UX impact) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable (a quick review, without benchmark, show that this should be at least as fast as the previous code. This is called only exceptionally anyway.) Closes #55537 Release Notes: - Fixed "thinking" text being badly formatted when sent to Ollama		2026-05-06 13:03:00 +00:00
..
src	ollama: Fix thinking being also sent as content (#55540)	2026-05-06 13:03:00 +00:00
Cargo.toml	cloud: Fix incorrect model getting selected at startup (#55325)	2026-05-04 07:52:37 +00:00
LICENSE-GPL