AutoGen vs Spinach
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.
Filling out the meeting-transcript-to-AI-agent integration matrix, one connector at a time.
Spinach is publishing a tightly coordinated content matrix: how to pipe Zoom, Google Meet, and Microsoft Teams transcripts into every major AI workspace and dev tool. Two date clusters dominate — five posts on April 24 and five more on May 1 — each running the same template across a different combination of source meeting platform and destination agent (Claude Code, Claude Cowork, Codex, Glean, Notion AI, HubSpot, Linear).
Spinach is repositioning from "AI meeting assistant" to "transcript pipeline for the rest of your AI stack," with its MCP server as the underlying connective tissue. The choice of destinations is telling — heavy emphasis on engineering tooling (Claude Code, Codex, Linear) suggests the GTM is moving toward technical buyers rather than the original ops/PM audience.
Expect more matrix entries — Cursor, Devin, JetBrains AI, ChatGPT desktop, Salesforce — published in fast batches. A consolidated "integrations directory" or marketplace page is the natural next visible artifact.
See more alternatives to AutoGen →
See more alternatives to Spinach →