n8n shipped [email protected] on 2026-09-29: Agents enabled by default (#39312); AI Agent Tool can use its own tools under a pre-v3 parent agent (#39160); MCP Client terminates sessions before close, MCP Registry flag removed from AI Assistant, editor adds Mistral Vibe to MCP picker; Azure OpenAI Chat Model renamed Azure AI Foundry with project/deployment listing and Entra app sign-in; plus shared Agent context and Agent Builder UX polish.
Key Takeaways
- ✓Release [email protected] on 2026-09-29; compare 2.41.0...2.42.0
- ✓Agents enabled by default (#39312); shared Agent context (#38930)
- ✓AI Agent Tool nests its own tools under pre-v3 parents (#39160)
- ✓MCP: terminate session on client close; Registry ungated in AI Assistant; Mistral Vibe in MCP picker
- ✓Azure OpenAI node renamed Azure AI Foundry Chat Model; docs AI Agents
Finished reading? Explore benchmark rankings & pricing
Real-world SWE-bench scores & $20/mo vs API cost break-even calculator
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background
Embedding LLM agents in low-code workflows often stalls on feature flags, nested AI Agent Tools losing their tools under older parents, and MCP session/registry friction. Azure naming (OpenAI vs AI Foundry) also confuses credentials.
What shipped
[email protected] enables Agents by default (#39312), adds shared Agent context (#38930), lets AI Agent Tools use their own tools under pre-v3 parents (#39160), hardens MCP client teardown/registry UX (incl. Mistral Vibe), and renames Azure OpenAI Chat Model to Azure AI Foundry Chat Model with project/deployment listing and Entra app sign-in.
Benchmarks
No public agent leaderboard in the notes. Regression-test nested tools and MCP session cleanup on your workflows.
Get started
Upgrade to 2.42.0; read AI Agents and the Agent node docs. Full diff: 2.41.0...2.42.0.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.