Goose
Goose's tracked feed is GDK alpha tags with no notes, so the agent itself isn't visible here.
A side-by-side editorial comparison of Continue and Ollama — release velocity, themes, recent moves, and the top alternatives to consider.
Continue ships a 'final release' of its VS Code extension and stops shipping notes after it.
In mid-June Continue cut what it calls the final stable release of its VS Code extension: it removed the CLI-install banner and Generate Rule, moved onboarding and new configs to explicit model definitions instead of Hub slugs, and updated a deprecation banner's export link. Two bare 2.0.0 and 2.1.0 tags followed with no notes.
Ollama starts v0.40.7 candidates by trimming duplicate CUDA libraries from the MLX package.
Ollama has moved to v0.40.7 release candidates. rc1 is packaging work: CUDA libraries shared by the GGML and MLX backends now ship once, in the CUDA payload, with release checks for the dependencies. The v0.40.6 candidates fixed model pulls behind proxies and gave --ask mode stable question ids, and v0.40.5 added Nemotron 3.5 Super on MLX and broader NVFP4 imports.
In mid-June Continue cut what it calls the final stable release of its VS Code extension: it removed the CLI-install banner and Generate Rule, moved onboarding and new configs to explicit model definitions instead of Hub slugs, and updated a deprecation banner's export link. Two bare 2.0.0 and 2.1.0 tags followed with no notes.
Through March the extension was in ordinary maintenance: JetBrains freeze fixes, dependency bumps, .continue/configs support and workspace-scoped history. June turns that into a wind-down, stripping Hub-dependent paths and pointing users at an export. The 2.x tags look like version housekeeping rather than a revival, because they carry no user-facing notes.
Expect few or no annotated extension releases from here. Whether the 2.x line carries real work is unclear until a 2.x release ships with notes.
Ollama has moved to v0.40.7 release candidates. rc1 is packaging work: CUDA libraries shared by the GGML and MLX backends now ship once, in the CUDA payload, with release checks for the dependencies. The v0.40.6 candidates fixed model pulls behind proxies and gave --ask mode stable question ids, and v0.40.5 added Nemotron 3.5 Super on MLX and broader NVFP4 imports.
MLX remains where new model families land first, and it is now being folded into the same CUDA distribution as GGML rather than shipping its own copy. Download, CLI and packaging plumbing are getting most of the attention between model additions, while the launch command is gradually tied to paid usage credits.
Expect stables for v0.40.4 through v0.40.7 to consolidate the Nemotron, Kev, proxy and packaging work. The entries don't show what the next model addition will be.
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 Continue or Ollama.
Goose's tracked feed is GDK alpha tags with no notes, so the agent itself isn't visible here.
Tabby's only visible release is an internal alpha with no notes; there is little to read yet.
opencode retires its separate beta repo as V2 becomes the main line.
Copilot gives enterprises an API to control which models their teams can use.
LobeHub's second v2.2.21 canary makes goals plan their own batches and queues steering server-side.
InvokeAI 7 alpha 3 turns boards into shared, role-gated spaces and adds Qwen-Image-2.1.
See all Continue alternatives → · See all Ollama alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Ollama is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Ollama is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top Continue alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Continue alternatives" section above for the current picks, or visit /alternatives/continue 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.