Recall
Post-2.0, Recall broadens what it captures while building a map for how people actually use it
A side-by-side editorial comparison of Jan and Sourcegraph — release velocity, themes, recent moves, and the top alternatives to consider.
Jan ships sparse, low-level fixes — CSP and context-length defaults in a thin crawl window
Only two changelog entries are crawled for Jan, both small engineering fixes: a CSP change to let video uploads load and a llama.cpp default change disabling context auto-fit. The thin feed limits what can be inferred — these are maintenance commits, not feature direction. The sparse window may itself reflect a crawl-coverage gap rather than a genuinely quiet product.
Sourcegraph turns code search into the substrate for agents that migrate whole repo fleets.
Sourcegraph is still a code-search and intelligence platform, but its published output is now almost entirely about AI agents operating across large codebases: migrations, security triage, and codebase comprehension. The one shipped product move in this window, Agentic Batch Changes in public beta, is the clearest signal of where the company is actually investing. Much of the rest is engineering-blog and marketing content rather than release notes.
Only two changelog entries are crawled for Jan, both small engineering fixes: a CSP change to let video uploads load and a llama.cpp default change disabling context auto-fit. The thin feed limits what can be inferred — these are maintenance commits, not feature direction. The sparse window may itself reflect a crawl-coverage gap rather than a genuinely quiet product.
On the visible evidence, work is at the plumbing layer: content-security policy correctness and local-inference defaults. Whether Jan is shipping larger features that aren't being captured can't be determined from two entries; the crawl coverage is worth checking.
Hard to predict from two low-level fixes; the safe read is continued llama.cpp default-tuning and bug fixes unless richer release notes surface.
Sourcegraph is still a code-search and intelligence platform, but its published output is now almost entirely about AI agents operating across large codebases: migrations, security triage, and codebase comprehension. The one shipped product move in this window, Agentic Batch Changes in public beta, is the clearest signal of where the company is actually investing. Much of the rest is engineering-blog and marketing content rather than release notes.
The throughline is agents that see and act on an entire codebase at once, not a single file: batch migrations across hundreds of repos, automated security triage from webhook to PR, and MCP-fed context for external coding agents. Sourcegraph is positioning its index as the memory layer that makes those agents effective where they otherwise stall. The search product is increasingly framed as agent infrastructure.
The most likely next move is Agentic Batch Changes graduating from public beta toward general availability, with tighter MCP integration so third-party agents lean on Sourcegraph's index. Beyond that the feed is mostly editorial, so roadmap specifics past Batch Changes aren't clear.
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 Sourcegraph.
Post-2.0, Recall broadens what it captures while building a map for how people actually use it
The model zoo is quietly rebuilding itself into the backend every inference engine targets.
Airparser's tracked feed is a content-marketing engine, not a product changelog.
Botsify's feed is all SEO blog content — no product releases surface here.
The Anthropic TypeScript SDK is racing to expose a wave of new agent-oriented API primitives
OpenHands Cloud is in enterprise-hardening mode, shipping org, budget and observability plumbing daily
See all Jan alternatives → · See all Sourcegraph alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sourcegraph is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. Sourcegraph is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 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 Sourcegraph alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Sourcegraph alternatives" section above for the current picks, or visit /alternatives/sourcegraph for the full list with editorial commentary on each.