Semantic Kernel vs Recall
Side-by-side trajectory, velocity, and editorial themes.
Semantic Kernel ships steady .NET/Python point releases while pointing users to its successor framework.
Microsoft's Semantic Kernel releases as parallel per-language package trains (.NET and Python), each a mix of dependency bumps, security hardening, and occasional real capability work. Recent notes add HTTP-redirect disabling and file-path validation hardening on .NET, OpenAPI parsing and server-URL validation changes, and Assistant-agent function-choice support on Python. Several release notes carry a documented callout naming the Microsoft Agent Framework as SK's successor.
The engineering signal is maintenance-plus: dependency currency, security tightening, and API refinement rather than large new capability surfaces. The more consequential thread is positional — SK is steering developers toward the Microsoft Agent Framework, which frames this train as stabilization of an established codebase rather than expansion.
Expect continued incremental point releases focused on security, dependency updates, and OpenAPI/agent API polish, alongside more explicit migration signposting toward the Agent Framework.
After Recall 2.0, the second-brain iterates fast on sources, voice, and control
Since April's Recall 2.0 relaunch — agentic chat, an API and MCP, and the Max tier — the product has been in rapid iteration. It has widened what it can ingest (Instagram, LinkedIn, Apple News, text/Markdown), added Listen Mode voice playback, and now Custom Personas that pin how the AI behaves. The consistent thesis is knowledge-first AI: your saved sources come before the open web.
Recall is layering reach and control onto its chat: more sources in, more ways to steer the AI (personas, multi-step actions), and more model choice (Opus 4.8, GPT-5.5). Release notes point toward public profiles, sharing, and a write API as the next expansion beyond personal capture.
Based on the roadmap notes threaded through these releases, expect public Recall profiles and shared collections, plus a write/bulk-ingest API, to be the next headline moves.
See more alternatives to Semantic Kernel →
See more alternatives to Recall →