Gemini
Gemini stops watching video frame by frame and starts deciding what to watch.
A side-by-side editorial comparison of Jan and Ollama — release velocity, themes, recent moves, and the top alternatives to consider.
Jan is quietly wiring subagents into the same tool pipeline its main agent uses.
Jan's tagged releases in this window are small: a persisted chain-of-thought duration, a CSP fix that unblocks video uploads, and a change to llama.cpp defaults that turns auto-fit off and pins context length to 8192. Cadence is slow — four tags spanning May to July. The most recent tag is not a release at all but a development checkpoint.
Ollama becomes a gateway provider for Claude Desktop — and this feed missed the release that says so.
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.
Jan's tagged releases in this window are small: a persisted chain-of-thought duration, a CSP fix that unblocks video uploads, and a change to llama.cpp defaults that turns auto-fit off and pins context length to 8192. Cadence is slow — four tags spanning May to July. The most recent tag is not a release at all but a development checkpoint.
That checkpoint is the informative one: subagents now reuse the main native tool pipeline rather than a separate path, alongside code-UI work. Jan is consolidating on one tool-calling surface for both the primary agent and its subagents, which is the precondition for multi-agent workflows inside a local desktop app. The shipped releases meanwhile read as stabilization of the chat surface — durable metadata, predictable inference defaults.
The subagent and code-UI work visible in the checkpoint tags should surface in the next minor release; on this cadence, expect more 0.8 stabilization patches before it does.
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.
Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Jan or Ollama.
Gemini stops watching video frame by frame and starts deciding what to watch.
Qodo is arguing that AI code review needs governance, not better instruction files
D-ID's feed is a content-marketing engine, not a changelog
Pictory publishes daily search content, not a changelog.
The Agents window now opens without a GitHub sign-in, if you bring an Anthropic key.
The OSS terms change takes effect today, under a steady drumbeat of agent-memory explainers.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Jan and Ollama are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jan and Ollama are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top Jan alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Jan alternatives" section above for the current picks, or visit /alternatives/jan for the full list with editorial commentary on each.
Top Ollama alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Ollama alternatives" section above for the current picks, or visit /alternatives/ollama for the full list with editorial commentary on each.