Semantic Kernel vs OpenAI
Side-by-side trajectory, velocity, and editorial themes.
Semantic Kernel READMEs now name a successor — Microsoft Agent Framework is the next stop.
Semantic Kernel's most recent Python release (1.42.0) added an explicit 'Microsoft Agent Framework successor callout' to the READMEs — Microsoft is publicly pointing users toward a different framework as the forward path. The rest of the recent cadence is consistent with a project in late-stage maintenance: security hardening (path validation in CloudDrivePlugin, gRPC plugin, OpenAPI plugin; SQL escaping in connectors; Snappier and Kiota vulnerability bumps), dependency bumps via dependabot, vector-store connector polish, and small prompt-template fixes. Feature additions are narrow — ImageContent in tool/function results, OpenAI text-to-image model support, prompt template serialization improvements.
The project is transitioning from active framework to maintained predecessor. Microsoft's agent stack is consolidating under the new Microsoft Agent Framework banner, and Semantic Kernel is shifting into security-and-deps mode — the kind of release pattern you see when a team is keeping production users safe while migration paths are being built elsewhere. Read in parallel with the eight-month silence at AutoGen, the picture is clear: Microsoft is collapsing three previous agent-framework efforts (SK, AutoGen, Semantic Workbench) toward one supported runtime.
Expect SK to stay on a security-and-deps cadence for at least another two quarters, with a hard deprecation timeline likely announced once Microsoft Agent Framework has feature parity. Anyone building net-new on Semantic Kernel today should plan a migration; existing deployments are safe for the moment but on borrowed roadmap time.
Codex everywhere, sovereign-AI deals, and a math proof — OpenAI is pushing on all fronts at once.
OpenAI is operating on three simultaneous fronts: Codex distribution into enterprise (Dell on-premise, Databricks, Ramp case studies, role-specific playbooks for data science and ops), country-level deployment deals (Singapore, Malta, the broader Education for Countries program), and frontier research signaling (a model disproving a long-standing discrete-geometry conjecture). Underpinning all of it is GPT-5.5, which is now the named model behind the agent and Codex workloads. Trust infrastructure — Content Credentials, SynthID, a public verification tool — is being shipped alongside the expansion.
The product surface is shifting from a single chat product to a distribution layer: Codex is being placed inside customer infrastructure (Dell hybrid, Databricks notebooks) and inside countries (national ChatGPT Plus access, training programs). The customer-story cadence around Codex suggests OpenAI is moving from 'try the API' to documented vertical use cases — code review, RCA briefs, leadership memos — that map to org-chart roles rather than developer personas. Provenance work and the research milestone are doing different jobs in parallel: one defends against regulatory pressure, the other resets the ceiling on what 'frontier' means.
Expect more country-level rollouts on the Malta/Singapore template, and Codex packaging that targets specific corporate functions (finance, legal, ops) with pre-baked deliverables rather than raw model access. The next visible move is likely a Codex SKU with deeper enterprise data-residency controls — Dell paved the surface, the SKU follows.
See more alternatives to Semantic Kernel →
See more alternatives to OpenAI →