Ollama vs tl;dv

This feed carries only release-candidate tags, and the last three shipped releases are absent from it: v0.33.0 (21 August), v0.33.1 (26 August) and v0.33.2 (27 August) are all live on GitHub and none was crawled. That matters because v0.33.0 is where the direction is stated — Claude Desktop can be configured to use Ollama as a third-party gateway provider — alongside a substantial prefill-caching correctness pass: cancelled prefills now keep every restore point they crossed, restore points no longer claim coverage they lack, and Claude Code's token-countdown system message was disabled because Ollama moved it to the front of the prompt and broke the KV cache on every request. The rc tags visible here carry only commit subjects, so what is stored is the shape of the work, not its substance.

Ollama has moved from a runtime you call to the place a user's local and cloud models are organised for other clients to consume, and the gateway-provider framing in v0.33.0 is the clearest statement of it so far. The caching work points the same way: the bugs being fixed are the ones that only appear when a long-running agent client sits on top, cancelling and retrying prefills. Underneath, the MLX backend keeps gaining models and structured output support. Treat any read of this product from the feed alone as partial until the release entries are crawled.

The three missing GA releases are the immediate gap, and until the crawler picks up the releases rather than the rc tags this feed will keep describing 0.33 as unreleased. On the product itself, the gateway work suggests further client configurations rather than depth on Claude Desktop alone.