Homepage ยท Docs ยท Start Cloud Trial ยท Blog ยท Forum
crewAI
Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.
Description
Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.
README
CrewAI is a lean, lightning-fast Python framework built entirely from scratchโcompletely independent of LangChain or other agent frameworks. It empowers developers with both high-level simplicity and precise low-level control, ideal for creating autonomous AI agents tailored to any scenario.
- CrewAI Crews: Optimize for autonomy and collaborative intelligence.
- CrewAI Flows: The enterprise and production architecture for building and deploying multi-agent systems. Enable granular, event-driven control, single LLM calls for precise task orchestration and supports Crews natively
With over 100,000 developers certified through our community courses at learn.crewai.com, CrewAI is rapidly becoming the standard for enterprise-ready AI automation.
CrewAI AMP Suite is a comprehensive bundle tailored for organizations that require secure, scalable, and easy-to-manage agent-driven automation.
You can try one part of the suite the Crew Control Plane for free
- Tracing & Observability: Monitor and track your AI agents and workflows in real-time, including metrics, logs, and traces.
- Unified Control Plane: A centralized platform for managing, monitoring, and scaling your AI agents and workflows.
- Seamless Integrations: Easily connect with existing enterprise systems, data sources, and cloud infrastructure.
- Advanced Security: Built-in robust security and compliance measures ensuring safe deployment and management.
- Actionable Insights: Real-time analytics and reporting to optimize performance and decision-making.
- 24/7 Support: Dedicated enterprise support to ensure uninterrupted operation and quick resolution of issues.
- On-premise and Cloud Deployment Options: Deploy CrewAI AMP on-premise or in the cloud, depending on your security and compliance requirements.
CrewAI AMP is designed for enterprises seeking a powerful, reliable solution to transform complex business processes into efficient, intelligent automations.
- Build with AI
- Why CrewAI?
- Getting Started
- Key Features
- Understanding Flows and Crews
- CrewAI vs LangGraph
- Examples
- Connecting Your Crew to a Model
- How CrewAI Compares
- Frequently Asked Questions (FAQ)
- Contribution
- Telemetry
- License
Using an AI coding agent? Teach it CrewAI best practices in one command:
Claude Code:
/plugin marketplace add crewAIInc/skills
/plugin install crewai-skills@crewai-plugins
/reload-pluginsFour skills that activate automatically when you ask relevant CrewAI questions:
| Skill | When it runs |
|---|---|
getting-started |
Scaffolding new projects, choosing between LLM.call() / Agent / Crew / Flow, wiring crew.py / main.py |
design-agent |
Configuring agents โ role, goal, backstory, tools, LLMs, memory, guardrails |
design-task |
Writing task descriptions, dependencies, structured output (output_pydantic, output_json), human review |
ask-docs |
Querying the live CrewAI docs MCP server for up-to-date API details |
Cursor, Codex, Windsurf, and others (skills.sh):
npx skills add crewaiinc/skillsThis installs the official CrewAI Skills โ structured instructions that teach coding agents how to scaffold Flows, configure Crews, design agents and tasks, and follow CrewAI patterns.
CrewAI unlocks the true potential of multi-agent automation, delivering the best-in-class combination of speed, flexibility, and control with either Crews of AI Agents or Flows of Events:
- Standalone Framework: Built from scratch, independent of LangChain or any other agent framework.
- High Performance: Optimized for speed and minimal resource usage, enabling faster execution.
- Flexible Low Level Customization: Complete freedom to customize at both high and low levels - from overall workflows and system architecture to granular agent behaviors, internal prompts, and execution logic.
- Ideal for Every Use Case: Proven effective for both simple tasks and highly complex, real-world, enterprise-grade scenarios.
- Robust Community: Backed by a rapidly growing community of over 100,000 certified developers offering comprehensive support and resources.
CrewAI empowers developers and enterprises to confidently build intelligent automations, bridging the gap between simplicity, flexibility, and performance.
Setup and run your first CrewAI agents by following this tutorial.
Learning Resources
Learn CrewAI through our comprehensive courses:
- Multi AI Agent Systems with CrewAI - Master the fundamentals of multi-agent systems
- Practical Multi AI Agents and Advanced Use Cases - Deep dive into advanced implementations
CrewAI offers two powerful, complementary approaches that work seamlessly together to build sophisticated AI applications:
-
Crews: Teams of AI agents with true autonomy and agency, working together to accomplish complex tasks through role-based collaboration. Crews enable:
- Natural, autonomous decision-making between agents
- Dynamic task delegation and collaboration
- Specialized roles with defined goals and expertise
- Flexible problem-solving approaches
-
Flows: Production-ready, event-driven workflows that deliver precise control over complex automations. Flows provide:
- Fine-grained control over execution paths for real-world scenarios
- Secure, consistent state management between tasks
- Clean integration of AI agents with production Python code
- Conditional branching for complex business logic
The true power of CrewAI emerges when combining Crews and Flows. This synergy allows you to:
- Build complex, production-grade applications
- Balance autonomy with precise control
- Handle sophisticated real-world scenarios
- Maintain clean, maintainable code structure
To get started with CrewAI, follow these simple steps:
Ensure you have Python >=3.10 <3.14 installed on your system. CrewAI uses UV for dependency management and package handling, offering a seamless setup and execution experience.
First, install CrewAI:
uv pip install crewaiIf you want to install the 'crewai' package along with its optional features that include additional tools for agents, you can do so by using the following command:
uv pip install 'crewai[tools]'The command above installs the basic package and also adds extra components which require more dependencies to function.
If you encounter issues during installation or usage, here are some common solutions:
-
ModuleNotFoundError: No module named 'tiktoken'
- Install tiktoken explicitly:
uv pip install 'crewai[embeddings]' - If using embedchain or other tools:
uv pip install 'crewai[tools]'
- Install tiktoken explicitly:
-
Failed building wheel for tiktoken
- Ensure Rust compiler is installed (see installation steps above)
- For Windows: Verify Visual C++ Build Tools are installed
- Try upgrading pip:
uv pip install --upgrade pip - If issues persist, use a pre-built wheel:
uv pip install tiktoken --prefer-binary
To create a new CrewAI project, run the following CLI (Command Line Interface) command:
crewai create crew <project_name>This command creates a new project folder with the following structure:
my_project/
โโโ .gitignore
โโโ pyproject.toml
โโโ README.md
โโโ .env
โโโ src/
โโโ my_project/
โโโ __init__.py
โโโ main.py
โโโ crew.py
โโโ tools/
โ โโโ custom_tool.py
โ โโโ __init__.py
โโโ config/
โโโ agents.yaml
โโโ tasks.yaml
You can now start developing your crew by editing the files in the src/my_project folder. The main.py file is the entry point of the project, the crew.py file is where you define your crew, the agents.yaml file is where you define your agents, and the tasks.yaml file is where you define your tasks.
- Modify
src/my_project/config/agents.yamlto define your agents. - Modify
src/my_project/config/tasks.yamlto define your tasks. - Modify
src/my_project/crew.pyto add your own logic, tools, and specific arguments. - Modify
src/my_project/main.pyto add custom inputs for your agents and tasks. - Add your environment variables into the
.envfile.
Instantiate your crew:
crewai create crew latest-ai-developmentModify the files as needed to fit your use case:
agents.yaml
# src/my_project/config/agents.yaml
researcher:
role: >
{topic} Senior Data Researcher
goal: >
Uncover cutting-edge developments in {topic}
backstory: >
You're a seasoned researcher with a knack for uncovering the latest
developments in {topic}. Known for your ability to find the most relevant
information and present it in a clear and concise manner.
reporting_analyst:
role: >
{topic} Reporting Analyst
goal: >
Create detailed reports based on {topic} data analysis and research findings
backstory: >
You're a meticulous analyst with a keen eye for detail. You're known for
your ability to turn complex data into clear and concise reports, making
it easy for others to understand and act on the information you provide.tasks.yaml
# src/my_project/config/tasks.yaml
research_task:
description: >
Conduct a thorough research about {topic}
Make sure you find any interesting and relevant information given
the current year is 2025.
expected_output: >
A list with 10 bullet points of the most relevant information about {topic}
agent: researcher
reporting_task:
description: >
Review the context you got and expand each topic into a full section for a report.
Make sure the report is detailed and contains any and all relevant information.
expected_output: >
A fully fledge reports with the mains topics, each with a full section of information.
Formatted as markdown without '```'
agent: reporting_analyst
output_file: report.mdcrew.py
# src/my_project/crew.py
from crewai import Agent, Crew, Process, Task
from crewai.project import CrewBase, agent, crew, task
from crewai_tools import SerperDevTool
from crewai.agents.agent_builder.base_agent import BaseAgent
from typing import List
@CrewBase
class LatestAiDevelopmentCrew():
"""LatestAiDevelopment crew"""
agents: List[BaseAgent]
tasks: List[Task]
@agent
def researcher(self) -> Agent:
return Agent(
config=self.agents_config['researcher'],
verbose=True,
tools=[SerperDevTool()]
)
@agent
def reporting_analyst(self) -> Agent:
return Agent(
config=self.agents_config['reporting_analyst'],
verbose=True
)
@task
def research_task(self) -> Task:
return Task(
config=self.tasks_config['research_task'],
)
@task
def reporting_task(self) -> Task:
return Task(
config=self.tasks_config['reporting_task'],
output_file='report.md'
)
@crew
def crew(self) -> Crew:
"""Creates the LatestAiDevelopment crew"""
return Crew(
agents=self.agents, # Automatically created by the @agent decorator
tasks=self.tasks, # Automatically created by the @task decorator
process=Process.sequential,
verbose=True,
)main.py
#!/usr/bin/env python
# src/my_project/main.py
import sys
from latest_ai_development.crew import LatestAiDevelopmentCrew
def run():
"""
Run the crew.
"""
inputs = {
'topic': 'AI Agents'
}
LatestAiDevelopmentCrew().crew().kickoff(inputs=inputs)Before running your crew, make sure you have the following keys set as environment variables in your .env file:
- An OpenAI API key (or other LLM API key):
OPENAI_API_KEY=sk-... - A Serper.dev API key:
SERPER_API_KEY=YOUR_KEY_HERE
Lock the dependencies and install them by using the CLI command but first, navigate to your project directory:
cd my_project
crewai install (Optional)To run your crew, execute the following command in the root of your project:
crewai runor
python src/my_project/main.pyIf an error happens due to the usage of poetry, please run the following command to update your crewai package:
crewai updateYou should see the output in the console and the report.md file should be created in the root of your project with the full final report.
In addition to the sequential process, you can use the hierarchical process, which automatically assigns a manager to the defined crew to properly coordinate the planning and execution of tasks through delegation and validation of results. See more about the processes here.
CrewAI stands apart as a lean, standalone, high-performance multi-AI Agent framework delivering simplicity, flexibility, and precise controlโfree from the complexity and limitations found in other agent frameworks.
- Standalone & Lean: Completely independent from other frameworks like LangChain, offering faster execution and lighter resource demands.
- Flexible & Precise: Easily orchestrate autonomous agents through intuitive Crews or precise Flows, achieving perfect balance for your needs.
- Seamless Integration: Effortlessly combine Crews (autonomy) and Flows (precision) to create complex, real-world automations.
- Deep Customization: Tailor every aspectโfrom high-level workflows down to low-level internal prompts and agent behaviors.
- Reliable Performance: Consistent results across simple tasks and complex, enterprise-level automations.
- Thriving Community: Backed by robust documentation and over 100,000 certified developers, providing exceptional support and guidance.
Choose CrewAI to easily build powerful, adaptable, and production-ready AI automations.
You can test different real life examples of AI crews in the CrewAI-examples repo:
Check out code for this example or watch a video below:
Check out code for this example or watch a video below:
Check out code for this example or watch a video below:
CrewAI's power truly shines when combining Crews with Flows to create sophisticated automation pipelines.
CrewAI flows support logical operators like or_ and and_ to combine multiple conditions. This can be used with @start, @listen, or @router decorators to create complex triggering conditions.
or_: Triggers when any of the specified conditions are met.and_Triggers when all of the specified conditions are met.
Here's how you can orchestrate multiple Crews within a Flow:
from crewai.flow.flow import Flow, listen, start, router, or_
from crewai import Crew, Agent, Task, Process
from pydantic import BaseModel
# Define structured state for precise control
class MarketState(BaseModel):
sentiment: str = "neutral"
confidence: float = 0.0
recommendations: list = []
class AdvancedAnalysisFlow(Flow[MarketState]):
@start()
def fetch_market_data(self):
# Demonstrate low-level control with structured state
self.state.sentiment = "analyzing"
return {"sector": "tech", "timeframe": "1W"} # These parameters match the task description template
@listen(fetch_market_data)
def analyze_with_crew(self, market_data):
# Show crew agency through specialized roles
analyst = Agent(
role="Senior Market Analyst",
goal="Conduct deep market analysis with expert insight",
backstory="You're a veteran analyst known for identifying subtle market patterns"
)
researcher = Agent(
role="Data Researcher",
goal="Gather and validate supporting market data",
backstory="You excel at finding and correlating multiple data sources"
)
analysis_task = Task(
description="Analyze {sector} sector data for the past {timeframe}",
expected_output="Detailed market analysis with confidence score",
agent=analyst
)
research_task = Task(
description="Find supporting data to validate the analysis",
expected_output="Corroborating evidence and potential contradictions",
agent=researcher
)
# Demonstrate crew autonomy
analysis_crew = Crew(
agents=[analyst, researcher],
tasks=[analysis_task, research_task],
process=Process.sequential,
verbose=True
)
return analysis_crew.kickoff(inputs=market_data) # Pass market_data as named inputs
@router(analyze_with_crew)
def determine_next_steps(self):
# Show flow control with conditional routing
if self.state.confidence > 0.8:
return "high_confidence"
elif self.state.confidence > 0.5:
return "medium_confidence"
return "low_confidence"
@listen("high_confidence")
def execute_strategy(self):
# Demonstrate complex decision making
strategy_crew = Crew(
agents=[
Agent(role="Strategy Expert",
goal="Develop optimal market strategy")
],
tasks=[
Task(description="Create detailed strategy based on analysis",
expected_output="Step-by-step action plan")
]
)
return strategy_crew.kickoff()
@listen(or_("medium_confidence", "low_confidence"))
def request_additional_analysis(self):
self.state.recommendations.append("Gather more data")
return "Additional analysis required"This example demonstrates how to:
- Use Python code for basic data operations
- Create and execute Crews as steps in your workflow
- Use Flow decorators to manage the sequence of operations
- Implement conditional branching based on Crew results
CrewAI supports using various LLMs through a variety of connection options. By default your agents will use the OpenAI API when querying the model. However, there are several other ways to allow your agents to connect to models. For example, you can configure your agents to use a local model via the Ollama tool.
Please refer to the Connect CrewAI to LLMs page for details on configuring your agents' connections to models.
CrewAI's Advantage: CrewAI combines autonomous agent intelligence with precise workflow control through its unique Crews and Flows architecture. The framework excels at both high-level orchestration and low-level customization, enabling complex, production-grade systems with granular control.
- LangGraph: While LangGraph provides a foundation for building agent workflows, its approach requires significant boilerplate code and complex state management patterns. The framework's tight coupling with LangChain can limit flexibility when implementing custom agent behaviors or integrating with external systems.
P.S. CrewAI demonstrates significant performance advantages over LangGraph, executing 5.76x faster in certain cases like this QA task example (see comparison) while achieving higher evaluation scores with faster completion times in certain coding tasks, like in this example (detailed analysis).
- Autogen: While Autogen excels at creating conversational agents capable of working together, it lacks an inherent concept of process. In Autogen, orchestrating agents' interactions requires additional programming, which can become complex and cumbersome as the scale of tasks grows.
- ChatDev: ChatDev introduced the idea of processes into the realm of AI agents, but its implementation is quite rigid. Customizations in ChatDev are limited and not geared towards production environments, which can hinder scalability and flexibility in real-world applications.
CrewAI is open-source and we welcome contributions. If you're looking to contribute, please:
- Fork the repository.
- Create a new branch for your feature.
- Add your feature or improvement.
- Send a pull request.
- We appreciate your input!
uv lock
uv syncuv venvpre-commit installuv run pytest .uvx mypy srcuv builduv pip install dist/*.tar.gzCrewAI uses anonymous telemetry to collect usage data with the main purpose of helping us improve the library by focusing our efforts on the most used features, integrations and tools.
It's pivotal to understand that NO data is collected concerning prompts, task descriptions, agents' backstories or goals, usage of tools, API calls, responses, any data processed by the agents, or secrets and environment variables, with the exception of the conditions mentioned. When the share_crew feature is enabled, detailed data including task descriptions, agents' backstories or goals, and other specific attributes are collected to provide deeper insights while respecting user privacy. Users can disable telemetry by setting the environment variable OTEL_SDK_DISABLED to true.
Data collected includes:
- Version of CrewAI
- So we can understand how many users are using the latest version
- Version of Python
- So we can decide on what versions to better support
- General OS (e.g. number of CPUs, macOS/Windows/Linux)
- So we know what OS we should focus on and if we could build specific OS related features
- Number of agents and tasks in a crew
- So we make sure we are testing internally with similar use cases and educate people on the best practices
- Crew Process being used
- Understand where we should focus our efforts
- If Agents are using memory or allowing delegation
- Understand if we improved the features or maybe even drop them
- If Tasks are being executed in parallel or sequentially
- Understand if we should focus more on parallel execution
- Language model being used
- Improved support on most used languages
- Roles of agents in a crew
- Understand high level use cases so we can build better tools, integrations and examples about it
- Tools names available
- Understand out of the publicly available tools, which ones are being used the most so we can improve them
Users can opt-in to Further Telemetry, sharing the complete telemetry data by setting the share_crew attribute to True on their Crews. Enabling share_crew results in the collection of detailed crew and task execution data, including goal, backstory, context, and output of tasks. This enables a deeper insight into usage patterns while respecting the user's choice to share.
CrewAI is released under the MIT License.
- What exactly is CrewAI?
- How do I install CrewAI?
- Does CrewAI depend on LangChain?
- Is CrewAI open-source?
- Does CrewAI collect data from users?
- Can CrewAI handle complex use cases?
- Can I use CrewAI with local AI models?
- What makes Crews different from Flows?
- How is CrewAI better than LangChain?
- Does CrewAI support fine-tuning or training custom models?
- What additional features does CrewAI AMP offer?
- Is CrewAI AMP available for cloud and on-premise deployments?
- Can I try CrewAI AMP for free?
A: CrewAI is a standalone, lean, and fast Python framework built specifically for orchestrating autonomous AI agents. Unlike frameworks like LangChain, CrewAI does not rely on external dependencies, making it leaner, faster, and simpler.
A: Install CrewAI using pip:
uv pip install crewaiFor additional tools, use:
uv pip install 'crewai[tools]'A: No. CrewAI is built entirely from the ground up, with no dependencies on LangChain or other agent frameworks. This ensures a lean, fast, and flexible experience.
A: Yes. CrewAI excels at both simple and highly complex real-world scenarios, offering deep customization options at both high and low levels, from internal prompts to sophisticated workflow orchestration.
A: Absolutely! CrewAI supports various language models, including local ones. Tools like Ollama and LM Studio allow seamless integration. Check the LLM Connections documentation for more details.
A: Crews provide autonomous agent collaboration, ideal for tasks requiring flexible decision-making and dynamic interaction. Flows offer precise, event-driven control, ideal for managing detailed execution paths and secure state management. You can seamlessly combine both for maximum effectiveness.
A: CrewAI provides simpler, more intuitive APIs, faster execution speeds, more reliable and consistent results, robust documentation, and an active communityโaddressing common criticisms and limitations associated with LangChain.
A: Yes, CrewAI is open-source and actively encourages community contributions and collaboration.
A: CrewAI collects anonymous telemetry data strictly for improvement purposes. Sensitive data such as prompts, tasks, or API responses are never collected unless explicitly enabled by the user.
A: Check out practical examples in the CrewAI-examples repository, covering use cases like trip planners, stock analysis, and job postings.
A: Contributions are warmly welcomed! Fork the repository, create your branch, implement your changes, and submit a pull request. See the Contribution section of the README for detailed guidelines.
A: CrewAI AMP provides advanced features such as a unified control plane, real-time observability, secure integrations, advanced security, actionable insights, and dedicated 24/7 enterprise support.
A: Yes, CrewAI AMP supports both cloud-based and on-premise deployment options, allowing enterprises to meet their specific security and compliance requirements.
A: Yes, you can explore part of the CrewAI AMP Suite by accessing the Crew Control Plane for free.
A: Yes, CrewAI can integrate with custom-trained or fine-tuned models, allowing you to enhance your agents with domain-specific knowledge and accuracy.
A: Absolutely! CrewAI agents can easily integrate with external tools, APIs, and databases, empowering them to leverage real-world data and resources.
A: Yes, CrewAI is explicitly designed with production-grade standards, ensuring reliability, stability, and scalability for enterprise deployments.
A: CrewAI is highly scalable, supporting simple automations and large-scale enterprise workflows involving numerous agents and complex tasks simultaneously.
A: Yes, CrewAI AMP includes advanced debugging, tracing, and real-time observability features, simplifying the management and troubleshooting of your automations.
A: CrewAI is primarily Python-based but easily integrates with services and APIs written in any programming language through its flexible API integration capabilities.
A: Yes, CrewAI provides extensive beginner-friendly tutorials, courses, and documentation through learn.crewai.com, supporting developers at all skill levels.
A: Yes, CrewAI fully supports human-in-the-loop workflows, allowing seamless collaboration between human experts and AI agents for enhanced decision-making.
Release History
| Version | Changes | Urgency | Date |
|---|---|---|---|
| 1.14.6 | ## What's Changed ### Features - Enhance StdioTransport to prevent environment variable leakage - Enhance planning configuration and observation handling - Declare env_vars on DatabricksQueryTool - Add Agent Control Plane docs ### Bug Fixes - Fix structured output leaks in tool-calling loops - Drop unroundtrippable callbacks and adapter state in checkpoint - Serialize type[BaseModel] fields as JSON schema in checkpoint - Avoid orphan task_started on resume scope restore - Allow AgentExecutor t | High | 5/28/2026 |
| 1.14.5 | ## What's Changed ### Features - Deprecate `CrewAgentExecutor`, default Crew agents to `AgentExecutor` - Improve Daytona sandbox tools - Add `restore_from_state_id` kickoff parameter - Add highlights to `ExaSearchTool`, rename from `EXASearchTool` ### Bug Fixes - Fix memory leak in `git.py` by using `cached_property` - Surface streamed tool calls when `available_functions` is absent - Ensure `skills` loading events for traces - Correct status endpoint path from `/{kickoff_id}/status` to `/stat | High | 5/18/2026 |
| 1.14.4 | ## What's Changed ### Features - Add support for custom persistence key in @persist - Add Responses API support for Azure OpenAI provider - Forward credential_scopes to Azure AI Inference client - Add Vertex AI workload identity setup guide - Add Tavily Research and get Research - Add You.com MCP tools for search, research, and content extraction ### Bug Fixes - Fix fall through when JSON regex match isn't valid JSON - Fix to preserve tool_calls when response also contains text - Fix to forwar | High | 4/30/2026 |
| 1.14.3 | ## What's Changed ### Features - Add lifecycle events for checkpoint operations - Add support for e2b - Fall back to DefaultAzureCredential when no API key is provided in Azure integration - Add Bedrock V4 support - Add Daytona sandbox tools for enhanced functionality - Add checkpoint and fork support to standalone agents ### Bug Fixes - Fix execution_id to be separate from state.id - Resolve replay of recorded method events on checkpoint resume - Fix serialization of initial_state class refer | High | 4/24/2026 |
| 1.14.3a2 | ## What's Changed ### Features - Add support for bedrock V4 - Add Daytona sandbox tools for enhanced functionality - Add 'Build with AI' page โ AI-native docs for coding agents - Add Build with AI to Get Started navigation and page files for all languages (en, ko, pt-BR, ar) ### Bug Fixes - Fix propagation of implicit @CrewBase names to crew events - Resolve issue with duplicate batch initialization in execution metadata merge - Fix serialization of Task class-reference fields for checkpointin | High | 4/21/2026 |
| 1.14.3a1 | ## What's Changed ### Features - Add checkpoint and fork support to standalone agents ### Bug Fixes - Preserve thought_signature in Gemini streaming tool calls - Emit task_started on fork resume and redesign checkpoint TUI - Correct dry-run order and handle checked-out stale branch in devtools release - Use future dates in checkpoint prune tests to prevent time-dependent failures (#5543) ### Documentation - Update changelog and version for v1.14.2 ## Contributors @alex-clawd, @greysonlalond | High | 4/20/2026 |
| 1.14.2 | ## What's Changed ### Features - Add checkpoint resume, diff, and prune commands with improved discoverability. - Add `from_checkpoint` parameter to `Agent.kickoff` and related methods. - Add template management commands for project templates. - Add resume hints to devtools release on failure. - Add deploy validation CLI and enhance LLM initialization ergonomics. - Add checkpoint forking with lineage tracking. - Enrich LLM token tracking with reasoning tokens and cache creation tokens. ### Bug | High | 4/17/2026 |
| 1.14.2 | ## What's Changed ### Features - Add checkpoint resume, diff, and prune commands with improved discoverability. - Add `from_checkpoint` parameter to `Agent.kickoff` and related methods. - Add template management commands for project templates. - Add resume hints to devtools release on failure. - Add deploy validation CLI and enhance LLM initialization ergonomics. - Add checkpoint forking with lineage tracking. - Enrich LLM token tracking with reasoning tokens and cache creation tokens. ### Bug | High | 4/17/2026 |
| 1.14.2 | ## What's Changed ### Features - Add checkpoint resume, diff, and prune commands with improved discoverability. - Add `from_checkpoint` parameter to `Agent.kickoff` and related methods. - Add template management commands for project templates. - Add resume hints to devtools release on failure. - Add deploy validation CLI and enhance LLM initialization ergonomics. - Add checkpoint forking with lineage tracking. - Enrich LLM token tracking with reasoning tokens and cache creation tokens. ### Bug | High | 4/17/2026 |
| 1.14.2 | ## What's Changed ### Features - Add checkpoint resume, diff, and prune commands with improved discoverability. - Add `from_checkpoint` parameter to `Agent.kickoff` and related methods. - Add template management commands for project templates. - Add resume hints to devtools release on failure. - Add deploy validation CLI and enhance LLM initialization ergonomics. - Add checkpoint forking with lineage tracking. - Enrich LLM token tracking with reasoning tokens and cache creation tokens. ### Bug | High | 4/17/2026 |
| 1.14.2rc1 | ## What's Changed ### Bug Fixes - Fix handling of cyclic JSON schemas in MCP tool resolution - Fix vulnerability by bumping python-multipart to 0.0.26 - Fix vulnerability by bumping pypdf to 6.10.1 ### Documentation - Update changelog and version for v1.14.2a5 ## Contributors @greysonlalonde | High | 4/15/2026 |
| 1.14.2a5 | ## What's Changed ### Documentation - Update changelog and version for v1.14.2a4 ## Contributors @greysonlalonde | High | 4/15/2026 |
| 1.14.2a4 | ## What's Changed ### Features - Add resume hints to devtools release on failure ### Bug Fixes - Fix strict mode forwarding to Bedrock Converse API - Fix pytest version to 9.0.3 for security vulnerability GHSA-6w46-j5rx-g56g - Bump OpenAI lower bound to >=2.0.0 ### Documentation - Update changelog and version for v1.14.2a3 ## Contributors @greysonlalonde | Medium | 4/14/2026 |
| 1.14.2a3 | ## What's Changed ### Features - Add deploy validation CLI - Improve LLM initialization ergonomics ### Bug Fixes - Override pypdf and uv to patched versions for CVE-2026-40260 and GHSA-pjjw-68hj-v9mw - Upgrade requests to >=2.33.0 for CVE temp file vulnerability - Preserve Bedrock tool call arguments by removing truthy default - Sanitize tool schemas for strict mode - Deflake MemoryRecord embedding serialization test ### Documentation - Clean up enterprise A2A language - Add enterprise A2A fe | Medium | 4/13/2026 |
| 1.14.2a2 | ## What's Changed ### Features - Add checkpoint TUI with tree view, fork support, and editable inputs/outputs - Enrich LLM token tracking with reasoning tokens and cache creation tokens - Add `from_checkpoint` parameter to kickoff methods - Embed `crewai_version` in checkpoints with migration framework - Add checkpoint forking with lineage tracking ### Bug Fixes - Fix strict mode forwarding to Anthropic and Bedrock providers - Harden NL2SQLTool with read-only default, query validation, and par | Medium | 4/10/2026 |
| 1.14.2a1 | ## What's Changed ### Bug Fixes - Fix emission of flow_finished event after HITL resume - Fix cryptography version to 46.0.7 to address CVE-2026-39892 ### Refactoring - Refactor to use shared I18N_DEFAULT singleton ### Documentation - Update changelog and version for v1.14.1 ## Contributors @greysonlalonde | Medium | 4/8/2026 |
| 1.14.1 | ## What's Changed ### Features - Add async checkpoint TUI browser - Add aclose()/close() and async context manager to streaming outputs ### Bug Fixes - Fix regex for template pyproject.toml version bumps - Sanitize tool names in hook decorator filters - Fix checkpoint handlers registration when CheckpointConfig is created - Bump transformers to 5.5.0 to resolve CVE-2026-1839 - Remove FilteredStream stdout/stderr wrapper ### Documentation - Update changelog and version for v1.14.1rc1 ### Refa | High | 4/8/2026 |
| 1.14.1rc1 | ## What's Changed ### Features - Add async checkpoint TUI browser - Add aclose()/close() and async context manager to streaming outputs ### Bug Fixes - Fix template pyproject.toml version bumps using regex - Sanitize tool names in hook decorator filters - Bump transformers to 5.5.0 to resolve CVE-2026-1839 - Register checkpoint handlers when CheckpointConfig is created ### Refactoring - Replace hardcoded denylist with dynamic BaseTool field exclusion in spec gen - Replace regex with tomlkit i | Medium | 4/8/2026 |
| 1.14.0 | ## What's Changed ### Features - Add checkpoint list/info CLI commands - Add guardrail_type and name to distinguish traces - Add SqliteProvider for checkpoint storage - Add CheckpointConfig for automatic checkpointing - Implement runtime state checkpointing, event system, and executor refactor ### Bug Fixes - Add SSRF and path traversal protections - Add path and URL validation to RAG tools - Exclude embedding vectors from memory serialization to save tokens - Ensure output directory exists be | Medium | 4/7/2026 |
| 1.14.0a4 | ## What's Changed ### Features - Add guardrail_type and name to distinguish traces - Add SqliteProvider for checkpoint storage - Add CheckpointConfig for automatic checkpointing - Implement runtime state checkpointing, event system, and executor refactor ### Bug Fixes - Exclude embedding vectors from memory serialization to save tokens - Bump litellm to >=1.83.0 to address CVE-2026-35030 ### Documentation - Update quickstart and installation guides for improved clarity - Add storage providers | Medium | 4/7/2026 |
| 1.14.0a3 | ## What's Changed ### Documentation - Update changelog and version for v1.14.0a2 ## Contributors @joaomdmoura | Medium | 4/6/2026 |
| 1.14.0a2 | Release 1.14.0a2 | Medium | 4/6/2026 |
| 1.13.0 | ## What's Changed ### Features - Add RuntimeState RootModel for unified state serialization - Enhance event listener with new telemetry spans for skill and memory events - Add A2UI extension with v0.8/v0.9 support, schemas, and docs - Emit token usage data in LLMCallCompletedEvent - Auto-update deployment test repo during release - Improve enterprise release resilience and UX ### Bug Fixes - Add tool repository credentials to crewai install - Add tool repository credentials to uv build in tool | Medium | 4/2/2026 |
| 1.13.0a7 | ## What's Changed ### Features - Add A2UI extension with v0.8/v0.9 support, schemas, and docs ### Bug Fixes - Fix multimodal vision prefixes by adding GPT-5 and o-series ### Documentation - Update changelog and version for v1.13.0a6 ## Contributors @alex-clawd, @greysonlalonde, @joaomdmoura | Medium | 4/2/2026 |
| 1.13.0a6 | ## What's Changed ### Documentation - Fix RBAC permission levels to match actual UI options (#5210) - Update changelog and version for v1.13.0a5 (#5200) ### Performance - Reduce framework overhead by implementing a lazy event bus and skipping tracing when disabled (#5187) ## Contributors @alex-clawd, @joaomdmoura, @lucasgomide | Medium | 4/1/2026 |
| 1.13.0a5 | ## What's Changed ### Documentation - Update changelog and version for v1.13.0a4 ## Contributors @greysonlalonde, @joaomdmoura | Medium | 4/1/2026 |
| 1.13.0a4 | ## What's Changed ### Documentation - Update changelog and version for v1.13.0a3 ## Contributors @greysonlalonde | Medium | 3/31/2026 |
| 1.13.0a3 | ## What's Changed ### Features - Emit token usage data in LLMCallCompletedEvent - Extract and publish tool metadata to AMP ### Bug Fixes - Handle GPT-5.x models not supporting the `stop` API parameter ### Documentation - Fix inaccuracies in agent-capabilities across all languages - Add Agent Capabilities overview and improve Skills documentation - Add comprehensive SSO configuration guide - Update changelog and version for v1.13.0rc1 ### Refactoring - Convert Flow to Pydantic BaseModel - Con | Medium | 3/31/2026 |
| 1.13.0rc1 | ## What's Changed ### Documentation - Update changelog and version for v1.13.0a2 ## Contributors @greysonlalonde | Medium | 3/27/2026 |
| 1.13.0a2 | ## What's Changed ### Features - Auto-update deployment test repo during release - Improve enterprise release resilience and UX ### Documentation - Update changelog and version for v1.13.0a1 ## Contributors @greysonlalonde | Medium | 3/26/2026 |
| 1.13.0a1 | ## What's Changed ### Bug Fixes - Fix broken links in documentation workflow by pinning Node to LTS 22 - Bust the uv cache for freshly published packages in enterprise release ### Documentation - Add comprehensive RBAC permissions matrix and deployment guide - Update changelog and version for v1.12.2 ## Contributors @greysonlalonde, @iris-clawd, @joaomdmoura | Medium | 3/26/2026 |
| 1.12.2 | ## What's Changed ### Features - Add enterprise release phase to devtools release ### Bug Fixes - Preserve method return value as flow output for @human_feedback with emit ### Documentation - Update changelog and version for v1.12.1 - Revise security policy and reporting instructions ## Contributors @alex-clawd, @greysonlalonde, @joaomdmoura, @theCyberTech | Medium | 3/26/2026 |
| 1.12.1 | ## What's Changed ### Features - Add request_id to HumanFeedbackRequestedEvent - Add Qdrant Edge storage backend for memory system - Add docs-check command to analyze changes and generate docs with translations - Add Arabic language support to changelog and release tooling - Add modern standard Arabic translation of all documentation - Add logout command in CLI - Add agent skills - Implement automatic root_scope for hierarchical memory isolation - Implement native OpenAI-compatible providers (O | Medium | 3/26/2026 |
| 1.12.0 | ## What's Changed ### Features - Add Qdrant Edge storage backend for memory system - Add docs-check command to analyze changes and generate docs with translations - Add Arabic language support to changelog and release tooling - Add modern standard Arabic translation of all documentation - Add logout command in CLI - Implement agent skills - Implement automatic root_scope for hierarchical memory isolation - Implement native OpenAI-compatible providers (OpenRouter, DeepSeek, Ollama, vLLM, Cerebra | Medium | 3/26/2026 |
| 1.12.0a3 | ## What's Changed ### Bug Fixes - Fix bad credentials for traces batch push (404) - Resolve multiple bugs in HITL flow system ### Documentation - Update changelog and version for v1.12.0a2 ## Contributors @akaKuruma, @greysonlalonde | Medium | 3/25/2026 |
| 1.12.0a2 | ## What's Changed ### Features - Add Qdrant Edge storage backend for memory system ### Documentation - Update changelog and version for v1.12.0a1 ## Contributors @greysonlalonde | Medium | 3/25/2026 |
| 1.12.0a1 | ## What's Changed ### Features - Add docs-check command to analyze changes and generate docs with translations - Add Arabic language support to changelog and release tooling - Add modern standard Arabic translation of all documentation - Add native OpenAI-compatible providers (OpenRouter, DeepSeek, Ollama, vLLM, Cerebras, Dashscope) - Add agent skills - Add logout command in CLI - Implement automatic root_scope for hierarchical memory isolation ### Bug Fixes - Fix agent memory saving - Resolve | Medium | 3/25/2026 |
| 1.11.1 | ## What's Changed ### Features - Add flow_structure() serializer for Flow class introspection. ### Bug Fixes - Fix security vulnerabilities by bumping pypdf, tinytag, and langchain-core. - Preserve full LLM config across HITL resume for non-OpenAI providers. - Prevent path traversal in FileWriterTool. - Fix lock_store crash when redis package is not installed. - Pass cache_function from BaseTool to CrewStructuredTool. ### Documentation - Add publish custom tools guide with translations. - Upd | Medium | 3/23/2026 |
| 1.11.0 | ## What's Changed ### Documentation - Update changelog and version for v1.11.0rc2 ## Contributors @greysonlalonde | Low | 3/18/2026 |
| 1.11.0rc2 | ## What's Changed ### Bug Fixes - Enhance LLM response handling and serialization. - Upgrade vulnerable transitive dependencies (authlib, PyJWT, snowflake-connector-python). - Replace `os.system` with `subprocess.run` in unsafe mode pip install. ### Documentation - Update Exa Search Tool page with improved naming, description, and configuration options. - Add Custom MCP Servers in How-To Guide. - Update OTEL collectors documentation. - Update MCP documentation. - Update changelog and version f | Low | 3/17/2026 |
| 1.11.0rc1 | ## What's Changed ### Features - Add Plus API token authentication for a2a enterprise - Implement plan execute pattern ### Bug Fixes - Resolve code interpreter sandbox escape issue ### Documentation - Update changelog and version for v1.10.2rc2 ## Contributors @Copilot, @greysonlalonde, @lorenzejay, @theCyberTech | Low | 3/16/2026 |
| 1.10.2rc2 | ## What's Changed ### Bug Fixes - Remove exclusive locks from read-only storage operations ### Documentation - Update changelog and version for v1.10.2rc1 ## Contributors @greysonlalonde | Low | 3/14/2026 |
| 1.10.2rc1 | ## What's Changed ### Features - Add release command and trigger PyPI publish ### Bug Fixes - Fix cross-process and thread-safe locking to unprotected I/O - Propagate contextvars across all thread and executor boundaries - Propagate ContextVars into async task threads ### Documentation - Update changelog and version for v1.10.2a1 ## Contributors @danglies007, @greysonlalonde | Low | 3/13/2026 |
| 1.10.2a1 | ## What's Changed ### Features - Add support for tool search by saving tokens and dynamically injecting appropriate tools during execution. - Introduce more Brave Search tools. - Create action for nightly releases. ### Bug Fixes - Fix LockException under concurrent multi-process execution. - Resolve grouping of parallel tool results in a single user message. - Address MCP tools resolutions and eliminate all shared mutable connections. - Fix update of LLM parameter handling in the human_feedbac | Low | 3/11/2026 |
| 1.10.1 | ## What's Changed ### ๐ Features - **Upgrade Gemini GenAI** ### ๐ Bug Fixes - Adjust executor listener value to avoid recursion - Group parallel function response parts in a single `Content` object in Gemini - Surface thought output from thinking models in Gemini - Load MCP and platform tools when agent tools are `None` - Support Jupyter environments with running event loops in A2A - Use anonymous ID for ephemeral traces - Conditionally pass plus header - Skip signal handler reg | Low | 3/4/2026 |
| 1.10.1a1 | ## What's Changed ### Features - Implement asynchronous invocation support in step callback methods - Implement lazy loading for heavy dependencies in Memory module ### Documentation - Update changelog and version for v1.10.0 ### Refactoring - Refactor step callback methods to support asynchronous invocation - Refactor to implement lazy loading for heavy dependencies in Memory module ### Bug Fixes - Fix branch for release notes ## Contributors @greysonlalonde, @joaomdmoura | Low | 2/27/2026 |
| 1.10.0 | ## What's Changed ### Features - Enhance MCP tool resolution and related events - Update lancedb version and add lance-namespace packages - Enhance JSON argument parsing and validation in CrewAgentExecutor and BaseTool - Migrate CLI HTTP client from requests to httpx - Add versioned documentation - Add yanked detection for version notes - Implement user input handling in Flows - Enhance HITL self-loop functionality in human feedback integration tests - Add started_event_id and set in eventbus - | Low | 2/27/2026 |
| 1.10.0a1 | ## What's Changed * declare `stagehand` package as dep for StagehandTool by @thiagomoretto in https://github.com/crewAIInc/crewAI/pull/4336 * fix: flow tracking by @greysonlalonde in https://github.com/crewAIInc/crewAI/pull/4335 * feat: auto update tools.specs by @lucasgomide in https://github.com/crewAIInc/crewAI/pull/4341 * adds additional brave-search-api params by @jonathansampson in https://github.com/crewAIInc/crewAI/pull/4321 * fix: enforce additionalProperties=false in schemas by @greyso | Low | 2/19/2026 |
| 1.9.3 | ## What's Changed Features * feat: add a2a liteagent, auth, transport negotiation, and file support Bug Fixes: * fix: improve output handling and response model integration in agents | Low | 1/30/2026 |
| 1.9.2 | ## What's Changed * fix: ensure verbosity flag is applied b * fix: use response_json_schema * fix: tool response pt2 | Low | 1/29/2026 |
| 1.9.1 | ## What's Changed ### Features - Implement before and after tool call hooks in CrewAgentExecutor - Add structured outputs and response_format support across providers ### Bug Fixes - Correct tool-calling content handling and schema serialization ## Contributors @greysonlalonde, @lorenzejay | Low | 1/28/2026 |
| 1.9.0 | ## What's Changed ### Features - Add structured outputs and response_format support across providers - Add response_id in streaming response - Add event ordering and parent-child hierarchy - Add Keycloak SSO provider support - Add native multimodal file handling; OpenAI responses API - Add a2a task execution utilities - Add a2a server config and agent card generation - Add additional a2a events and enrich event metadata - Add additional a2a transports - Add Galileo to integrations p | Low | 1/27/2026 |
| 1.8.1 | ## What's Changed ### Features - Add A2A task execution utilities - Add A2A server configuration and agent card generation - Add additional A2A transports - Add Galileo to integrations page ### Bug Fixes - Enhance Azure model stop word support detection - Increase frame inspection depth to detect `parent_flow` - Unlink task in execution spans - Improve error handling for HumanFeedbackPending in flow execution - Handle HumanFeedbackPending in flow error management ### Documentation - Update A2 | Low | 1/15/2026 |
| 1.8.0 | ## What's Changed ### Features - Add native async chain for a2a - Add a2a update mechanisms (poll/stream/push) with handlers and config - Introduce global flow configuration for human-in-the-loop feedback - Add streaming tool call events and fix provider ID tracking - Introduce production-ready Flows and Crews architecture - Add HITL for Flows - Improve EventListener and TraceCollectionListener for enhanced event handling ### Bug Fixes - Handle missing a2a dependency as optional - Correct erro | Low | 1/8/2026 |
| 1.7.2 | ## What's Changed ### Bug Fixes - Resolve connection issues (#4129) ### Documentation - Update api-reference/status docs page ## Contributors @greysonlalonde, @heitorado, @lorenzejay, @lucasgomide | Low | 12/19/2025 |
| 1.7.1 | ## What's Changed ### Improvements - Add `--no-commit` flag to bump command - Use JSON schema for tool argument serialization ### Bug Fixes - Fix error message display from response when tool repository login fails - Fix graceful termination of future when executing a task asynchronously - Fix task ordering by adding index - Fix platform compatibility checks for Windows signals - Fix RPM controller timer to prevent process hang - Fix token usage recording and validate response mode | Low | 12/16/2025 |
| 1.7.0 | ## What's Changed ### Features - Add async flow kickoff - Add async crew support - Add async task support - Add async knowledge support - Add async memory support - Add async support for tools and agent executor; improve typing and docs - Implement a2a extensions API and async agent card caching; fix task propagation & streaming - Add native async tool support - Add async llm support - Create sys event types and handler ### Bug Fixes - Fix issue to ensure nonetypes are not passed to otel - Fix | Low | 12/9/2025 |






