DocsBot AI
Evaluation content dominates a feed whose real move was handing agents the admin panel
A side-by-side editorial comparison of Recall and Semantic Kernel — release velocity, themes, recent moves, and the top alternatives to consider.
Handwriting and screenshots become searchable cards, and the extension reaches Safari
Recall's August release is the broadest in months. OCR turns photos, screenshots and handwritten notes into real cards; the browser extension now runs on Safari and Edge alongside Chrome and Firefox, with connection editing inside the extension; chat proposes questions drawn from the saved library; and content can be added ten URLs at a time or by drag and drop. This follows a July that moved search into the full library page with text and AI modes searching reader content, notes and quizzes rather than titles.
Semantic Kernel's releases are now dependency bumps and redirect READMEs pointing users elsewhere.
The .NET and Python packages ship on a steady cadence, but the contents are servicing: SDK and package version bumps, CVE-driven dependency updates, CodeQL suppressions, and HTTP hardening such as disabling automatic redirects in the web plugins. The genuinely functional changes are narrow — a Gemini connector now honoring the configured function choice behavior, an MCP tool approval callback for Azure AI agents shipped as a breaking change, and MCP tools with colliding normalized names being skipped. The latest .NET release removes migrated vector-store providers outright, leaving redirect READMEs behind.
Recall's August release is the broadest in months. OCR turns photos, screenshots and handwritten notes into real cards; the browser extension now runs on Safari and Edge alongside Chrome and Firefox, with connection editing inside the extension; chat proposes questions drawn from the saved library; and content can be added ten URLs at a time or by drag and drop. This follows a July that moved search into the full library page with text and AI modes searching reader content, notes and quizzes rather than titles.
Two threads have been converging all summer. One widens what can enter the library — social posts, Apple News, text and Markdown files, and now anything a camera can photograph. The other makes what is already inside retrievable: full-content search, personas, cross-card chat, and now suggested questions. OCR closes the last major gap on the input side, since paper was the one source that could not get in.
The mobile search overhaul is explicitly promised and is the most likely next release. Suggested questions plus full-content search point toward retrieval quality inside chat becoming the next area of investment.
The .NET and Python packages ship on a steady cadence, but the contents are servicing: SDK and package version bumps, CVE-driven dependency updates, CodeQL suppressions, and HTTP hardening such as disabling automatic redirects in the web plugins. The genuinely functional changes are narrow — a Gemini connector now honoring the configured function choice behavior, an MCP tool approval callback for Azure AI agents shipped as a breaking change, and MCP tools with colliding normalized names being skipped. The latest .NET release removes migrated vector-store providers outright, leaving redirect READMEs behind.
The centre of gravity is moving out of this repository. Vector store providers have migrated to CommunityToolkit packages and their originals are now deleted rather than deprecated, with samples following them across. What remains is maintenance plus the occasional MCP fix, which suggests the agent work that would once have landed here is happening in a different codebase. For teams with Semantic Kernel in production, the signal to read is the removals: each one is a dependency that now resolves somewhere else.
Expect the cadence to continue as security and dependency servicing with occasional MCP fixes, and for migration tooling or documentation pointing at Microsoft Agent Framework to grow faster than any new capability in Semantic Kernel itself.
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 Recall or Semantic Kernel.
Evaluation content dominates a feed whose real move was handing agents the admin panel
A release train of small runtime wins between model drops
ClearML is filling in the hyperdataset lifecycle while hardening the SDK against what it loads.
Baseten is selling to the labs that build models, not just the developers who call them.
Between a BTS tie-in and free student plans, Gemini quietly moves into a Waymo
Perplexity is selling access to other people's models, and now repricing them weekly.
See all Recall alternatives → · See all Semantic Kernel alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Recall is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Recall is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 Recall alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Recall alternatives" section above for the current picks, or visit /alternatives/getrecall for the full list with editorial commentary on each.
Top Semantic Kernel alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Semantic Kernel alternatives" section above for the current picks, or visit /alternatives/semantic-kernel for the full list with editorial commentary on each.