1.14.4a2

CrewAI Releases / 4/30/2026

📰 NewsDeveloper Stack & InfrastructureTools & Practical UsageModels & Research

共有:

Key Points

The release adds support for using a custom persistence key in crewAI’s flow feature, improving how state is stored and retrieved.
It fixes LLM handling by ensuring validated message variables are used in non-streaming request handlers.
The update extends Azure support by adding Responses API compatibility for the Azure OpenAI provider.
It improves MCP integration reliability by warning and returning an empty result when a native MCP server provides no tools.
Overall, this version focuses on interoperability and correctness across multiple AI integration points (LLM flows, Azure APIs, and MCP tooling).

feat(flow): support custom persistence key in @persist by @lucasgomide in #5649
fix(llm): use validated messages variable in non-streaming handlers by @greysonlalonde in #5655
feat(azure): add Responses API support for Azure OpenAI provider by @kunalk16 in #5201
fix(mcp): warn and return empty when native MCP server returns no tools by @greysonlalonde in #5657
fix(instructor): forward base_url and api_key to instructor.from_provider by @greysonlalonde in #5658
feat(azure): forward credential_scopes to Azure AI Inference client by @mattatcha in #5661

Full Changelog: 1.14.4a1...1.14.4a2

AI Business

Mistral AI Blog

Dev.to

Dev.to

LangChain Releases