AutoGen vs OpenRouter
Side-by-side trajectory, velocity, and editorial themes.
AutoGen has gone quiet — last release was September 2025, with no public update for nearly eight months.
AutoGen's most recent release is python-v0.7.5 on 2025-09-30. The last sustained activity came in a Q3 2025 cluster: v0.7.0 through v0.7.5, with v0.7.1 introducing nested Teams as group-chat participants, RedisMemory, latest MCP version, and OpenAIAgent built-in tools. v0.7.2 made DockerCommandLineCodeExecutor the default for MagenticOne and added an approval_func to CodeExecutorAgent. After that, the cadence stops cold — eight months of public silence as of May 2026.
The technical arc through July–September 2025 was clear: deeper team composition (teams-as-tools, teams-as-participants), better memory (RedisMemory, GraphFlow state retention across resumes), and an MCP-aligned tool surface. Then nothing. For a Microsoft research project in the agent-framework space, an eight-month gap during the most competitive period in agent tooling (LangGraph, OpenAI Agents SDK, Anthropic's Claude Agent SDK, Semantic Kernel agent expansions) is not normal silence — the absence is the signal. Without a release or public roadmap statement, this reads as either pre-major-rewrite mode or quiet wind-down/absorption into another Microsoft framework.
If there is no release within the next quarter, treat AutoGen as effectively frozen for production use; the agentic framework ecosystem has moved without it. If a release does land, expect it to be a structural rewrite tied to Semantic Kernel or a Microsoft-wide agent surface rather than continuation of the 0.7.x line.
OpenRouter is becoming a full agent platform, not just a model router.
OpenRouter has rolled out an Agent SDK, universal web search and fetch for any tool-calling model, dedicated audio APIs for TTS and transcription, and a response cache that drops cost to zero on repeat requests. It is also publishing pricing analyses that benchmark frontier-model cost shifts. The April-30 'release spotlight' frames the past month as a multi-product push rather than incremental shipping.
The product is moving up the stack from per-token model routing toward an opinionated developer surface — tool use, caching, multi-modality, account provisioning via CLI — so that an agent built on OpenRouter does not need separate vendors for search, audio, or workflow scaffolding. The Stripe-driven CLI signup hints that agents themselves are now an addressable customer.
Next likely move is expanding the Agent SDK with shared evaluation and traces across providers, plus deeper caching primitives — turning model-routing economics into a real switching argument against single-provider SDKs.
See more alternatives to AutoGen →
See more alternatives to OpenRouter →