# New Release: CrewAI 1.1.0 is out! 🚨 **URL:** \ **Category:** Announcements\ **Created:** [October 22, 2025, 6:22pm UTC](https://community.crewai.com/t/new-release-crewai-1-1-0-is-out/7142 "2025-10-22T18:22:18Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Tony\_Wood](https://sea1.discourse-cdn.com/flex025/user_avatar/community.crewai.com/tony_wood/32/1876_2.png) [@Tony\_Wood](https://community.crewai.com/u/Tony_Wood)\ **Post date:** [October 22, 2025, 6:22pm UTC](https://community.crewai.com/t/new-release-crewai-1-1-0-is-out/7142/1 "2025-10-22T18:22:18Z")
CrewAI version 1.1.0 (released 2025-10-21) delivers key enhancements for language model integration, developer experience, and vector search capabilities. However, please note several unresolved high-severity bugs and known issues that may affect critical workflows. Here’s what you need to know: ## **Core Improvements & Fixes** - **Multi-provider Large Language Model (LLM) support** Now supports multiple LLM backends in `InternalInstructor` and related classes, letting you choose the best model for your needs. - **mypy plugin base and stricter typing** Improved static type checking makes code safer and easier to maintain, while surfacing parameter mismatches earlier. - **Template pinning** Prevents unintentional changes to task/agent templates by enabling version locking. - **Internal logging and tracing fixes** Fixes to logging/tracing make debugging more reliable; improves error tracking in complex workflows. - **Dependency fixes** **More core fixes and context:** - [CrewAI Issues Tracker](https://github.com/crewAIInc/crewAI/issues) * * * ## **New Features & Enhancements** - **Qdrant Vector Search Tool upgrades** Significant improvements to vector search and retrieval. However, be aware of reported [Qdrant regressions](https://github.com/crewAIInc/crewAI-tools/issues/478) (test before upgrading). - **Initial plugin framework** The new mypy-compatible base sets the stage for community-built plugins. - **Enhanced error surfacing (in progress)** Work to improve error message clarity and exception handling is ongoing, following [community requests](https://github.com/crewAIInc/crewAI/issues/3755). - **Better LLM integration options** Seamless switching between providers; updated guides for Azure, Bedrock, and OpenAI compatibility. **Still outstanding:** High-priority issues remain open for tool failures ([StageHand](https://github.com/crewAIInc/crewAI-tools/issues/412), TXTSearch), async deadlocks ([#3730](https://github.com/crewAIInc/crewAI/issues/3730)), memory management ([#3753](https://github.com/crewAIInc/crewAI/issues/3753)), and context window errors ([#3774](https://github.com/crewAIInc/crewAI/issues/3774)). - [Full list of open issues](https://github.com/crewAIInc/crewAI/issues) * * * ## **Documentation & Guides** - **LLM integration documentation updated** Step-by-step guidance for using multiple LLMs, with tips for dependency management and version safety. [Docs: LLM Integration](https://docs.crewai.com/integrations/) - **Upgrade notes and examples** Expanded guides and real-world walkthroughs for upgrading your CrewAI environment to 1.1.0, addressing breaking changes and workarounds. - **Known issues section** Documentation now flags memory reset, vector search, and tool/plugin errors with status and links to community-reported fixes.[Release FAQ](https://github.com/crewAIInc/crewAI/tree/1.1.0) - **Contribution guidance** How to propose or document new features, especially for integrations and LLM/provider support. **Gaps to note:** Some documentation (especially for tool compatibility and typical workflow breakages) lags behind v1.1.0 features and real-world issues. If you encounter undocumented blockers, please: - [Open a docs suggestion](https://github.com/crewAIInc/crewAI/discussions) - Share workarounds in [the CrewAI Forum](https://github.com/crewAIInc/crewAI/discussions) * * * **Community Insights** - Most requested: Fixes for memory reset failures, Qdrant/TXTSearch tool regressions, improved error messages, and more prompt updates to documentation. - Enterprise and advanced users value the expanded LLM/plugin support and static typing, but upgrade blocking bugs need rapid action. - Community collaboration is robust—your issue reports and shared workarounds are directly shaping CrewAI’s roadmap and support priorities. * * * **Action Steps for You** - Before upgrading, check the [open issues list](https://github.com/crewAIInc/crewAI/issues) for known blockers affecting your workflow. - Test CrewAI 1.1.0 in a safe environment, especially if you rely on Qdrant, TXTSearch, StageHand, or memory-intensive agents. - Share feedback, bug reports, or documentation needs in [CrewAI Issues](https://github.com/crewAIInc/crewAI/issues) or the [CrewAI Forum](https://github.com/crewAIInc/crewAI/discussions). - Suggest and vote on integration requests—community demand directly influences the roadmap. * * * Full release notes here: [https://github.com/crewAIInc/crewAI/releases](https://github.com/crewAIInc/crewAI/releases) Thank you for strengthening CrewAI! For ongoing support and to join the conversation, visit the [CrewAI Forum](https://github.com/crewAIInc/crewAI/discussions). _Release data and recommendations current as of 2025-10-22. Prepared for the CrewAI community by your analysis agent, synthesising the latest releases, docs, and real-time feedback._ ---
**Author:** ![Tony\_Wood](https://sea1.discourse-cdn.com/flex025/user_avatar/community.crewai.com/tony_wood/32/1876_2.png) [@Tony\_Wood](https://community.crewai.com/u/Tony_Wood)\ **Post date:** [October 22, 2025, 6:23pm UTC](https://community.crewai.com/t/new-release-crewai-1-1-0-is-out/7142/2 "2025-10-22T18:23:48Z")
# **[CrewAI Q3 2025]: Cross-Analysis of Releases, Issues & Community Feedback** _Prepared for CREWAI community practitioners, developers, and leadership. This report surfaces actionable patterns, direct linkages, and opportunities for improving both product and community experience, based on comprehensive release notes, GitHub issue tracking, the community forum, documentation, and blog highlights from 2025-08-22 to 2025-10-22._ * * * ## **Executive Summary** CrewAI v1.1.0 (released 2025-10-21) focuses on expanded Large Language Model (LLM) support, type-safety improvements, and upgraded vector search while preserving upgrade safety (no breaking changes). However, critical and high-severity bugs remain unresolved around tool failures, agent memory management, and dependency mismatches. Community engagement remains high, with clear requests for better documentation, enhanced error messages, and additional integrations. Collaboration and open issue reporting are helping to shape rapid iteration and evolving best practices. **Key insights:** - Memory management and tool integration bugs are the top blockers, overshadowing new features for some community members. - Static typing and multi-provider LLM support are well-received and signal CrewAI’s focus on enterprise and reliability use cases. - Critical upgrades to vector search (especially Qdrant) yielded new capabilities but introduced severe regressions affecting core workflows. - Documentation gaps and abrupt behaviour changes increase support load and slow onboarding for new users. * * * ## **1. What’s New & Changed: Major Releases** | **Version** | **Release Date** | **Major Additions & Fixes** | **Major Docs or Blog Highlights** | | --- | --- | --- | --- | | 1.1.0 | 2025-10-21 | - Multi-provider LLM support | | - mypy plugin base - QdrantVectorSearchTool improvements - Integration doc link fixes - Typed tracing/logging fixes - Template pinning | - LLM integration docs updated - Example-rich upgrade guidance | | 1.0.0 | 2025-10-20 | - Agent knowledge/guardrail improvements - Tool repo credential injection - Docker/cron fixes - Bug and doc cleanups | - Security policy update - Telemetry guides - Webhook parameter clarification | | (Pre-releases 1.0.0a4-1.0.0b3) | 2025-10-02—2025-10-18 | - SDK/Bedrock/Azure integrations - Guardrail/task validation - Async bus/thread-safe improvements - Tracing - Test/print parameter enhancements | - Tracing documentation - Braintrust/AMP docs - Feature request flow guidance | _Full changelog: [GitHub releases](https://github.com/crewAIInc/crewAI/releases)_ * * * ## **2. Top Issues & Community Pain-Points** **🟠 = Still open or recurring in support channels** | **Theme / Blocker** | **Raised In** | **Major Linked Issues/Threads** | **Resolution/Status** | | --- | --- | --- | --- | | Memory reset fails (readonly DB, agent knowledge) | GitHub | [#3753 crewAI](https://github.com/crewAIInc/crewAI/issues/3753) | 🟠 Critical, blocks resets | | Qdrant/TXT tool failures post-upgrade | GitHub | [#478](https://github.com/crewAIInc/crewAI-tools/issues/478), [#466](https://github.com/crewAIInc/crewAI-tools/issues/466) | 🟠 Open, high impact | | Import/module errors (PGSearch, litellm) | GitHub | [#3776 crewAI](https://github.com/crewAIInc/crewAI/issues/3776), [#3750 crewAI](https://github.com/crewAIInc/crewAI/issues/3750) | 🟠 High, unresolved | | Context window overrun crash | GitHub | [#3774 crewAI](https://github.com/crewAIInc/crewAI/issues/3774) | 🟠 Unhandled, open | | AsyncI/O deadlocks (ollama, asyncio) | GitHub | [#3730 crewAI](https://github.com/crewAIInc/crewAI/issues/3730) | 🟠 Widespread intermittence | | Local knowledge: auth errors (401) | GitHub/Forum | [#3764 crewAI](https://github.com/crewAIInc/crewAI/issues/3764) | 🟠 Still present | | StageHand tool error (blocks workflows) | GitHub | [#412 tools](https://github.com/crewAIInc/crewAI-tools/issues/412) | 🟠 Critical, not fixed | | Improved exception verbosity, API feature requests | GitHub | [#3755, #3744, #3739, #3735 crewAI](https://github.com/crewAIInc/crewAI/issues/) | 🟠 Requested, in backlog | | Documentation gaps for LLM/tooling integration | Forum, GitHub | Multiple open-for-comment threads | 🟠 Partial updates only | _Note: 🟠 = still a major irritant or unresolved for some user profiles._ * * * ## **3. Cross-System Patterns & Linking Table** ### **Key Cross-References** | **Product Change / Feature** | **Issue(s) Closed / Improved** | **Forum or Community Feedback** | **Docs / Blog Updates** | | --- | --- | --- | --- | | QdrantVectorSearchTool upgrades | [#478 Qdrant error](https://github.com/crewAIInc/crewAI-tools/issues/478) (regression reported, not closed) | Multiple high-urgency reports | Docs updated but workarounds/community guidance still needed | | LLM multi-provider in InternalInstructor | Dependency/compat breakages ([#3750](https://github.com/crewAIInc/crewAI/issues/3750)), litellm issue | New integration requests, confusion on version matching | Integration docs updated for v1.1.0 | | Typed plugin & typing improvements | Better type safety, but led to stricter validation in model parameters ([#466](https://github.com/crewAIInc/crewAI-tools/issues/466)) | Forum requests for detail/examples | API usage illustrated in new examples | | Agent memory reset/refactor | [#3753 critical bug](https://github.com/crewAIInc/crewAI/issues/3753) | User reports of stuck/blocked agent resets | Known issue warning section pending in docs | | Workflow enhancements (StageHand, task guardrail) | [#412 StageHand bug](https://github.com/crewAIInc/crewAI-tools/issues/412) | Slowed adoption of new features in production | Issue acknowledged, with workarounds in select blog threads | | Airweave Tool, fastAPI requests | [#482 tools](https://github.com/crewAIInc/crewAI-tools/issues/482), [#3739 core](https://github.com/crewAIInc/crewAI/issues/3739) | Popular request threads | Future roadmap mention, not yet in documentation | **Pattern:** High-value enhancements have often triggered regressions or stricter validation/failure cases, with the community surfacing specific workflows where “upgrade breaks what worked yesterday.” Forum participation is robust, usually leading to clarified documentation or acknowledged bugs rather than immediate fixes. Workarounds are widely shared peer-to-peer. * * * ## **4. Trends & Relationships** - Major new features (multi-provider LLM, plugin base, vector search tool) have run in parallel with persistent high/critical bugs. - Update cycles have improved core architectural reliability (mypy, strict typing), but have increased UX hurdles for existing users due to tighter validation and module dependencies. - Community focus has shifted toward reliability and workflow unblockers rather than pure feature-speed; documentation and error-message clarity are high priorities. - New integrations (Airweave tool, fastAPI, enhanced Pydantic output) gain immediate upvotes when proposed, indicating broad interest in ecosystem expansion. - Documentation refreshes lag slightly behind feature rollouts, causing friction for those upgrading in real-world environments. * * * ## **5. FAQs (Frequently Asked Questions)** **Q1: Why does my tool/agent fail with a “readonly database” or memory reset error?** [crewAIInc/crewAI issue #3753](https://github.com/crewAIInc/crewAI/issues/3753) covers a current critical bug: memory reset and agent knowledge commands may attempt to write to a database instance in read-only mode. This is under urgent review. Monitor the issue for workarounds and, where appropriate, avoid using agent-wide reset until resolved. **Q2: Can I use multiple LLM providers with CrewAI 1.1.0?** Yes, v1.1.0’s InternalInstructor and integration classes explicitly support multiple LLM backends. Check updated integration docs and ensure all dependencies (notably `litellm` and provider-specific SDKs) are installed at matching versions. **Q3: Why does QdrantVectorSearchTool or TXTSearchTool break after upgrade?** Upgrades improved vector search, but several compatibility issues were reported ([Qdrant #478](https://github.com/crewAIInc/crewAI-tools/issues/478), [TXTSearch #466](https://github.com/crewAIInc/crewAI-tools/issues/466)). Review the linked issues and test upgrades in isolated environments; revert tool/plugin versions where needed until resolved. * * * ## **6. Data Matrices & References** #### **GitHub Issues: Status Table** | **Type** | **Total** | **Open** | **Closed** | **Blockers\*** | | --- | --- | --- | --- | --- | | Bugs | 13 | 13 | 0 | 8 | | Enhancements | 6 | 6 | 0 | 0 | | Docs | 4 | 4 | 0 | 0 | | Task/Other | 2 | 2 | 0 | 0 | | **Total:** | 25 | 25 | 0 | 8 | \*Blockers/high-priority: - [StageHand tool error (tools #412)](https://github.com/crewAIInc/crewAI-tools/issues/412) - [Failed memory reset (core #3753)](https://github.com/crewAIInc/crewAI/issues/3753) - [Qdrant\_Search\_Tool retrieval (tools #478)](https://github.com/crewAIInc/crewAI-tools/issues/478) - [TXTSearchTool failure (tools #466)](https://github.com/crewAIInc/crewAI-tools/issues/466) - [PGSearchtool import error (core #3776)](https://github.com/crewAIInc/crewAI/issues/3776) - [litellm missing after upgrade (core #3750)](https://github.com/crewAIInc/crewAI/issues/3750) - [crew hanging on asyncio/local ollama (core #3730)](https://github.com/crewAIInc/crewAI/issues/3730) - [SystemExit/context window bug (core #3774)](https://github.com/crewAIInc/crewAI/issues/3774) **Online Resources:** - [CrewAI Issues](https://github.com/crewAIInc/crewAI/issues) - [CrewAI Tools Issues](https://github.com/crewAIInc/crewAI-tools/issues) - [Documentation](https://docs.crewai.com/) - [Release Notes](https://github.com/crewAIInc/crewAI/releases) * * * ## **7. Recommendations & Next Steps** ### **For the Team:** - **Prioritise hotfixes** for agent memory resets, tool/plugin breakages (Qdrant, TXTSearch, StageHand), and critical authentication errors to reduce downtime. - **Establish version compatibility matrices** for all plugins/integrations (LLM, vector search, FastAPI, etc.), and publish clear “safe upgrade” guides ahead of future releases. - **Expand test coverage** for edge cases surfaced by high-severity user reports (e.g. read-only DBs, SystemExit, dependency mismatches). - **Proactively communicate workarounds** and “known issues” in both documentation and blog posts to shorten resolution lag for active users, especially around tool and agent reset problems. ### **For Community Members:** - **Check open issue trackers** ([core](https://github.com/crewAIInc/crewAI/issues), [tools](https://github.com/crewAIInc/crewAI-tools/issues)) for affected bug reports or feature proposals before upgrading or deploying v1.1.0 in critical environments. - **Test upgrades in isolation** and document all breakages/recoveries to assist maintainers and peers; share your workaround steps in relevant threads. - **Suggest and upvote feature requests** (especially for integrations and exception clarity)—maintainers have responded quickly around real-world pain-point themes. - **Contribute to documentation** by submitting pull requests or topic suggestions for missing/unclear areas—especially for LLM, tools, and agent edge cases. * * * ❤ Thank you for shaping CrewAI’s future. For the latest support and to contribute a solution, join [CrewAI Forum](https://github.com/crewAIInc/crewAI/discussions) and keep building! * * * **Legend** : 🟠 = Recurring or still open ✅ = Closed/resolved Release/data as of 2025-10-22. For feedback or clarification, reply in the next community sync or open a thread. * * * _Prepared by CREWAI community analysis agent based on online releases, GitHub issues, documentation, community threads, and official blog posts, 2025-08-22 to 2025-10-22._