Fix langchain at 0.1.0

.editorconfig

@@ -1,14 +0,0 @@
-# .editorconfig
-root = true
-
-# All files
-[*]
-charset = utf-8
-end_of_line = lf
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-# Python files
-[*.py]
-indent_style = space
-indent_size = 2

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,115 +0,0 @@
-name: Bug report
-description: Create a report to help us improve CrewAI
-title: "[BUG]"
-labels: ["bug"]
-assignees: []
-body:
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: Provide a clear and concise description of what the bug is.
-    validations:
-      required: true
-  - type: textarea
-    id: steps-to-reproduce
-    attributes:
-      label: Steps to Reproduce
-      description: Provide a step-by-step process to reproduce the behavior.
-      placeholder: |
-        1. Go to '...'
-        2. Click on '....'
-        3. Scroll down to '....'
-        4. See error
-    validations:
-      required: true
-  - type: textarea
-    id: expected-behavior
-    attributes:
-      label: Expected behavior
-      description: A clear and concise description of what you expected to happen.
-    validations:
-      required: true
-  - type: textarea
-    id: screenshots-code
-    attributes:
-      label: Screenshots/Code snippets
-      description: If applicable, add screenshots or code snippets to help explain your problem.
-    validations:
-      required: true
-  - type: dropdown
-    id: os
-    attributes:
-      label: Operating System
-      description: Select the operating system you're using
-      options:
-        - Ubuntu 20.04
-        - Ubuntu 22.04
-        - Ubuntu 24.04
-        - macOS Catalina
-        - macOS Big Sur
-        - macOS Monterey
-        - macOS Ventura
-        - macOS Sonoma
-        - Windows 10
-        - Windows 11
-        - Other (specify in additional context)
-    validations:
-      required: true
-  - type: dropdown
-    id: python-version
-    attributes:
-      label: Python Version
-      description: Version of Python your Crew is running on
-      options:
-        - '3.10'
-        - '3.11'
-        - '3.12'
-    validations:
-      required: true
-  - type: input
-    id: crewai-version
-    attributes:
-      label: crewAI Version
-      description: What version of CrewAI are you using
-    validations:
-      required: true
-  - type: input
-    id: crewai-tools-version
-    attributes:
-      label: crewAI Tools Version
-      description: What version of CrewAI Tools are you using 
-    validations:
-      required: true
-  - type: dropdown
-    id: virtual-environment
-    attributes:
-      label: Virtual Environment
-      description: What Virtual Environment are you running your crew in.
-      options:
-        - Venv
-        - Conda
-        - Poetry
-    validations:
-      required: true
-  - type: textarea
-    id: evidence
-    attributes:
-      label: Evidence
-      description: Include relevant information, logs or error messages. These can be screenshots.
-    validations:
-      required: true
-  - type: textarea
-    id: possible-solution
-    attributes:
-      label: Possible Solution
-      description: Have a solution in mind? Please suggest it here, or write "None".
-    validations:
-      required: true
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: Additional context
-      description: Add any other context about the problem here.
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +0,0 @@
-blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,65 +0,0 @@
-name: Feature request
-description: Suggest a new feature for CrewAI
-title: "[FEATURE]"
-labels: ["feature-request"]
-assignees: []
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this feature request!
-  - type: dropdown
-    id: feature-area
-    attributes:
-      label: Feature Area
-      description: Which area of CrewAI does this feature primarily relate to?
-      options:
-        - Core functionality
-        - Agent capabilities
-        - Task management
-        - Integration with external tools
-        - Performance optimization
-        - Documentation
-        - Other (please specify in additional context)
-    validations:
-      required: true
-  - type: textarea
-    id: problem
-    attributes:
-      label: Is your feature request related to a an existing bug? Please link it here.
-      description: A link to the bug or NA if not related to an existing bug.
-    validations:
-      required: true
-  - type: textarea
-    id: solution
-    attributes:
-      label: Describe the solution you'd like
-      description: A clear and concise description of what you want to happen.
-    validations:
-      required: true
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Describe alternatives you've considered
-      description: A clear and concise description of any alternative solutions or features you've considered.
-    validations:
-      required: false
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional context
-      description: Add any other context, screenshots, or examples about the feature request here.
-    validations:
-      required: false
-  - type: dropdown
-    id: willingness-to-contribute
-    attributes:
-      label: Willingness to Contribute
-      description: Would you be willing to contribute to the implementation of this feature?
-      options:
-        - Yes, I'd be happy to submit a pull request
-        - I could provide more detailed specifications
-        - I can test the feature once it's implemented
-        - No, I'm just suggesting the idea
-    validations:
-      required: true

.github/security.md

@@ -1,19 +0,0 @@
-CrewAI takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organization.
-If you believe you have found a security vulnerability in any CrewAI product or service, please report it to us as described below.
-
- ## Reporting a Vulnerability
- Please do not report security vulnerabilities through public GitHub issues.
- To report a vulnerability, please email us at security@crewai.com.
- Please include the requested information listed below so that we can triage your report more quickly
-
- - Type of issue (e.g. SQL injection, cross-site scripting, etc.)
- - Full paths of source file(s) related to the manifestation of the issue
- - The location of the affected source code (tag/branch/commit or direct URL)
- - Any special configuration required to reproduce the issue
- - Step-by-step instructions to reproduce the issue (please include screenshots if needed)
- - Proof-of-concept or exploit code (if possible)
- - Impact of the issue, including how an attacker might exploit the issue
-
- Once we have received your report, we will respond to you at the email address you provide. If the issue is confirmed, we will release a patch as soon as possible depending on the complexity of the issue.
-
- At this time, we are not offering a bug bounty program. Any rewards will be at our discretion.

.github/workflows/black.yml

@@ -0,0 +1,10 @@
+name: Lint
+
+on: [push, pull_request]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: psf/black@stable

.github/workflows/linter.yml

@@ -1,16 +0,0 @@
-name: Lint
-
-on: [pull_request]
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Install Requirements
-        run: |
-          pip install ruff
-
-      - name: Run Ruff Linter
-        run: ruff check

.github/workflows/mkdocs.yml

@@ -1,8 +1,10 @@
 name: Deploy MkDocs
 
 on:
-  release:
-    types: [published]
+  workflow_dispatch:    
+  push:
+    branches:
+      - main
 
 permissions:
   contents: write
@@ -13,33 +15,21 @@ jobs:
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v2
 
       - name: Setup Python
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v4
         with:
           python-version: '3.10'
 
-      - name: Calculate requirements hash
-        id: req-hash
-        run: echo "::set-output name=hash::$(sha256sum requirements-doc.txt | awk '{print $1}')"
-
-      - name: Setup cache
-        uses: actions/cache@v4
-        with:
-          key: mkdocs-material-${{ steps.req-hash.outputs.hash }}
-          path: .cache
-          restore-keys: |
-            mkdocs-material-
-
       - name: Install Requirements
         run: |
           sudo apt-get update &&
           sudo apt-get install pngquant &&
-          pip install mkdocs-material mkdocs-material-extensions pillow cairosvg
+          pip install mkdocs-material
 
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
 
       - name: Build and deploy MkDocs
-        run: mkdocs gh-deploy --force
+        run: mkdocs gh-deploy --force

.github/workflows/security-checker.yml

@@ -1,23 +0,0 @@
-name: Security Checker
-
-on: [pull_request]
-
-jobs:
-  security-check:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.11.9"
-
-      - name: Install dependencies
-        run: pip install bandit
-
-      - name: Run Bandit
-        run: bandit -c pyproject.toml -r src/ -ll
-

.github/workflows/stale.yml

@@ -1,29 +0,0 @@
-name: Mark stale issues and pull requests
-
-permissions:
-  contents: write
-  issues: write
-  pull-requests: write
-
-on:
-  schedule:
-    - cron: '10 12 * * *'
-  workflow_dispatch:
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/stale@v9
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        stale-issue-label: 'no-issue-activity'
-        stale-issue-message: 'This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
-        close-issue-message: 'This issue was closed because it has been stalled for 5 days with no activity.'
-        days-before-issue-stale: 30
-        days-before-issue-close: 5
-        stale-pr-label: 'no-pr-activity'
-        stale-pr-message: 'This PR is stale because it has been open for 45 days with no activity.'
-        days-before-pr-stale: 45
-        days-before-pr-close: -1
-        operations-per-run: 1200

.github/workflows/tests.yml

@@ -1,6 +1,6 @@
 name: Run Tests
 
-on: [pull_request]
+on: [push, pull_request]
 
 permissions:
   contents: write
@@ -9,24 +9,24 @@ env:
   OPENAI_API_KEY: fake-api-key
 
 jobs:
-  tests:
+  deploy:
     runs-on: ubuntu-latest
-    timeout-minutes: 15
+
     steps:
       - name: Checkout code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v2
 
-      - name: Install uv
-        uses: astral-sh/setup-uv@v3
+      - name: Setup Python
+        uses: actions/setup-python@v4
         with:
-          enable-cache: true
+          python-version: '3.10'
 
-
-      - name: Set up Python
-        run: uv python install 3.12.8
-
-      - name: Install the project
-        run: uv sync --dev --all-extras
+      - name: Install Requirements
+        run: |
+          sudo apt-get update &&
+          pip install poetry &&
+          poetry lock &&
+          poetry install
 
       - name: Run tests
-        run: uv run pytest tests -vv
+        run: poetry run pytest

.github/workflows/type-checker.yml

@@ -1,26 +0,0 @@
-name: Run Type Checks
-
-on: [pull_request]
-
-permissions:
-  contents: write
-
-jobs:
-  type-checker:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.11.9"
-
-      - name: Install Requirements
-        run: |
-          pip install mypy
-
-      - name: Run type checks
-        run: mypy src

.gitignore

@@ -2,28 +2,7 @@
 .pytest_cache
 __pycache__
 dist/
-lib/
 .env
 assets/*
 .idea
-test/
-docs_crew/
-chroma.sqlite3
-old_en.json
-db/
-test.py
-rc-tests/*
-*.pkl
-temp/*
-.vscode/*
-crew_tasks_output.json
-.codesight
-.mypy_cache
-.ruff_cache
-.venv
-agentops.log
-test_flow.html
-crewairules.mdc
-plan.md
-conceptual_plan.md
-build_image
+test.py

.pre-commit-config.yaml

@@ -1,7 +1,21 @@
 repos:
-  - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.8.2
+
+  - repo: https://github.com/psf/black-pre-commit-mirror
+    rev: 23.12.1
     hooks:
-      - id: ruff
-        args: ["--fix"]
-      - id: ruff-format
+      - id: black
+        language_version: python3.11
+        files: \.(py)$
+
+  - repo: https://github.com/pycqa/isort
+    rev: 5.13.2
+    hooks:
+      - id: isort
+        name: isort (python)
+        args: ["--profile", "black", "--filter-files"]
+
+  - repo: https://github.com/PyCQA/autoflake
+    rev: v2.2.1
+    hooks:
+      - id: autoflake
+        args: ['--in-place', '--remove-all-unused-imports', '--remove-unused-variables', '--ignore-init-module-imports']

.ruff.toml

@@ -1,9 +0,0 @@
-exclude = [
-    "templates",
-    "__init__.py",
-]
-
-[lint]
-select = [
-    "I", # isort rules
-]

LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2025 crewAI, Inc.
+Copyright (c) 2018 The Python Packaging Authority
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,519 +1,183 @@
-<div align="center">
+THIS IS A TEST
 
-![Logo of CrewAI](./docs/crewai_logo.png)
+# crewAI
 
+![Logo of crewAI, tow people rowing on a boat](./docs/crewai_logo.png)
 
-</div>
+🤖 Cutting-edge framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.
 
-### Fast and Flexible Multi-Agent Automation Framework
-
-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**: 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](https://learn.crewai.com), CrewAI is rapidly becoming the
-standard for enterprise-ready AI automation.
-
-# CrewAI Enterprise Suite
-
-CrewAI Enterprise 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](https://app.crewai.com)
-
-## Crew Control Plane Key Features:
-- **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 Enterprise on-premise or in the cloud, depending on your security and compliance requirements.
-
-CrewAI Enterprise is designed for enterprises seeking a powerful,
-reliable solution to transform complex business processes into efficient,
-intelligent automations.
-
-<h3>
-
-[Homepage](https://www.crewai.com/) | [Documentation](https://docs.crewai.com/) | [Chat with Docs](https://chatg.pt/DWjSBZn) | [Discourse](https://community.crewai.com)
-
-</h3>
-
-[![GitHub Repo stars](https://img.shields.io/github/stars/joaomdmoura/crewAI)](https://github.com/crewAIInc/crewAI)
-[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
-
-</div>
-
-## Table of contents
-
-- [Why CrewAI?](#why-crewai)
-- [Getting Started](#getting-started)
-- [Key Features](#key-features)
-- [Understanding Flows and Crews](#understanding-flows-and-crews)
-- [CrewAI vs LangGraph](#how-crewai-compares)
-- [Examples](#examples)
-  - [Quick Tutorial](#quick-tutorial)
-  - [Write Job Descriptions](#write-job-descriptions)
-  - [Trip Planner](#trip-planner)
-  - [Stock Analysis](#stock-analysis)
-  - [Using Crews and Flows Together](#using-crews-and-flows-together)
-- [Connecting Your Crew to a Model](#connecting-your-crew-to-a-model)
-- [How CrewAI Compares](#how-crewai-compares)
-- [Frequently Asked Questions (FAQ)](#frequently-asked-questions-faq)
-- [Contribution](#contribution)
-- [Telemetry](#telemetry)
-- [License](#license)
+- [crewAI](#crewai)
+  - [Why CrewAI?](#why-crewai)
+  - [Getting Started](#getting-started)
+  - [Key Features](#key-features)
+  - [Examples](#examples)
+    - [Code](#code)
+    - [Video](#video)
+      - [Quick Tutorial](#quick-tutorial)
+      - [Trip Planner](#trip-planner)
+      - [Stock Analysis](#stock-analysis)
+  - [Connecting Your Crew to a Model](#connecting-your-crew-to-a-model)
+  - [How CrewAI Compares](#how-crewai-compares)
+  - [Contribution](#contribution)
+    - [Installing Dependencies](#installing-dependencies)
+    - [Virtual Env](#virtual-env)
+    - [Pre-commit hooks](#pre-commit-hooks)
+    - [Running Tests](#running-tests)
+    - [Packaging](#packaging)
+    - [Installing Locally](#installing-locally)
+  - [Hire CrewAI](#hire-crewai)
+  - [License](#license)
 
 ## Why CrewAI?
 
-<div align="center" style="margin-bottom: 30px;">
-  <img src="docs/asset.png" alt="CrewAI Logo" width="100%">
-</div>
+The power of AI collaboration has too much to offer.
+CrewAI is designed to enable AI agents to assume roles, share goals, and operate in a cohesive unit - much like a well-oiled crew. Whether you're building a smart assistant platform, an automated customer service ensemble, or a multi-agent research team, CrewAI provides the backbone for sophisticated multi-agent interactions.
 
-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.
+- 🤖 [Talk with the Docs](https://chatg.pt/DWjSBZn)
+- 📄 [Documentation Wiki](https://joaomdmoura.github.io/crewAI/)
 
 ## Getting Started
 
-### Learning Resources
-
-Learn CrewAI through our comprehensive courses:
-- [Multi AI Agent Systems with CrewAI](https://www.deeplearning.ai/short-courses/multi-ai-agent-systems-with-crewai/) - Master the fundamentals of multi-agent systems
-- [Practical Multi AI Agents and Advanced Use Cases](https://www.deeplearning.ai/short-courses/practical-multi-ai-agents-and-advanced-use-cases-with-crewai/) - Deep dive into advanced implementations
-
-### Understanding Flows and Crews
-
-CrewAI offers two powerful, complementary approaches that work seamlessly together to build sophisticated AI applications:
-
-1. **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
-
-2. **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
-
-### Getting Started with Installation
-
 To get started with CrewAI, follow these simple steps:
 
-### 1. Installation
-
-Ensure you have Python >=3.10 <3.13 installed on your system. CrewAI uses [UV](https://docs.astral.sh/uv/) for dependency management and package handling, offering a seamless setup and execution experience.
-
-First, install CrewAI:
+1. **Installation**:
 
 ```shell
 pip install crewai
 ```
-If 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:
 
+The example below also uses duckduckgo, so also install that
 ```shell
-pip install 'crewai[tools]'
-```
-The command above installs the basic package and also adds extra components which require more dependencies to function.
-
-### Troubleshooting Dependencies
-
-If you encounter issues during installation or usage, here are some common solutions:
-
-#### Common Issues
-
-1. **ModuleNotFoundError: No module named 'tiktoken'**
-   - Install tiktoken explicitly: `pip install 'crewai[embeddings]'`
-   - If using embedchain or other tools: `pip install 'crewai[tools]'`
-
-2. **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: `pip install --upgrade pip`
-   - If issues persist, use a pre-built wheel: `pip install tiktoken --prefer-binary`
-
-### 2. Setting Up Your Crew with the YAML Configuration
-
-To create a new CrewAI project, run the following CLI (Command Line Interface) command:
-
-```shell
-crewai create crew <project_name>
+pip install duckduckgo-search
 ```
 
-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.
-
-#### To customize your project, you can:
-
-- Modify `src/my_project/config/agents.yaml` to define your agents.
-- Modify `src/my_project/config/tasks.yaml` to define your tasks.
-- Modify `src/my_project/crew.py` to add your own logic, tools, and specific arguments.
-- Modify `src/my_project/main.py` to add custom inputs for your agents and tasks.
-- Add your environment variables into the `.env` file.
-
-#### Example of a simple crew with a sequential process:
-
-Instantiate your crew:
-
-```shell
-crewai create crew latest-ai-development
-```
-
-Modify the files as needed to fit your use case:
-
-**agents.yaml**
-
-```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**
-
-```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.md
-```
-
-**crew.py**
+2. **Setting Up Your Crew**:
 
 ```python
-# 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
+import os
+from crewai import Agent, Task, Crew, Process
 
-@CrewBase
-class LatestAiDevelopmentCrew():
-	"""LatestAiDevelopment crew"""
+os.environ["OPENAI_API_KEY"] = "YOUR KEY"
 
-	@agent
-	def researcher(self) -> Agent:
-		return Agent(
-			config=self.agents_config['researcher'],
-			verbose=True,
-			tools=[SerperDevTool()]
-		)
+# You can choose to use a local model through Ollama for example. See ./docs/llm-connections.md for more information.
+# from langchain.llms import Ollama
+# ollama_llm = Ollama(model="openhermes")
 
-	@agent
-	def reporting_analyst(self) -> Agent:
-		return Agent(
-			config=self.agents_config['reporting_analyst'],
-			verbose=True
-		)
+# Install duckduckgo-search for this example:
+# !pip install -U duckduckgo-search
 
-	@task
-	def research_task(self) -> Task:
-		return Task(
-			config=self.tasks_config['research_task'],
-		)
+from langchain.tools import DuckDuckGoSearchRun
+search_tool = DuckDuckGoSearchRun()
 
-	@task
-	def reporting_task(self) -> Task:
-		return Task(
-			config=self.tasks_config['reporting_task'],
-			output_file='report.md'
-		)
+# Define your agents with roles and goals
+researcher = Agent(
+  role='Senior Research Analyst',
+  goal='Uncover cutting-edge developments in AI and data science',
+  backstory="""You work at a leading tech think tank.
+  Your expertise lies in identifying emerging trends.
+  You have a knack for dissecting complex data and presenting
+  actionable insights.""",
+  verbose=True,
+  allow_delegation=False,
+  tools=[search_tool]
+  # You can pass an optional llm attribute specifying what mode you wanna use.
+  # It can be a local model through Ollama / LM Studio or a remote
+  # model like OpenAI, Mistral, Antrophic or others (https://python.langchain.com/docs/integrations/llms/)
+  #
+  # Examples:
+  # llm=ollama_llm # was defined above in the file
+  # llm=OpenAI(model_name="gpt-3.5", temperature=0.7)
+  # For the OpenAI model you would need to import
+  # from langchain_openai import OpenAI
+)
+writer = Agent(
+  role='Tech Content Strategist',
+  goal='Craft compelling content on tech advancements',
+  backstory="""You are a renowned Content Strategist, known for
+  your insightful and engaging articles.
+  You transform complex concepts into compelling narratives.""",
+  verbose=True,
+  allow_delegation=True,
+  # (optional) llm=ollama_llm
+)
 
-	@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,
-		)
+# Create tasks for your agents
+task1 = Task(
+  description="""Conduct a comprehensive analysis of the latest advancements in AI in 2024.
+  Identify key trends, breakthrough technologies, and potential industry impacts.
+  Your final answer MUST be a full analysis report""",
+  agent=researcher
+)
+
+task2 = Task(
+  description="""Using the insights provided, develop an engaging blog
+  post that highlights the most significant AI advancements.
+  Your post should be informative yet accessible, catering to a tech-savvy audience.
+  Make it sound cool, avoid complex words so it doesn't sound like AI.
+  Your final answer MUST be the full blog post of at least 4 paragraphs.""",
+  agent=writer
+)
+
+# Instantiate your crew with a sequential process
+crew = Crew(
+  agents=[researcher, writer],
+  tasks=[task1, task2],
+  verbose=2, # You can set it to 1 or 2 to different logging levels
+)
+
+# Get your crew to work!
+result = crew.kickoff()
+
+print("######################")
+print(result)
 ```
 
-**main.py**
+Currently the only supported process is `Process.sequential`, where one task is executed after the other and the outcome of one is passed as extra content into this next.
 
-```python
-#!/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)
-```
-
-### 3. Running Your Crew
-
-Before running your crew, make sure you have the following keys set as environment variables in your `.env` file:
-
-- An [OpenAI API key](https://platform.openai.com/account/api-keys) (or other LLM API key): `OPENAI_API_KEY=sk-...`
-- A [Serper.dev](https://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:
-
-```shell
-cd my_project
-crewai install (Optional)
-```
-
-To run your crew, execute the following command in the root of your project:
-
-```bash
-crewai run
-```
-
-or
-
-```bash
-python src/my_project/main.py
-```
-
-If an error happens due to the usage of poetry, please run the following command to update your crewai package:
-
-```bash
-crewai update
-```
-
-You 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](https://docs.crewai.com/core-concepts/Processes/).
 
 ## Key Features
 
-CrewAI stands apart as a lean, standalone, high-performance framework delivering simplicity, flexibility, and precise control—free from the complexity and limitations found in other agent frameworks.
+- **Role-Based Agent Design**: Customize agents with specific roles, goals, and tools.
+- **Autonomous Inter-Agent Delegation**: Agents can autonomously delegate tasks and inquire amongst themselves, enhancing problem-solving efficiency.
+- **Flexible Task Management**: Define tasks with customizable tools and assign them to agents dynamically.
+- **Processes Driven**: Currently only supports `sequential` task execution but more complex processes like consensual and hierarchical being worked on.
+- **Works with Open Source Models**: Run your crew using Open AI or open source models refer to the [Connect crewAI to LLMs](./docs/llm-connections.md) page for details on configuring you agents' connections to models, even ones running locally!
 
-- **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](https://docs.crewai.com/concepts/crews) or precise [Flows](https://docs.crewai.com/concepts/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.
+![CrewAI Mind Map](./docs/crewAI-mindmap.png "CrewAI Mind Map")
 
 ## Examples
+You can test different real life examples of AI crews [in the examples repo](https://github.com/joaomdmoura/crewAI-examples?tab=readme-ov-file)
 
-You can test different real life examples of AI crews in the [CrewAI-examples repo](https://github.com/crewAIInc/crewAI-examples?tab=readme-ov-file):
+### Code
+- [Trip Planner](https://github.com/joaomdmoura/crewAI-examples/tree/main/trip_planner)
+- [Stock Analysis](https://github.com/joaomdmoura/crewAI-examples/tree/main/stock_analysis)
+- [Landing Page Generator](https://github.com/joaomdmoura/crewAI-examples/tree/main/landing_page_generator)
+- [Having Human input on the execution](./docs/how-to/Human-Input-on-Execution.md)
 
-- [Landing Page Generator](https://github.com/crewAIInc/crewAI-examples/tree/main/landing_page_generator)
-- [Having Human input on the execution](https://docs.crewai.com/how-to/Human-Input-on-Execution)
-- [Trip Planner](https://github.com/crewAIInc/crewAI-examples/tree/main/trip_planner)
-- [Stock Analysis](https://github.com/crewAIInc/crewAI-examples/tree/main/stock_analysis)
+### Video
+#### Quick Tutorial
+[![CrewAI Tutorial](https://img.youtube.com/vi/tnejrr-0a94/0.jpg)](https://www.youtube.com/watch?v=tnejrr-0a94 "CrewAI Tutorial")
 
-### Quick Tutorial
+#### Trip Planner
+[![Trip Planner](https://img.youtube.com/vi/xis7rWp-hjs/0.jpg)](https://www.youtube.com/watch?v=xis7rWp-hjs "Trip Planner")
 
-[![CrewAI Tutorial](https://img.youtube.com/vi/tnejrr-0a94/maxresdefault.jpg)](https://www.youtube.com/watch?v=tnejrr-0a94 "CrewAI Tutorial")
-
-### Write Job Descriptions
-
-[Check out code for this example](https://github.com/crewAIInc/crewAI-examples/tree/main/job-posting) or watch a video below:
-
-[![Jobs postings](https://img.youtube.com/vi/u98wEMz-9to/maxresdefault.jpg)](https://www.youtube.com/watch?v=u98wEMz-9to "Jobs postings")
-
-### Trip Planner
-
-[Check out code for this example](https://github.com/crewAIInc/crewAI-examples/tree/main/trip_planner) or watch a video below:
-
-[![Trip Planner](https://img.youtube.com/vi/xis7rWp-hjs/maxresdefault.jpg)](https://www.youtube.com/watch?v=xis7rWp-hjs "Trip Planner")
-
-### Stock Analysis
-
-[Check out code for this example](https://github.com/crewAIInc/crewAI-examples/tree/main/stock_analysis) or watch a video below:
-
-[![Stock Analysis](https://img.youtube.com/vi/e0Uj4yWdaAg/maxresdefault.jpg)](https://www.youtube.com/watch?v=e0Uj4yWdaAg "Stock Analysis")
-
-### Using Crews and Flows Together
-
-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:
-
-```python
-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:
-1. Use Python code for basic data operations
-2. Create and execute Crews as steps in your workflow
-3. Use Flow decorators to manage the sequence of operations
-4. Implement conditional branching based on Crew results
+#### Stock Analysis
+[![Stock Analysis](https://img.youtube.com/vi/e0Uj4yWdaAg/0.jpg)](https://www.youtube.com/watch?v=e0Uj4yWdaAg "Stock Analysis")
 
 ## Connecting Your Crew to a Model
 
-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.
+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](https://docs.crewai.com/how-to/LLM-Connections/) page for details on configuring you agents' connections to models.
+Please refer to the [Connect crewAI to LLMs](./docs/how-to/llm-connections.md) page for details on configuring you agents' connections to models.
 
 ## How CrewAI Compares
 
-**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](https://github.com/crewAIInc/crewAI-examples/tree/main/Notebooks/CrewAI%20Flows%20%26%20Langgraph/QA%20Agent)) while achieving higher evaluation scores with faster completion times in certain coding tasks, like in this example ([detailed analysis](https://github.com/crewAIInc/crewAI-examples/blob/main/Notebooks/CrewAI%20Flows%20%26%20Langgraph/Coding%20Assistant/coding_assistant_eval.ipynb)).*
-
-- **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.
+- **Autogen**: While Autogen excels in 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's Advantage**: CrewAI is built with production in mind. It offers the flexibility of Autogen's conversational agents and the structured process approach of ChatDev, but without the rigidity. CrewAI's processes are designed to be dynamic and adaptable, fitting seamlessly into both development and production workflows.
+
 ## Contribution
 
 CrewAI is open-source and we welcome contributions. If you're looking to contribute, please:
@@ -525,16 +189,14 @@ CrewAI is open-source and we welcome contributions. If you're looking to contrib
 - We appreciate your input!
 
 ### Installing Dependencies
-
 ```bash
-uv lock
-uv sync
+poetry lock
+poetry install
 ```
 
 ### Virtual Env
-
 ```bash
-uv venv
+poetry shell
 ```
 
 ### Pre-commit hooks
@@ -544,160 +206,23 @@ pre-commit install
 ```
 
 ### Running Tests
-
 ```bash
-uv run pytest .
-```
-
-### Running static type checks
-
-```bash
-uvx mypy src
+poetry run pytest
 ```
 
 ### Packaging
-
 ```bash
-uv build
+poetry build
 ```
 
 ### Installing Locally
-
 ```bash
 pip install dist/*.tar.gz
 ```
 
-## Telemetry
-
-CrewAI 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.
+## Hire CrewAI
+We're a company developing crewAI and crewAI Enterprise, we for a limited time are offer consulting with selected customers, to get them early access to our enterprise solution
+If you are interested on having access to it and hiring weekly hours with our team, feel free to email us at [sales@crewai.io](mailto:sales@crewai.io)
 
 ## License
-
-CrewAI is released under the [MIT License](https://github.com/crewAIInc/crewAI/blob/main/LICENSE).
-
-
-## Frequently Asked Questions (FAQ)
-
-### General
-- [What exactly is CrewAI?](#q-what-exactly-is-crewai)
-- [How do I install CrewAI?](#q-how-do-i-install-crewai)
-- [Does CrewAI depend on LangChain?](#q-does-crewai-depend-on-langchain)
-- [Is CrewAI open-source?](#q-is-crewai-open-source)
-- [Does CrewAI collect data from users?](#q-does-crewai-collect-data-from-users)
-
-### Features and Capabilities
-- [Can CrewAI handle complex use cases?](#q-can-crewai-handle-complex-use-cases)
-- [Can I use CrewAI with local AI models?](#q-can-i-use-crewai-with-local-ai-models)
-- [What makes Crews different from Flows?](#q-what-makes-crews-different-from-flows)
-- [How is CrewAI better than LangChain?](#q-how-is-crewai-better-than-langchain)
-- [Does CrewAI support fine-tuning or training custom models?](#q-does-crewai-support-fine-tuning-or-training-custom-models)
-
-### Resources and Community
-- [Where can I find real-world CrewAI examples?](#q-where-can-i-find-real-world-crewai-examples)
-- [How can I contribute to CrewAI?](#q-how-can-i-contribute-to-crewai)
-
-### Enterprise Features
-- [What additional features does CrewAI Enterprise offer?](#q-what-additional-features-does-crewai-enterprise-offer)
-- [Is CrewAI Enterprise available for cloud and on-premise deployments?](#q-is-crewai-enterprise-available-for-cloud-and-on-premise-deployments)
-- [Can I try CrewAI Enterprise for free?](#q-can-i-try-crewai-enterprise-for-free)
-
-
-
-### Q: What exactly is CrewAI?
-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.
-
-### Q: How do I install CrewAI?
-A: Install CrewAI using pip:
-```shell
-pip install crewai
-```
-For additional tools, use:
-```shell
-pip install 'crewai[tools]'
-```
-### Q: Does CrewAI depend on LangChain?
-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.
-
-### Q: Can CrewAI handle complex use cases?
-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.
-
-### Q: Can I use CrewAI with local AI models?
-A: Absolutely! CrewAI supports various language models, including local ones. Tools like Ollama and LM Studio allow seamless integration. Check the [LLM Connections documentation](https://docs.crewai.com/how-to/LLM-Connections/) for more details.
-
-### Q: What makes Crews different from Flows?
-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.
-
-### Q: How is CrewAI better than LangChain?
-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.
-
-### Q: Is CrewAI open-source?
-A: Yes, CrewAI is open-source and actively encourages community contributions and collaboration.
-
-### Q: Does CrewAI collect data from users?
-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.
-
-### Q: Where can I find real-world CrewAI examples?
-A: Check out practical examples in the [CrewAI-examples repository](https://github.com/crewAIInc/crewAI-examples), covering use cases like trip planners, stock analysis, and job postings.
-
-### Q: How can I contribute to CrewAI?
-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.
-
-### Q: What additional features does CrewAI Enterprise offer?
-A: CrewAI Enterprise provides advanced features such as a unified control plane, real-time observability, secure integrations, advanced security, actionable insights, and dedicated 24/7 enterprise support.
-
-### Q: Is CrewAI Enterprise available for cloud and on-premise deployments?
-A: Yes, CrewAI Enterprise supports both cloud-based and on-premise deployment options, allowing enterprises to meet their specific security and compliance requirements.
-
-### Q: Can I try CrewAI Enterprise for free?
-A: Yes, you can explore part of the CrewAI Enterprise Suite by accessing the [Crew Control Plane](https://app.crewai.com) for free.
-
-### Q: Does CrewAI support fine-tuning or training custom models?
-A: Yes, CrewAI can integrate with custom-trained or fine-tuned models, allowing you to enhance your agents with domain-specific knowledge and accuracy.
-
-### Q: Can CrewAI agents interact with external tools and APIs?
-A: Absolutely! CrewAI agents can easily integrate with external tools, APIs, and databases, empowering them to leverage real-world data and resources.
-
-### Q: Is CrewAI suitable for production environments?
-A: Yes, CrewAI is explicitly designed with production-grade standards, ensuring reliability, stability, and scalability for enterprise deployments.
-
-### Q: How scalable is CrewAI?
-A: CrewAI is highly scalable, supporting simple automations and large-scale enterprise workflows involving numerous agents and complex tasks simultaneously.
-
-### Q: Does CrewAI offer debugging and monitoring tools?
-A: Yes, CrewAI Enterprise includes advanced debugging, tracing, and real-time observability features, simplifying the management and troubleshooting of your automations.
-
-### Q: What programming languages does CrewAI support?
-A: CrewAI is primarily Python-based but easily integrates with services and APIs written in any programming language through its flexible API integration capabilities.
-
-### Q: Does CrewAI offer educational resources for beginners?
-A: Yes, CrewAI provides extensive beginner-friendly tutorials, courses, and documentation through learn.crewai.com, supporting developers at all skill levels.
-
-### Q: Can CrewAI automate human-in-the-loop workflows?
-A: Yes, CrewAI fully supports human-in-the-loop workflows, allowing seamless collaboration between human experts and AI agents for enhanced decision-making.
+CrewAI is released under the MIT License

crewAI.excalidraw

@@ -1463,11 +1463,11 @@
       "locked": false,
       "fontSize": 20,
       "fontFamily": 3,
-      "text": "Agents have the innate ability of\nreach out to another to delegate\nwork or ask questions.",
+      "text": "Agents have the inert ability of\nreach out to another to delegate\nwork or ask questions.",
       "textAlign": "right",
       "verticalAlign": "top",
       "containerId": null,
-      "originalText": "Agents have the innate ability of\nreach out to another to delegate\nwork or ask questions.",
+      "originalText": "Agents have the inert ability of\nreach out to another to delegate\nwork or ask questions.",
       "lineHeight": 1.2,
       "baseline": 68
     },
@@ -1734,4 +1734,4 @@
     "viewBackgroundColor": "#ffffff"
   },
   "files": {}
-}
+}

docs/changelog.mdx

@@ -1,187 +0,0 @@
----
-title: Changelog
-description: View the latest updates and changes to CrewAI
-icon: timeline
----
-
-<Update label="2025-03-17" description="v0.108.0">
-  **Features**
-  - Converted tabs to spaces in `crew.py` template
-  - Enhanced LLM Streaming Response Handling and Event System
-  - Included `model_name`
-  - Enhanced Event Listener with rich visualization and improved logging
-  - Added fingerprints
-
-  **Bug Fixes**
-  - Fixed Mistral issues
-  - Fixed a bug in documentation
-  - Fixed type check error in fingerprint property
-
-  **Documentation Updates**
-  - Improved tool documentation
-  - Updated installation guide for the `uv` tool package
-  - Added instructions for upgrading crewAI with the `uv` tool
-  - Added documentation for `ApifyActorsTool`
-</Update>
-
-<Update label="2025-03-10" description="v0.105.0">
-  **Core Improvements & Fixes**
-  - Fixed issues with missing template variables and user memory configuration
-  - Improved async flow support and addressed agent response formatting
-  - Enhanced memory reset functionality and fixed CLI memory commands
-  - Fixed type issues, tool calling properties, and telemetry decoupling
-
-  **New Features & Enhancements**
-  - Added Flow state export and improved state utilities
-  - Enhanced agent knowledge setup with optional crew embedder
-  - Introduced event emitter for better observability and LLM call tracking
-  - Added support for Python 3.10 and ChatOllama from langchain_ollama
-  - Integrated context window size support for the o3-mini model
-  - Added support for multiple router calls
-
-  **Documentation & Guides**
-  - Improved documentation layout and hierarchical structure
-  - Added QdrantVectorSearchTool guide and clarified event listener usage
-  - Fixed typos in prompts and updated Amazon Bedrock model listings
-</Update>
-
-<Update label="2025-02-12" description="v0.102.0">
-  **Core Improvements & Fixes**
-  - Enhanced LLM Support: Improved structured LLM output, parameter handling, and formatting for Anthropic models
-  - Crew & Agent Stability: Fixed issues with cloning agents/crews using knowledge sources, multiple task outputs in conditional tasks, and ignored Crew task callbacks
-  - Memory & Storage Fixes: Fixed short-term memory handling with Bedrock, ensured correct embedder initialization, and added a reset memories function in the crew class
-  - Training & Execution Reliability: Fixed broken training and interpolation issues with dict and list input types
-
-  **New Features & Enhancements**
-  - Advanced Knowledge Management: Improved naming conventions and enhanced embedding configuration with custom embedder support
-  - Expanded Logging & Observability: Added JSON format support for logging and integrated MLflow tracing documentation
-  - Data Handling Improvements: Updated excel_knowledge_source.py to process multi-tab files
-  - General Performance & Codebase Clean-Up: Streamlined enterprise code alignment and resolved linting issues
-  - Adding new tool: `QdrantVectorSearchTool`
-
-  **Documentation & Guides**
-  - Updated AI & Memory Docs: Improved Bedrock, Google AI, and long-term memory documentation
-  - Task & Workflow Clarity: Added "Human Input" row to Task Attributes, Langfuse guide, and FileWriterTool documentation
-  - Fixed Various Typos & Formatting Issues
-</Update>
-
-<Update label="2025-01-28" description="v0.100.0">
-  **Features**
-  - Add Composio docs
-  - Add SageMaker as a LLM provider
-  
-  **Fixes**
-  - Overall LLM connection issues
-  - Using safe accessors on training
-  - Add version check to crew_chat.py
-  
-  **Documentation**
-  - New docs for crewai chat
-  - Improve formatting and clarity in CLI and Composio Tool docs
-</Update>
-
-<Update label="2025-01-20" description="v0.98.0">
-  **Features**
-  - Conversation crew v1
-  - Add unique ID to flow states
-  - Add @persist decorator with FlowPersistence interface
-  
-  **Integrations**
-  - Add SambaNova integration
-  - Add NVIDIA NIM provider in cli
-  - Introducing VoyageAI
-  
-  **Fixes**
-  - Fix API Key Behavior and Entity Handling in Mem0 Integration
-  - Fixed core invoke loop logic and relevant tests
-  - Make tool inputs actual objects and not strings
-  - Add important missing parts to creating tools
-  - Drop litellm version to prevent windows issue
-  - Before kickoff if inputs are none
-  - Fixed typos, nested pydantic model issue, and docling issues
-</Update>
-
-<Update label="2025-01-04" description="v0.95.0">
-  **New Features**
-  - Adding Multimodal Abilities to Crew
-  - Programatic Guardrails
-  - HITL multiple rounds
-  - Gemini 2.0 Support
-  - CrewAI Flows Improvements
-  - Add Workflow Permissions
-  - Add support for langfuse with litellm
-  - Portkey Integration with CrewAI
-  - Add interpolate_only method and improve error handling
-  - Docling Support
-  - Weviate Support
-  
-  **Fixes**
-  - output_file not respecting system path
-  - disk I/O error when resetting short-term memory
-  - CrewJSONEncoder now accepts enums
-  - Python max version
-  - Interpolation for output_file in Task
-  - Handle coworker role name case/whitespace properly
-  - Add tiktoken as explicit dependency and document Rust requirement
-  - Include agent knowledge in planning process
-  - Change storage initialization to None for KnowledgeStorage
-  - Fix optional storage checks
-  - include event emitter in flows
-  - Docstring, Error Handling, and Type Hints Improvements
-  - Suppressed userWarnings from litellm pydantic issues
-</Update>
-
-<Update label="2024-12-05" description="v0.86.0">
-  **Changes**
-  - Remove all references to pipeline and pipeline router
-  - Add Nvidia NIM as provider in Custom LLM
-  - Add knowledge demo + improve knowledge docs
-  - Add HITL multiple rounds of followup
-  - New docs about yaml crew with decorators
-  - Simplify template crew
-</Update>
-
-<Update label="2024-12-04" description="v0.85.0">
-  **Features**
-  - Added knowledge to agent level
-  - Feat/remove langchain
-  - Improve typed task outputs
-  - Log in to Tool Repository on crewai login
-  
-  **Fixes**
-  - Fixes issues with result as answer not properly exiting LLM loop
-  - Fix missing key name when running with ollama provider
-  - Fix spelling issue found
-  
-  **Documentation**
-  - Update readme for running mypy
-  - Add knowledge to mint.json
-  - Update Github actions
-  - Update Agents docs to include two approaches for creating an agent
-  - Improvements to LLM Configuration and Usage
-</Update>
-
-<Update label="2024-11-25" description="v0.83.0">
-  **New Features**
-  - New before_kickoff and after_kickoff crew callbacks
-  - Support to pre-seed agents with Knowledge
-  - Add support for retrieving user preferences and memories using Mem0
-  
-  **Fixes**
-  - Fix Async Execution
-  - Upgrade chroma and adjust embedder function generator
-  - Update CLI Watson supported models + docs
-  - Reduce level for Bandit
-  - Fixing all tests
-  
-  **Documentation**
-  - Update Docs
-</Update>
-
-<Update label="2024-11-13" description="v0.80.0">
-  **Fixes**
-  - Fixing Tokens callback replacement bug
-  - Fixing Step callback issue
-  - Add cached prompt tokens info on usage metrics
-  - Fix crew_train_success test
-</Update>

docs/concepts/agents.mdx

@@ -1,357 +0,0 @@
----
-title: Agents
-description: Detailed guide on creating and managing agents within the CrewAI framework.
-icon: robot
----
-
-## Overview of an Agent
-
-In the CrewAI framework, an `Agent` is an autonomous unit that can:
-- Perform specific tasks
-- Make decisions based on its role and goal
-- Use tools to accomplish objectives
-- Communicate and collaborate with other agents
-- Maintain memory of interactions
-- Delegate tasks when allowed
-
-<Tip>
-Think of an agent as a specialized team member with specific skills, expertise, and responsibilities. For example, a `Researcher` agent might excel at gathering and analyzing information, while a `Writer` agent might be better at creating content.
-</Tip>
-
-<Note type="info" title="Enterprise Enhancement: Visual Agent Builder">
-CrewAI Enterprise includes a Visual Agent Builder that simplifies agent creation and configuration without writing code. Design your agents visually and test them in real-time.
-
-![Visual Agent Builder Screenshot](../images/enterprise/crew-studio-quickstart)
-
-The Visual Agent Builder enables:
-- Intuitive agent configuration with form-based interfaces
-- Real-time testing and validation
-- Template library with pre-configured agent types
-- Easy customization of agent attributes and behaviors
-</Note>
-
-## Agent Attributes
-
-| Attribute                               | Parameter                | Type                          | Description                                                                                                          |
-| :-------------------------------------- | :----------------------- | :---------------------------- | :------------------------------------------------------------------------------------------------------------------- |
-| **Role**                                | `role`                   | `str`                         | Defines the agent's function and expertise within the crew.                                                           |
-| **Goal**                                | `goal`                   | `str`                         | The individual objective that guides the agent's decision-making.                                                     |
-| **Backstory**                           | `backstory`              | `str`                         | Provides context and personality to the agent, enriching interactions.                                                |
-| **LLM** _(optional)_                    | `llm`                    | `Union[str, LLM, Any]`        | Language model that powers the agent. Defaults to the model specified in `OPENAI_MODEL_NAME` or "gpt-4".              |
-| **Tools** _(optional)_                  | `tools`                  | `List[BaseTool]`              | Capabilities or functions available to the agent. Defaults to an empty list.                                          |
-| **Function Calling LLM** _(optional)_   | `function_calling_llm`   | `Optional[Any]`               | Language model for tool calling, overrides crew's LLM if specified.                                                   |
-| **Max Iterations** _(optional)_         | `max_iter`               | `int`                         | Maximum iterations before the agent must provide its best answer. Default is 20.                                      |
-| **Max RPM** _(optional)_                | `max_rpm`                | `Optional[int]`               | Maximum requests per minute to avoid rate limits.                                                                     |
-| **Max Execution Time** _(optional)_     | `max_execution_time`     | `Optional[int]`               | Maximum time (in seconds) for task execution.                                                                         |
-| **Memory** _(optional)_                 | `memory`                 | `bool`                        | Whether the agent should maintain memory of interactions. Default is True.                                            |
-| **Verbose** _(optional)_                | `verbose`                | `bool`                        | Enable detailed execution logs for debugging. Default is False.                                                       |
-| **Allow Delegation** _(optional)_       | `allow_delegation`       | `bool`                        | Allow the agent to delegate tasks to other agents. Default is False.                                                  |
-| **Step Callback** _(optional)_          | `step_callback`          | `Optional[Any]`               | Function called after each agent step, overrides crew callback.                                                       |
-| **Cache** _(optional)_                  | `cache`                  | `bool`                        | Enable caching for tool usage. Default is True.                                                                       |
-| **System Template** _(optional)_        | `system_template`        | `Optional[str]`               | Custom system prompt template for the agent.                                                                          |
-| **Prompt Template** _(optional)_        | `prompt_template`        | `Optional[str]`               | Custom prompt template for the agent.                                                                                 |
-| **Response Template** _(optional)_      | `response_template`      | `Optional[str]`               | Custom response template for the agent.                                                                               |
-| **Allow Code Execution** _(optional)_   | `allow_code_execution`   | `Optional[bool]`              | Enable code execution for the agent. Default is False.                                                                |
-| **Max Retry Limit** _(optional)_        | `max_retry_limit`        | `int`                         | Maximum number of retries when an error occurs. Default is 2.                                                         |
-| **Respect Context Window** _(optional)_ | `respect_context_window` | `bool`                        | Keep messages under context window size by summarizing. Default is True.                                              |
-| **Code Execution Mode** _(optional)_    | `code_execution_mode`    | `Literal["safe", "unsafe"]`   | Mode for code execution: 'safe' (using Docker) or 'unsafe' (direct). Default is 'safe'.                               |
-| **Embedder** _(optional)_               | `embedder`               | `Optional[Dict[str, Any]]`    | Configuration for the embedder used by the agent.                                                                     |
-| **Knowledge Sources** _(optional)_      | `knowledge_sources`      | `Optional[List[BaseKnowledgeSource]]` | Knowledge sources available to the agent.                                                                     |
-| **Use System Prompt** _(optional)_      | `use_system_prompt`      | `Optional[bool]`              | Whether to use system prompt (for o1 model support). Default is True.                                                 |
-
-## Creating Agents
-
-There are two ways to create agents in CrewAI: using **YAML configuration (recommended)** or defining them **directly in code**.
-
-### YAML Configuration (Recommended)
-
-Using YAML configuration provides a cleaner, more maintainable way to define agents. We strongly recommend using this approach in your CrewAI projects.
-
-After creating your CrewAI project as outlined in the [Installation](/installation) section, navigate to the `src/latest_ai_development/config/agents.yaml` file and modify the template to match your requirements.
-
-<Note>
-Variables in your YAML files (like `{topic}`) will be replaced with values from your inputs when running the crew:
-```python Code
-crew.kickoff(inputs={'topic': 'AI Agents'})
-```
-</Note>
-
-Here's an example of how to configure agents using YAML:
-
-```yaml agents.yaml
-# src/latest_ai_development/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.
-```
-
-To use this YAML configuration in your code, create a crew class that inherits from `CrewBase`:
-
-```python Code
-# src/latest_ai_development/crew.py
-from crewai import Agent, Crew, Process
-from crewai.project import CrewBase, agent, crew
-from crewai_tools import SerperDevTool
-
-@CrewBase
-class LatestAiDevelopmentCrew():
-  """LatestAiDevelopment crew"""
-
-  agents_config = "config/agents.yaml"
-
-  @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
-    )
-```
-
-<Note>
-The names you use in your YAML files (`agents.yaml`) should match the method names in your Python code.
-</Note>
-
-### Direct Code Definition
-
-You can create agents directly in code by instantiating the `Agent` class. Here's a comprehensive example showing all available parameters:
-
-```python Code
-from crewai import Agent
-from crewai_tools import SerperDevTool
-
-# Create an agent with all available parameters
-agent = Agent(
-    role="Senior Data Scientist",
-    goal="Analyze and interpret complex datasets to provide actionable insights",
-    backstory="With over 10 years of experience in data science and machine learning, "
-              "you excel at finding patterns in complex datasets.",
-    llm="gpt-4",  # Default: OPENAI_MODEL_NAME or "gpt-4"
-    function_calling_llm=None,  # Optional: Separate LLM for tool calling
-    memory=True,  # Default: True
-    verbose=False,  # Default: False
-    allow_delegation=False,  # Default: False
-    max_iter=20,  # Default: 20 iterations
-    max_rpm=None,  # Optional: Rate limit for API calls
-    max_execution_time=None,  # Optional: Maximum execution time in seconds
-    max_retry_limit=2,  # Default: 2 retries on error
-    allow_code_execution=False,  # Default: False
-    code_execution_mode="safe",  # Default: "safe" (options: "safe", "unsafe")
-    respect_context_window=True,  # Default: True
-    use_system_prompt=True,  # Default: True
-    tools=[SerperDevTool()],  # Optional: List of tools
-    knowledge_sources=None,  # Optional: List of knowledge sources
-    embedder=None,  # Optional: Custom embedder configuration
-    system_template=None,  # Optional: Custom system prompt template
-    prompt_template=None,  # Optional: Custom prompt template
-    response_template=None,  # Optional: Custom response template
-    step_callback=None,  # Optional: Callback function for monitoring
-)
-```
-
-Let's break down some key parameter combinations for common use cases:
-
-#### Basic Research Agent
-```python Code
-research_agent = Agent(
-    role="Research Analyst",
-    goal="Find and summarize information about specific topics",
-    backstory="You are an experienced researcher with attention to detail",
-    tools=[SerperDevTool()],
-    verbose=True  # Enable logging for debugging
-)
-```
-
-#### Code Development Agent
-```python Code
-dev_agent = Agent(
-    role="Senior Python Developer",
-    goal="Write and debug Python code",
-    backstory="Expert Python developer with 10 years of experience",
-    allow_code_execution=True,
-    code_execution_mode="safe",  # Uses Docker for safety
-    max_execution_time=300,  # 5-minute timeout
-    max_retry_limit=3  # More retries for complex code tasks
-)
-```
-
-#### Long-Running Analysis Agent
-```python Code
-analysis_agent = Agent(
-    role="Data Analyst",
-    goal="Perform deep analysis of large datasets",
-    backstory="Specialized in big data analysis and pattern recognition",
-    memory=True,
-    respect_context_window=True,
-    max_rpm=10,  # Limit API calls
-    function_calling_llm="gpt-4o-mini"  # Cheaper model for tool calls
-)
-```
-
-#### Custom Template Agent
-```python Code
-custom_agent = Agent(
-    role="Customer Service Representative",
-    goal="Assist customers with their inquiries",
-    backstory="Experienced in customer support with a focus on satisfaction",
-    system_template="""<|start_header_id|>system<|end_header_id|>
-                        {{ .System }}<|eot_id|>""",
-    prompt_template="""<|start_header_id|>user<|end_header_id|>
-                        {{ .Prompt }}<|eot_id|>""",
-    response_template="""<|start_header_id|>assistant<|end_header_id|>
-                        {{ .Response }}<|eot_id|>""",
-)
-```
-
-### Parameter Details
-
-#### Critical Parameters
-- `role`, `goal`, and `backstory` are required and shape the agent's behavior
-- `llm` determines the language model used (default: OpenAI's GPT-4)
-
-#### Memory and Context
-- `memory`: Enable to maintain conversation history
-- `respect_context_window`: Prevents token limit issues
-- `knowledge_sources`: Add domain-specific knowledge bases
-
-#### Execution Control
-- `max_iter`: Maximum attempts before giving best answer
-- `max_execution_time`: Timeout in seconds
-- `max_rpm`: Rate limiting for API calls
-- `max_retry_limit`: Retries on error
-
-#### Code Execution
-- `allow_code_execution`: Must be True to run code
-- `code_execution_mode`:
-  - `"safe"`: Uses Docker (recommended for production)
-  - `"unsafe"`: Direct execution (use only in trusted environments)
-
-#### Templates
-- `system_template`: Defines agent's core behavior
-- `prompt_template`: Structures input format
-- `response_template`: Formats agent responses
-
-<Note>
-When using custom templates, you can use variables like `{role}`, `{goal}`, and `{input}` in your templates. These will be automatically populated during execution.
-</Note>
-
-## Agent Tools
-
-Agents can be equipped with various tools to enhance their capabilities. CrewAI supports tools from:
-- [CrewAI Toolkit](https://github.com/joaomdmoura/crewai-tools)
-- [LangChain Tools](https://python.langchain.com/docs/integrations/tools)
-
-Here's how to add tools to an agent:
-
-```python Code
-from crewai import Agent
-from crewai_tools import SerperDevTool, WikipediaTools
-
-# Create tools
-search_tool = SerperDevTool()
-wiki_tool = WikipediaTools()
-
-# Add tools to agent
-researcher = Agent(
-    role="AI Technology Researcher",
-    goal="Research the latest AI developments",
-    tools=[search_tool, wiki_tool],
-    verbose=True
-)
-```
-
-## Agent Memory and Context
-
-Agents can maintain memory of their interactions and use context from previous tasks. This is particularly useful for complex workflows where information needs to be retained across multiple tasks.
-
-```python Code
-from crewai import Agent
-
-analyst = Agent(
-    role="Data Analyst",
-    goal="Analyze and remember complex data patterns",
-    memory=True,  # Enable memory
-    verbose=True
-)
-```
-
-<Note>
-When `memory` is enabled, the agent will maintain context across multiple interactions, improving its ability to handle complex, multi-step tasks.
-</Note>
-
-## Important Considerations and Best Practices
-
-### Security and Code Execution
-- When using `allow_code_execution`, be cautious with user input and always validate it
-- Use `code_execution_mode: "safe"` (Docker) in production environments
-- Consider setting appropriate `max_execution_time` limits to prevent infinite loops
-
-### Performance Optimization
-- Use `respect_context_window: true` to prevent token limit issues
-- Set appropriate `max_rpm` to avoid rate limiting
-- Enable `cache: true` to improve performance for repetitive tasks
-- Adjust `max_iter` and `max_retry_limit` based on task complexity
-
-### Memory and Context Management
-- Use `memory: true` for tasks requiring historical context
-- Leverage `knowledge_sources` for domain-specific information
-- Configure `embedder_config` when using custom embedding models
-- Use custom templates (`system_template`, `prompt_template`, `response_template`) for fine-grained control over agent behavior
-
-### Agent Collaboration
-- Enable `allow_delegation: true` when agents need to work together
-- Use `step_callback` to monitor and log agent interactions
-- Consider using different LLMs for different purposes:
-  - Main `llm` for complex reasoning
-  - `function_calling_llm` for efficient tool usage
-
-### Model Compatibility
-- Set `use_system_prompt: false` for older models that don't support system messages
-- Ensure your chosen `llm` supports the features you need (like function calling)
-
-## Troubleshooting Common Issues
-
-1. **Rate Limiting**: If you're hitting API rate limits:
-   - Implement appropriate `max_rpm`
-   - Use caching for repetitive operations
-   - Consider batching requests
-
-2. **Context Window Errors**: If you're exceeding context limits:
-   - Enable `respect_context_window`
-   - Use more efficient prompts
-   - Clear agent memory periodically
-
-3. **Code Execution Issues**: If code execution fails:
-   - Verify Docker is installed for safe mode
-   - Check execution permissions
-   - Review code sandbox settings
-
-4. **Memory Issues**: If agent responses seem inconsistent:
-   - Verify memory is enabled
-   - Check knowledge source configuration
-   - Review conversation history management
-
-Remember that agents are most effective when configured according to their specific use case. Take time to understand your requirements and adjust these parameters accordingly.

docs/concepts/cli.mdx

@@ -1,211 +0,0 @@
----
-title: CLI
-description: Learn how to use the CrewAI CLI to interact with CrewAI.
-icon: terminal
----
-
-# CrewAI CLI Documentation
-
-The CrewAI CLI provides a set of commands to interact with CrewAI, allowing you to create, train, run, and manage crews & flows.
-
-## Installation
-
-To use the CrewAI CLI, make sure you have CrewAI installed:
-
-```shell Terminal
-pip install crewai
-```
-
-## Basic Usage
-
-The basic structure of a CrewAI CLI command is:
-
-```shell Terminal
-crewai [COMMAND] [OPTIONS] [ARGUMENTS]
-```
-
-## Available Commands
-
-### 1. Create
-
-Create a new crew or flow.
-
-```shell Terminal
-crewai create [OPTIONS] TYPE NAME
-```
-
-- `TYPE`: Choose between "crew" or "flow"
-- `NAME`: Name of the crew or flow
-
-Example:
-```shell Terminal
-crewai create crew my_new_crew
-crewai create flow my_new_flow
-```
-
-### 2. Version
-
-Show the installed version of CrewAI.
-
-```shell Terminal
-crewai version [OPTIONS]
-```
-
-- `--tools`: (Optional) Show the installed version of CrewAI tools
-
-Example:
-```shell Terminal
-crewai version
-crewai version --tools
-```
-
-### 3. Train
-
-Train the crew for a specified number of iterations.
-
-```shell Terminal
-crewai train [OPTIONS]
-```
-
-- `-n, --n_iterations INTEGER`: Number of iterations to train the crew (default: 5)
-- `-f, --filename TEXT`: Path to a custom file for training (default: "trained_agents_data.pkl")
-
-Example:
-```shell Terminal
-crewai train -n 10 -f my_training_data.pkl
-```
-
-### 4. Replay
-
-Replay the crew execution from a specific task.
-
-```shell Terminal
-crewai replay [OPTIONS]
-```
-
-- `-t, --task_id TEXT`: Replay the crew from this task ID, including all subsequent tasks
-
-Example:
-```shell Terminal    
-crewai replay -t task_123456
-```
-
-### 5. Log-tasks-outputs
-
-Retrieve your latest crew.kickoff() task outputs.
-
-```shell Terminal
-crewai log-tasks-outputs
-```
-
-### 6. Reset-memories
-
-Reset the crew memories (long, short, entity, latest_crew_kickoff_outputs).
-
-```shell Terminal
-crewai reset-memories [OPTIONS]
-```
-
-- `-l, --long`: Reset LONG TERM memory
-- `-s, --short`: Reset SHORT TERM memory
-- `-e, --entities`: Reset ENTITIES memory
-- `-k, --kickoff-outputs`: Reset LATEST KICKOFF TASK OUTPUTS
-- `-a, --all`: Reset ALL memories
-
-Example:
-```shell Terminal
-crewai reset-memories --long --short
-crewai reset-memories --all
-```
-
-### 7. Test
-
-Test the crew and evaluate the results.
-
-```shell Terminal
-crewai test [OPTIONS]
-```
-
-- `-n, --n_iterations INTEGER`: Number of iterations to test the crew (default: 3)
-- `-m, --model TEXT`: LLM Model to run the tests on the Crew (default: "gpt-4o-mini")
-
-Example:
-```shell Terminal    
-crewai test -n 5 -m gpt-3.5-turbo
-```
-
-### 8. Run
-
-Run the crew or flow.
-
-```shell Terminal
-crewai run
-```
-
-<Note>
-Starting from version 0.103.0, the `crewai run` command can be used to run both standard crews and flows. For flows, it automatically detects the type from pyproject.toml and runs the appropriate command. This is now the recommended way to run both crews and flows.
-</Note>
-
-<Note>
-Make sure to run these commands from the directory where your CrewAI project is set up. 
-Some commands may require additional configuration or setup within your project structure.
-</Note>
-
-### 9. Chat
-
-Starting in version `0.98.0`, when you run the `crewai chat` command, you start an interactive session with your crew. The AI assistant will guide you by asking for necessary inputs to execute the crew. Once all inputs are provided, the crew will execute its tasks.
-
-After receiving the results, you can continue interacting with the assistant for further instructions or questions.
-
-```shell Terminal
-crewai chat
-```
-<Note>
-Ensure you execute these commands from your CrewAI project's root directory.
-</Note>
-<Note>
-IMPORTANT: Set the `chat_llm` property in your `crew.py` file to enable this command.
-
-```python
-@crew
-def crew(self) -> Crew:
-    return Crew(
-        agents=self.agents,
-        tasks=self.tasks,
-        process=Process.sequential,
-        verbose=True,
-        chat_llm="gpt-4o",  # LLM for chat orchestration
-    )
-```
-</Note>
-
-### 10. API Keys
-
-When running ```crewai create crew``` command, the CLI will first show you the top 5 most common LLM providers and ask you to select one.
-
-Once you've selected an LLM provider, you will be prompted for API keys.
-
-#### Initial API key providers
-
-The CLI will initially prompt for API keys for the following services:
-
-* OpenAI
-* Groq
-* Anthropic
-* Google Gemini
-* SambaNova
-
-When you select a provider, the CLI will prompt you to enter your API key.
-
-#### Other Options
-
-If you select option 6, you will be able to select from a list of LiteLLM supported providers.
-
-When you select a provider, the CLI will prompt you to enter the Key name and the API key.
-
-See the following link for each provider's key name:
-
-* [LiteLLM Providers](https://docs.litellm.ai/docs/providers)
-
-
-

docs/concepts/collaboration.mdx

@@ -1,51 +0,0 @@
----
-title: Collaboration
-description: Exploring the dynamics of agent collaboration within the CrewAI framework, focusing on the newly integrated features for enhanced functionality.
-icon: screen-users
----
-
-## Collaboration Fundamentals      
-
-Collaboration in CrewAI is fundamental, enabling agents to combine their skills, share information, and assist each other in task execution, embodying a truly cooperative ecosystem.
-
-- **Information Sharing**: Ensures all agents are well-informed and can contribute effectively by sharing data and findings.
-- **Task Assistance**: Allows agents to seek help from peers with the required expertise for specific tasks.
-- **Resource Allocation**: Optimizes task execution through the efficient distribution and sharing of resources among agents.
-
-## Enhanced Attributes for Improved Collaboration
-
-The `Crew` class has been enriched with several attributes to support advanced functionalities:
-
-| Feature                                    | Description                                                                                                                                                                                                                  |
-|:-------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Language Model Management** (`manager_llm`, `function_calling_llm`) | Manages language models for executing tasks and tools. `manager_llm` is required for hierarchical processes, while `function_calling_llm` is optional with a default value for streamlined interactions.                    |
-| **Custom Manager Agent** (`manager_agent`) | Specifies a custom agent as the manager, replacing the default CrewAI manager.                                                                                                                                                |
-| **Process Flow** (`process`)           | Defines execution logic (e.g., sequential, hierarchical) for task distribution.                                                                                                                                                |
-| **Verbose Logging** (`verbose`)        | Provides detailed logging for monitoring and debugging. Accepts integer and boolean values to control verbosity level.                                                                                                       |
-| **Rate Limiting** (`max_rpm`)          | Limits requests per minute to optimize resource usage. Setting guidelines depend on task complexity and load.                                                                                                                 |
-| **Internationalization / Customization** (`prompt_file`) | Supports prompt customization for global usability. [Example of file](https://github.com/joaomdmoura/crewAI/blob/main/src/crewai/translations/en.json)                                                                                      |
-| **Callback and Telemetry** (`step_callback`, `task_callback`) | Enables step-wise and task-level execution monitoring and telemetry for performance analytics.                                                                                                                               |
-| **Crew Sharing** (`share_crew`)        | Allows sharing crew data with CrewAI for model improvement. Privacy implications and benefits should be considered.                                                                                                          |
-| **Usage Metrics** (`usage_metrics`)    | Logs all LLM usage metrics during task execution for performance insights.                                                                                                                           |
-| **Memory Usage** (`memory`)            | Enables memory for storing execution history, aiding in agent learning and task efficiency.                                                                                                                                  |
-| **Embedder Configuration** (`embedder`) | Configures the embedder for language understanding and generation, with support for provider customization.                                                                                                                   |
-| **Cache Management** (`cache`)         | Specifies whether to cache tool execution results, enhancing performance.                                                                                                                                                   |
-| **Output Logging** (`output_log_file`) | Defines the file path for logging crew execution output.                                                                                                                                                                      |
-| **Planning Mode** (`planning`)         | Enables action planning before task execution. Set `planning=True` to activate.                                                                                                                                              |
-| **Replay Feature** (`replay`)         | Provides CLI for listing tasks from the last run and replaying from specific tasks, aiding in task management and troubleshooting.                                                                                           |
-
-## Delegation (Dividing to Conquer)
-
-Delegation enhances functionality by allowing agents to intelligently assign tasks or seek help, thereby amplifying the crew's overall capability.
-
-## Implementing Collaboration and Delegation
-
-Setting up a crew involves defining the roles and capabilities of each agent. CrewAI seamlessly manages their interactions, ensuring efficient collaboration and delegation, with enhanced customization and monitoring features to adapt to various operational needs.
-
-## Example Scenario
-
-Consider a crew with a researcher agent tasked with data gathering and a writer agent responsible for compiling reports. The integration of advanced language model management and process flow attributes allows for more sophisticated interactions, such as the writer delegating complex research tasks to the researcher or querying specific information, thereby facilitating a seamless workflow.
-
-## Conclusion
-
-The integration of advanced attributes and functionalities into the CrewAI framework significantly enriches the agent collaboration ecosystem. These enhancements not only simplify interactions but also offer unprecedented flexibility and control, paving the way for sophisticated AI-driven solutions capable of tackling complex tasks through intelligent collaboration and delegation.

docs/concepts/crews.mdx

@@ -1,353 +0,0 @@
----
-title: Crews
-description: Understanding and utilizing crews in the crewAI framework with comprehensive attributes and functionalities.
-icon: people-group
----
-
-## What is a Crew?
-
-A crew in crewAI represents a collaborative group of agents working together to achieve a set of tasks. Each crew defines the strategy for task execution, agent collaboration, and the overall workflow.
-
-## Crew Attributes
-
-| Attribute                             | Parameters             | Description                                                                                                                                                                                                                                               |
-| :------------------------------------ | :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Tasks**                             | `tasks`                | A list of tasks assigned to the crew.                                                                                                                                                                                                                     |
-| **Agents**                            | `agents`               | A list of agents that are part of the crew.                                                                                                                                                                                                               |
-| **Process** _(optional)_              | `process`              | The process flow (e.g., sequential, hierarchical) the crew follows. Default is `sequential`.                                                                                                                                                              |
-| **Verbose** _(optional)_              | `verbose`              | The verbosity level for logging during execution. Defaults to `False`.                                                                                                                                                                                    |
-| **Manager LLM** _(optional)_          | `manager_llm`          | The language model used by the manager agent in a hierarchical process. **Required when using a hierarchical process.**                                                                                                                                   |
-| **Function Calling LLM** _(optional)_ | `function_calling_llm` | If passed, the crew will use this LLM to do function calling for tools for all agents in the crew. Each agent can have its own LLM, which overrides the crew's LLM for function calling.                                                                  |
-| **Config** _(optional)_               | `config`               | Optional configuration settings for the crew, in `Json` or `Dict[str, Any]` format.                                                                                                                                                                       |
-| **Max RPM** _(optional)_              | `max_rpm`              | Maximum requests per minute the crew adheres to during execution. Defaults to `None`.                                                                                                                                                                     |
-| **Memory** _(optional)_               | `memory`               | Utilized for storing execution memories (short-term, long-term, entity memory).                                                                                                                                                                           |
-| **Memory Config** _(optional)_        | `memory_config`        | Configuration for the memory provider to be used by the crew.                                                                                                                                                                                             |
-| **Cache** _(optional)_                | `cache`                | Specifies whether to use a cache for storing the results of tools' execution. Defaults to `True`.                                                                                                                                                         |
-| **Embedder** _(optional)_             | `embedder`             | Configuration for the embedder to be used by the crew. Mostly used by memory for now. Default is `{"provider": "openai"}`.                                                                                                                                |
-| **Step Callback** _(optional)_        | `step_callback`        | A function that is called after each step of every agent. This can be used to log the agent's actions or to perform other operations; it won't override the agent-specific `step_callback`.                                                               |
-| **Task Callback** _(optional)_        | `task_callback`        | A function that is called after the completion of each task. Useful for monitoring or additional operations post-task execution.                                                                                                                          |
-| **Share Crew** _(optional)_           | `share_crew`           | Whether you want to share the complete crew information and execution with the crewAI team to make the library better, and allow us to train models.                                                                                                      |
-| **Output Log File** _(optional)_      | `output_log_file`      | Set to True to save logs as logs.txt in the current directory or provide a file path. Logs will be in JSON format if the filename ends in .json, otherwise .txt. Defautls to `None`.                                                                      |
-| **Manager Agent** _(optional)_        | `manager_agent`        | `manager` sets a custom agent that will be used as a manager.                                                                                                                                                                                             |
-| **Prompt File** _(optional)_          | `prompt_file`          | Path to the prompt JSON file to be used for the crew.                                                                                                                                                                                                     |
-| **Planning** *(optional)*             | `planning`             | Adds planning ability to the Crew. When activated before each Crew iteration, all Crew data is sent to an AgentPlanner that will plan the tasks and this plan will be added to each task description.                                                     |
-| **Planning LLM** *(optional)*         | `planning_llm`         | The language model used by the AgentPlanner in a planning process.                                                                                                                                                                                        |
-
-<Tip>
-**Crew Max RPM**: The `max_rpm` attribute sets the maximum number of requests per minute the crew can perform to avoid rate limits and will override individual agents' `max_rpm` settings if you set it.
-</Tip>
-
-## Creating Crews
-
-There are two ways to create crews in CrewAI: using **YAML configuration (recommended)** or defining them **directly in code**.
-
-### YAML Configuration (Recommended)
-
-Using YAML configuration provides a cleaner, more maintainable way to define crews and is consistent with how agents and tasks are defined in CrewAI projects.
-
-After creating your CrewAI project as outlined in the [Installation](/installation) section, you can define your crew in a class that inherits from `CrewBase` and uses decorators to define agents, tasks, and the crew itself.
-
-#### Example Crew Class with Decorators
-
-```python code
-from crewai import Agent, Crew, Task, Process
-from crewai.project import CrewBase, agent, task, crew, before_kickoff, after_kickoff
-
-
-@CrewBase
-class YourCrewName:
-    """Description of your crew"""
-
-    # Paths to your YAML configuration files
-    # To see an example agent and task defined in YAML, checkout the following:
-    # - Task: https://docs.crewai.com/concepts/tasks#yaml-configuration-recommended
-    # - Agents: https://docs.crewai.com/concepts/agents#yaml-configuration-recommended
-    agents_config = 'config/agents.yaml' 
-    tasks_config = 'config/tasks.yaml' 
-
-    @before_kickoff
-    def prepare_inputs(self, inputs):
-        # Modify inputs before the crew starts
-        inputs['additional_data'] = "Some extra information"
-        return inputs
-
-    @after_kickoff
-    def process_output(self, output):
-        # Modify output after the crew finishes
-        output.raw += "\nProcessed after kickoff."
-        return output
-
-    @agent
-    def agent_one(self) -> Agent:
-        return Agent(
-            config=self.agents_config['agent_one'],
-            verbose=True
-        )
-
-    @agent
-    def agent_two(self) -> Agent:
-        return Agent(
-            config=self.agents_config['agent_two'],
-            verbose=True
-        )
-
-    @task
-    def task_one(self) -> Task:
-        return Task(
-            config=self.tasks_config['task_one']
-        )
-
-    @task
-    def task_two(self) -> Task:
-        return Task(
-            config=self.tasks_config['task_two']
-        )
-
-    @crew
-    def crew(self) -> Crew:
-        return Crew(
-            agents=self.agents,  # Automatically collected by the @agent decorator
-            tasks=self.tasks,    # Automatically collected by the @task decorator. 
-            process=Process.sequential,
-            verbose=True,
-        )
-```
-
-<Note>
-Tasks will be executed in the order they are defined.
-</Note>
-
-The `CrewBase` class, along with these decorators, automates the collection of agents and tasks, reducing the need for manual management.
-
-#### Decorators overview from `annotations.py`
-
-CrewAI provides several decorators in the `annotations.py` file that are used to mark methods within your crew class for special handling:
-
-- `@CrewBase`: Marks the class as a crew base class.
-- `@agent`: Denotes a method that returns an `Agent` object.
-- `@task`: Denotes a method that returns a `Task` object.
-- `@crew`: Denotes the method that returns the `Crew` object.
-- `@before_kickoff`: (Optional) Marks a method to be executed before the crew starts.
-- `@after_kickoff`: (Optional) Marks a method to be executed after the crew finishes.
-
-These decorators help in organizing your crew's structure and automatically collecting agents and tasks without manually listing them.
-
-### Direct Code Definition (Alternative)
-
-Alternatively, you can define the crew directly in code without using YAML configuration files.
-
-```python code
-from crewai import Agent, Crew, Task, Process
-from crewai_tools import YourCustomTool
-
-class YourCrewName:
-    def agent_one(self) -> Agent:
-        return Agent(
-            role="Data Analyst",
-            goal="Analyze data trends in the market",
-            backstory="An experienced data analyst with a background in economics",
-            verbose=True,
-            tools=[YourCustomTool()]
-        )
-
-    def agent_two(self) -> Agent:
-        return Agent(
-            role="Market Researcher",
-            goal="Gather information on market dynamics",
-            backstory="A diligent researcher with a keen eye for detail",
-            verbose=True
-        )
-
-    def task_one(self) -> Task:
-        return Task(
-            description="Collect recent market data and identify trends.",
-            expected_output="A report summarizing key trends in the market.",
-            agent=self.agent_one()
-        )
-
-    def task_two(self) -> Task:
-        return Task(
-            description="Research factors affecting market dynamics.",
-            expected_output="An analysis of factors influencing the market.",
-            agent=self.agent_two()
-        )
-
-    def crew(self) -> Crew:
-        return Crew(
-            agents=[self.agent_one(), self.agent_two()],
-            tasks=[self.task_one(), self.task_two()],
-            process=Process.sequential,
-            verbose=True
-        )
-```
-
-In this example:
-
-- Agents and tasks are defined directly within the class without decorators.
-- We manually create and manage the list of agents and tasks.
-- This approach provides more control but can be less maintainable for larger projects.
-
-## Crew Output
-
-The output of a crew in the CrewAI framework is encapsulated within the `CrewOutput` class.
-This class provides a structured way to access results of the crew's execution, including various formats such as raw strings, JSON, and Pydantic models.
-The `CrewOutput` includes the results from the final task output, token usage, and individual task outputs.
-
-### Crew Output Attributes
-
-| Attribute        | Parameters     | Type                       | Description                                                                                          |
-| :--------------- | :------------- | :------------------------- | :--------------------------------------------------------------------------------------------------- |
-| **Raw**          | `raw`          | `str`                      | The raw output of the crew. This is the default format for the output.                               |
-| **Pydantic**     | `pydantic`     | `Optional[BaseModel]`      | A Pydantic model object representing the structured output of the crew.                              |
-| **JSON Dict**    | `json_dict`    | `Optional[Dict[str, Any]]` | A dictionary representing the JSON output of the crew.                                               |
-| **Tasks Output** | `tasks_output` | `List[TaskOutput]`         | A list of `TaskOutput` objects, each representing the output of a task in the crew.                  |
-| **Token Usage**  | `token_usage`  | `Dict[str, Any]`           | A summary of token usage, providing insights into the language model's performance during execution. |
-
-### Crew Output Methods and Properties
-
-| Method/Property | Description                                                                                       |
-| :-------------- | :------------------------------------------------------------------------------------------------ |
-| **json**        | Returns the JSON string representation of the crew output if the output format is JSON.           |
-| **to_dict**     | Converts the JSON and Pydantic outputs to a dictionary.                                           |
-| \***\*str\*\*** | Returns the string representation of the crew output, prioritizing Pydantic, then JSON, then raw. |
-
-### Accessing Crew Outputs
-
-Once a crew has been executed, its output can be accessed through the `output` attribute of the `Crew` object. The `CrewOutput` class provides various ways to interact with and present this output.
-
-#### Example
-
-```python Code
-# Example crew execution
-crew = Crew(
-    agents=[research_agent, writer_agent],
-    tasks=[research_task, write_article_task],
-    verbose=True
-)
-
-crew_output = crew.kickoff()
-
-# Accessing the crew output
-print(f"Raw Output: {crew_output.raw}")
-if crew_output.json_dict:
-    print(f"JSON Output: {json.dumps(crew_output.json_dict, indent=2)}")
-if crew_output.pydantic:
-    print(f"Pydantic Output: {crew_output.pydantic}")
-print(f"Tasks Output: {crew_output.tasks_output}")
-print(f"Token Usage: {crew_output.token_usage}")
-```
-
-## Accessing Crew Logs
-
-You can see real time log of the crew execution, by setting `output_log_file` as a `True(Boolean)` or a `file_name(str)`. Supports logging of events as both `file_name.txt` and `file_name.json`.
-In case of `True(Boolean)` will save as `logs.txt`.
-
-In case of `output_log_file` is set as `False(Booelan)` or `None`, the logs will not be populated.
-
-```python Code
-# Save crew logs
-crew = Crew(output_log_file = True)  # Logs will be saved as logs.txt
-crew = Crew(output_log_file = file_name)  # Logs will be saved as file_name.txt
-crew = Crew(output_log_file = file_name.txt)  # Logs will be saved as file_name.txt
-crew = Crew(output_log_file = file_name.json)  # Logs will be saved as file_name.json
-```
-
-
-
-## Memory Utilization
-
-Crews can utilize memory (short-term, long-term, and entity memory) to enhance their execution and learning over time. This feature allows crews to store and recall execution memories, aiding in decision-making and task execution strategies.
-
-## Cache Utilization
-
-Caches can be employed to store the results of tools' execution, making the process more efficient by reducing the need to re-execute identical tasks.
-
-## Crew Usage Metrics
-
-After the crew execution, you can access the `usage_metrics` attribute to view the language model (LLM) usage metrics for all tasks executed by the crew. This provides insights into operational efficiency and areas for improvement.
-
-```python Code
-# Access the crew's usage metrics
-crew = Crew(agents=[agent1, agent2], tasks=[task1, task2])
-crew.kickoff()
-print(crew.usage_metrics)
-```
-
-## Crew Execution Process
-
-- **Sequential Process**: Tasks are executed one after another, allowing for a linear flow of work.
-- **Hierarchical Process**: A manager agent coordinates the crew, delegating tasks and validating outcomes before proceeding. **Note**: A `manager_llm` or `manager_agent` is required for this process and it's essential for validating the process flow.
-
-### Kicking Off a Crew
-
-Once your crew is assembled, initiate the workflow with the `kickoff()` method. This starts the execution process according to the defined process flow.
-
-```python Code
-# Start the crew's task execution
-result = my_crew.kickoff()
-print(result)
-```
-
-### Different Ways to Kick Off a Crew
-
-Once your crew is assembled, initiate the workflow with the appropriate kickoff method. CrewAI provides several methods for better control over the kickoff process: `kickoff()`, `kickoff_for_each()`, `kickoff_async()`, and `kickoff_for_each_async()`.
-
-- `kickoff()`: Starts the execution process according to the defined process flow.
-- `kickoff_for_each()`: Executes tasks sequentially for each provided input event or item in the collection.
-- `kickoff_async()`: Initiates the workflow asynchronously.
-- `kickoff_for_each_async()`: Executes tasks concurrently for each provided input event or item, leveraging asynchronous processing.
-
-```python Code
-# Start the crew's task execution
-result = my_crew.kickoff()
-print(result)
-
-# Example of using kickoff_for_each
-inputs_array = [{'topic': 'AI in healthcare'}, {'topic': 'AI in finance'}]
-results = my_crew.kickoff_for_each(inputs=inputs_array)
-for result in results:
-    print(result)
-
-# Example of using kickoff_async
-inputs = {'topic': 'AI in healthcare'}
-async_result = my_crew.kickoff_async(inputs=inputs)
-print(async_result)
-
-# Example of using kickoff_for_each_async
-inputs_array = [{'topic': 'AI in healthcare'}, {'topic': 'AI in finance'}]
-async_results = my_crew.kickoff_for_each_async(inputs=inputs_array)
-for async_result in async_results:
-    print(async_result)
-```
-
-These methods provide flexibility in how you manage and execute tasks within your crew, allowing for both synchronous and asynchronous workflows tailored to your needs.
-
-### Replaying from a Specific Task
-
-You can now replay from a specific task using our CLI command `replay`.
-
-The replay feature in CrewAI allows you to replay from a specific task using the command-line interface (CLI). By running the command `crewai replay -t <task_id>`, you can specify the `task_id` for the replay process.
-
-Kickoffs will now save the latest kickoffs returned task outputs locally for you to be able to replay from.
-
-### Replaying from a Specific Task Using the CLI
-
-To use the replay feature, follow these steps:
-
-1. Open your terminal or command prompt.
-2. Navigate to the directory where your CrewAI project is located.
-3. Run the following command:
-
-To view the latest kickoff task IDs, use:
-
-```shell
-crewai log-tasks-outputs
-```
-
-Then, to replay from a specific task, use:
-
-```shell
-crewai replay -t <task_id>
-```
-
-These commands let you replay from your latest kickoff tasks, still retaining context from previously executed tasks.

docs/concepts/event-listener.mdx

@@ -1,365 +0,0 @@
----
-title: 'Event Listeners'
-description: 'Tap into CrewAI events to build custom integrations and monitoring'
-icon: spinner
----
-
-# Event Listeners
-
-CrewAI provides a powerful event system that allows you to listen for and react to various events that occur during the execution of your Crew. This feature enables you to build custom integrations, monitoring solutions, logging systems, or any other functionality that needs to be triggered based on CrewAI's internal events.
-
-## How It Works
-
-CrewAI uses an event bus architecture to emit events throughout the execution lifecycle. The event system is built on the following components:
-
-1. **CrewAIEventsBus**: A singleton event bus that manages event registration and emission
-2. **BaseEvent**: Base class for all events in the system
-3. **BaseEventListener**: Abstract base class for creating custom event listeners
-
-When specific actions occur in CrewAI (like a Crew starting execution, an Agent completing a task, or a tool being used), the system emits corresponding events. You can register handlers for these events to execute custom code when they occur.
-
-<Note type="info" title="Enterprise Enhancement: Prompt Tracing">
-CrewAI Enterprise provides a built-in Prompt Tracing feature that leverages the event system to track, store, and visualize all prompts, completions, and associated metadata. This provides powerful debugging capabilities and transparency into your agent operations.
-
-![Prompt Tracing Dashboard](../images/enterprise/prompt-tracing.png)
-
-With Prompt Tracing you can:
-- View the complete history of all prompts sent to your LLM
-- Track token usage and costs
-- Debug agent reasoning failures
-- Share prompt sequences with your team
-- Compare different prompt strategies
-- Export traces for compliance and auditing
-</Note>
-
-## Creating a Custom Event Listener
-
-To create a custom event listener, you need to:
-
-1. Create a class that inherits from `BaseEventListener`
-2. Implement the `setup_listeners` method
-3. Register handlers for the events you're interested in
-4. Create an instance of your listener in the appropriate file
-
-Here's a simple example of a custom event listener class:
-
-```python
-from crewai.utilities.events import (
-    CrewKickoffStartedEvent,
-    CrewKickoffCompletedEvent,
-    AgentExecutionCompletedEvent,
-)
-from crewai.utilities.events.base_event_listener import BaseEventListener
-
-class MyCustomListener(BaseEventListener):
-    def __init__(self):
-        super().__init__()
-
-    def setup_listeners(self, crewai_event_bus):
-        @crewai_event_bus.on(CrewKickoffStartedEvent)
-        def on_crew_started(source, event):
-            print(f"Crew '{event.crew_name}' has started execution!")
-
-        @crewai_event_bus.on(CrewKickoffCompletedEvent)
-        def on_crew_completed(source, event):
-            print(f"Crew '{event.crew_name}' has completed execution!")
-            print(f"Output: {event.output}")
-
-        @crewai_event_bus.on(AgentExecutionCompletedEvent)
-        def on_agent_execution_completed(source, event):
-            print(f"Agent '{event.agent.role}' completed task")
-            print(f"Output: {event.output}")
-```
-
-## Properly Registering Your Listener
-
-Simply defining your listener class isn't enough. You need to create an instance of it and ensure it's imported in your application. This ensures that:
-
-1. The event handlers are registered with the event bus
-2. The listener instance remains in memory (not garbage collected)
-3. The listener is active when events are emitted
-
-### Option 1: Import and Instantiate in Your Crew or Flow Implementation
-
-The most important thing is to create an instance of your listener in the file where your Crew or Flow is defined and executed:
-
-#### For Crew-based Applications
-
-Create and import your listener at the top of your Crew implementation file:
-
-```python
-# In your crew.py file
-from crewai import Agent, Crew, Task
-from my_listeners import MyCustomListener
-
-# Create an instance of your listener
-my_listener = MyCustomListener()
-
-class MyCustomCrew:
-    # Your crew implementation...
-
-    def crew(self):
-        return Crew(
-            agents=[...],
-            tasks=[...],
-            # ...
-        )
-```
-
-#### For Flow-based Applications
-
-Create and import your listener at the top of your Flow implementation file:
-
-```python
-# In your main.py or flow.py file
-from crewai.flow import Flow, listen, start
-from my_listeners import MyCustomListener
-
-# Create an instance of your listener
-my_listener = MyCustomListener()
-
-class MyCustomFlow(Flow):
-    # Your flow implementation...
-
-    @start()
-    def first_step(self):
-        # ...
-```
-
-This ensures that your listener is loaded and active when your Crew or Flow is executed.
-
-### Option 2: Create a Package for Your Listeners
-
-For a more structured approach, especially if you have multiple listeners:
-
-1. Create a package for your listeners:
-
-```
-my_project/
-  ├── listeners/
-  │   ├── __init__.py
-  │   ├── my_custom_listener.py
-  │   └── another_listener.py
-```
-
-2. In `my_custom_listener.py`, define your listener class and create an instance:
-
-```python
-# my_custom_listener.py
-from crewai.utilities.events.base_event_listener import BaseEventListener
-# ... import events ...
-
-class MyCustomListener(BaseEventListener):
-    # ... implementation ...
-
-# Create an instance of your listener
-my_custom_listener = MyCustomListener()
-```
-
-3. In `__init__.py`, import the listener instances to ensure they're loaded:
-
-```python
-# __init__.py
-from .my_custom_listener import my_custom_listener
-from .another_listener import another_listener
-
-# Optionally export them if you need to access them elsewhere
-__all__ = ['my_custom_listener', 'another_listener']
-```
-
-4. Import your listeners package in your Crew or Flow file:
-
-```python
-# In your crew.py or flow.py file
-import my_project.listeners  # This loads all your listeners
-
-class MyCustomCrew:
-    # Your crew implementation...
-```
-
-This is exactly how CrewAI's built-in `agentops_listener` is registered. In the CrewAI codebase, you'll find:
-
-```python
-# src/crewai/utilities/events/third_party/__init__.py
-from .agentops_listener import agentops_listener
-```
-
-This ensures the `agentops_listener` is loaded when the `crewai.utilities.events` package is imported.
-
-## Available Event Types
-
-CrewAI provides a wide range of events that you can listen for:
-
-### Crew Events
-
-- **CrewKickoffStartedEvent**: Emitted when a Crew starts execution
-- **CrewKickoffCompletedEvent**: Emitted when a Crew completes execution
-- **CrewKickoffFailedEvent**: Emitted when a Crew fails to complete execution
-- **CrewTestStartedEvent**: Emitted when a Crew starts testing
-- **CrewTestCompletedEvent**: Emitted when a Crew completes testing
-- **CrewTestFailedEvent**: Emitted when a Crew fails to complete testing
-- **CrewTrainStartedEvent**: Emitted when a Crew starts training
-- **CrewTrainCompletedEvent**: Emitted when a Crew completes training
-- **CrewTrainFailedEvent**: Emitted when a Crew fails to complete training
-
-### Agent Events
-
-- **AgentExecutionStartedEvent**: Emitted when an Agent starts executing a task
-- **AgentExecutionCompletedEvent**: Emitted when an Agent completes executing a task
-- **AgentExecutionErrorEvent**: Emitted when an Agent encounters an error during execution
-
-### Task Events
-
-- **TaskStartedEvent**: Emitted when a Task starts execution
-- **TaskCompletedEvent**: Emitted when a Task completes execution
-- **TaskFailedEvent**: Emitted when a Task fails to complete execution
-- **TaskEvaluationEvent**: Emitted when a Task is evaluated
-
-### Tool Usage Events
-
-- **ToolUsageStartedEvent**: Emitted when a tool execution is started
-- **ToolUsageFinishedEvent**: Emitted when a tool execution is completed
-- **ToolUsageErrorEvent**: Emitted when a tool execution encounters an error
-- **ToolValidateInputErrorEvent**: Emitted when a tool input validation encounters an error
-- **ToolExecutionErrorEvent**: Emitted when a tool execution encounters an error
-- **ToolSelectionErrorEvent**: Emitted when there's an error selecting a tool
-
-### Flow Events
-
-- **FlowCreatedEvent**: Emitted when a Flow is created
-- **FlowStartedEvent**: Emitted when a Flow starts execution
-- **FlowFinishedEvent**: Emitted when a Flow completes execution
-- **FlowPlotEvent**: Emitted when a Flow is plotted
-- **MethodExecutionStartedEvent**: Emitted when a Flow method starts execution
-- **MethodExecutionFinishedEvent**: Emitted when a Flow method completes execution
-- **MethodExecutionFailedEvent**: Emitted when a Flow method fails to complete execution
-
-### LLM Events
-
-- **LLMCallStartedEvent**: Emitted when an LLM call starts
-- **LLMCallCompletedEvent**: Emitted when an LLM call completes
-- **LLMCallFailedEvent**: Emitted when an LLM call fails
-- **LLMStreamChunkEvent**: Emitted for each chunk received during streaming LLM responses
-
-## Event Handler Structure
-
-Each event handler receives two parameters:
-
-1. **source**: The object that emitted the event
-2. **event**: The event instance, containing event-specific data
-
-The structure of the event object depends on the event type, but all events inherit from `BaseEvent` and include:
-
-- **timestamp**: The time when the event was emitted
-- **type**: A string identifier for the event type
-
-Additional fields vary by event type. For example, `CrewKickoffCompletedEvent` includes `crew_name` and `output` fields.
-
-## Real-World Example: Integration with AgentOps
-
-CrewAI includes an example of a third-party integration with [AgentOps](https://github.com/AgentOps-AI/agentops), a monitoring and observability platform for AI agents. Here's how it's implemented:
-
-```python
-from typing import Optional
-
-from crewai.utilities.events import (
-    CrewKickoffCompletedEvent,
-    ToolUsageErrorEvent,
-    ToolUsageStartedEvent,
-)
-from crewai.utilities.events.base_event_listener import BaseEventListener
-from crewai.utilities.events.crew_events import CrewKickoffStartedEvent
-from crewai.utilities.events.task_events import TaskEvaluationEvent
-
-try:
-    import agentops
-    AGENTOPS_INSTALLED = True
-except ImportError:
-    AGENTOPS_INSTALLED = False
-
-class AgentOpsListener(BaseEventListener):
-    tool_event: Optional["agentops.ToolEvent"] = None
-    session: Optional["agentops.Session"] = None
-
-    def __init__(self):
-        super().__init__()
-
-    def setup_listeners(self, crewai_event_bus):
-        if not AGENTOPS_INSTALLED:
-            return
-
-        @crewai_event_bus.on(CrewKickoffStartedEvent)
-        def on_crew_kickoff_started(source, event: CrewKickoffStartedEvent):
-            self.session = agentops.init()
-            for agent in source.agents:
-                if self.session:
-                    self.session.create_agent(
-                        name=agent.role,
-                        agent_id=str(agent.id),
-                    )
-
-        @crewai_event_bus.on(CrewKickoffCompletedEvent)
-        def on_crew_kickoff_completed(source, event: CrewKickoffCompletedEvent):
-            if self.session:
-                self.session.end_session(
-                    end_state="Success",
-                    end_state_reason="Finished Execution",
-                )
-
-        @crewai_event_bus.on(ToolUsageStartedEvent)
-        def on_tool_usage_started(source, event: ToolUsageStartedEvent):
-            self.tool_event = agentops.ToolEvent(name=event.tool_name)
-            if self.session:
-                self.session.record(self.tool_event)
-
-        @crewai_event_bus.on(ToolUsageErrorEvent)
-        def on_tool_usage_error(source, event: ToolUsageErrorEvent):
-            agentops.ErrorEvent(exception=event.error, trigger_event=self.tool_event)
-```
-
-This listener initializes an AgentOps session when a Crew starts, registers agents with AgentOps, tracks tool usage, and ends the session when the Crew completes.
-
-The AgentOps listener is registered in CrewAI's event system through the import in `src/crewai/utilities/events/third_party/__init__.py`:
-
-```python
-from .agentops_listener import agentops_listener
-```
-
-This ensures the `agentops_listener` is loaded when the `crewai.utilities.events` package is imported.
-
-## Advanced Usage: Scoped Handlers
-
-For temporary event handling (useful for testing or specific operations), you can use the `scoped_handlers` context manager:
-
-```python
-from crewai.utilities.events import crewai_event_bus, CrewKickoffStartedEvent
-
-with crewai_event_bus.scoped_handlers():
-    @crewai_event_bus.on(CrewKickoffStartedEvent)
-    def temp_handler(source, event):
-        print("This handler only exists within this context")
-
-    # Do something that emits events
-
-# Outside the context, the temporary handler is removed
-```
-
-## Use Cases
-
-Event listeners can be used for a variety of purposes:
-
-1. **Logging and Monitoring**: Track the execution of your Crew and log important events
-2. **Analytics**: Collect data about your Crew's performance and behavior
-3. **Debugging**: Set up temporary listeners to debug specific issues
-4. **Integration**: Connect CrewAI with external systems like monitoring platforms, databases, or notification services
-5. **Custom Behavior**: Trigger custom actions based on specific events
-
-## Best Practices
-
-1. **Keep Handlers Light**: Event handlers should be lightweight and avoid blocking operations
-2. **Error Handling**: Include proper error handling in your event handlers to prevent exceptions from affecting the main execution
-3. **Cleanup**: If your listener allocates resources, ensure they're properly cleaned up
-4. **Selective Listening**: Only listen for events you actually need to handle
-5. **Testing**: Test your event listeners in isolation to ensure they behave as expected
-
-By leveraging CrewAI's event system, you can extend its functionality and integrate it seamlessly with your existing infrastructure.

docs/concepts/flows.mdx

@@ -1,862 +0,0 @@
----
-title: Flows
-description: Learn how to create and manage AI workflows using CrewAI Flows.
-icon: arrow-progress
----
-
-## Introduction
-
-CrewAI Flows is a powerful feature designed to streamline the creation and management of AI workflows. Flows allow developers to combine and coordinate coding tasks and Crews efficiently, providing a robust framework for building sophisticated AI automations.
-
-Flows allow you to create structured, event-driven workflows. They provide a seamless way to connect multiple tasks, manage state, and control the flow of execution in your AI applications. With Flows, you can easily design and implement multi-step processes that leverage the full potential of CrewAI's capabilities.
-
-1. **Simplified Workflow Creation**: Easily chain together multiple Crews and tasks to create complex AI workflows.
-
-2. **State Management**: Flows make it super easy to manage and share state between different tasks in your workflow.
-
-3. **Event-Driven Architecture**: Built on an event-driven model, allowing for dynamic and responsive workflows.
-
-4. **Flexible Control Flow**: Implement conditional logic, loops, and branching within your workflows.
-
-## Getting Started
-
-Let's create a simple Flow where you will use OpenAI to generate a random city in one task and then use that city to generate a fun fact in another task.
-
-```python Code
-
-from crewai.flow.flow import Flow, listen, start
-from dotenv import load_dotenv
-from litellm import completion
-
-
-class ExampleFlow(Flow):
-    model = "gpt-4o-mini"
-
-    @start()
-    def generate_city(self):
-        print("Starting flow")
-        # Each flow state automatically gets a unique ID
-        print(f"Flow State ID: {self.state['id']}")
-
-        response = completion(
-            model=self.model,
-            messages=[
-                {
-                    "role": "user",
-                    "content": "Return the name of a random city in the world.",
-                },
-            ],
-        )
-
-        random_city = response["choices"][0]["message"]["content"]
-        # Store the city in our state
-        self.state["city"] = random_city
-        print(f"Random City: {random_city}")
-
-        return random_city
-
-    @listen(generate_city)
-    def generate_fun_fact(self, random_city):
-        response = completion(
-            model=self.model,
-            messages=[
-                {
-                    "role": "user",
-                    "content": f"Tell me a fun fact about {random_city}",
-                },
-            ],
-        )
-
-        fun_fact = response["choices"][0]["message"]["content"]
-        # Store the fun fact in our state
-        self.state["fun_fact"] = fun_fact
-        return fun_fact
-
-
-
-flow = ExampleFlow()
-result = flow.kickoff()
-
-print(f"Generated fun fact: {result}")
-```
-
-In the above example, we have created a simple Flow that generates a random city using OpenAI and then generates a fun fact about that city. The Flow consists of two tasks: `generate_city` and `generate_fun_fact`. The `generate_city` task is the starting point of the Flow, and the `generate_fun_fact` task listens for the output of the `generate_city` task.
-
-Each Flow instance automatically receives a unique identifier (UUID) in its state, which helps track and manage flow executions. The state can also store additional data (like the generated city and fun fact) that persists throughout the flow's execution.
-
-When you run the Flow, it will:
-1. Generate a unique ID for the flow state
-2. Generate a random city and store it in the state
-3. Generate a fun fact about that city and store it in the state
-4. Print the results to the console
-
-The state's unique ID and stored data can be useful for tracking flow executions and maintaining context between tasks.
-
-**Note:** Ensure you have set up your `.env` file to store your `OPENAI_API_KEY`. This key is necessary for authenticating requests to the OpenAI API.
-
-### @start()
-
-The `@start()` decorator is used to mark a method as the starting point of a Flow. When a Flow is started, all the methods decorated with `@start()` are executed in parallel. You can have multiple start methods in a Flow, and they will all be executed when the Flow is started.
-
-### @listen()
-
-The `@listen()` decorator is used to mark a method as a listener for the output of another task in the Flow. The method decorated with `@listen()` will be executed when the specified task emits an output. The method can access the output of the task it is listening to as an argument.
-
-#### Usage
-
-The `@listen()` decorator can be used in several ways:
-
-1. **Listening to a Method by Name**: You can pass the name of the method you want to listen to as a string. When that method completes, the listener method will be triggered.
-
-   ```python Code
-   @listen("generate_city")
-   def generate_fun_fact(self, random_city):
-       # Implementation
-   ```
-
-2. **Listening to a Method Directly**: You can pass the method itself. When that method completes, the listener method will be triggered.
-   ```python Code
-   @listen(generate_city)
-   def generate_fun_fact(self, random_city):
-       # Implementation
-   ```
-
-### Flow Output
-
-Accessing and handling the output of a Flow is essential for integrating your AI workflows into larger applications or systems. CrewAI Flows provide straightforward mechanisms to retrieve the final output, access intermediate results, and manage the overall state of your Flow.
-
-#### Retrieving the Final Output
-
-When you run a Flow, the final output is determined by the last method that completes. The `kickoff()` method returns the output of this final method.
-
-Here's how you can access the final output:
-
-<CodeGroup>
-```python Code
-from crewai.flow.flow import Flow, listen, start
-
-class OutputExampleFlow(Flow):
-    @start()
-    def first_method(self):
-        return "Output from first_method"
-
-    @listen(first_method)
-    def second_method(self, first_output):
-        return f"Second method received: {first_output}"
-
-
-flow = OutputExampleFlow()
-final_output = flow.kickoff()
-
-print("---- Final Output ----")
-print(final_output)
-```
-
-```text Output
----- Final Output ----
-Second method received: Output from first_method
-```
-
-</CodeGroup>
-
-In this example, the `second_method` is the last method to complete, so its output will be the final output of the Flow.
-The `kickoff()` method will return the final output, which is then printed to the console.
-
-#### Accessing and Updating State
-
-In addition to retrieving the final output, you can also access and update the state within your Flow. The state can be used to store and share data between different methods in the Flow. After the Flow has run, you can access the state to retrieve any information that was added or updated during the execution.
-
-Here's an example of how to update and access the state:
-
-<CodeGroup>
-
-```python Code
-from crewai.flow.flow import Flow, listen, start
-from pydantic import BaseModel
-
-class ExampleState(BaseModel):
-    counter: int = 0
-    message: str = ""
-
-class StateExampleFlow(Flow[ExampleState]):
-
-    @start()
-    def first_method(self):
-        self.state.message = "Hello from first_method"
-        self.state.counter += 1
-
-    @listen(first_method)
-    def second_method(self):
-        self.state.message += " - updated by second_method"
-        self.state.counter += 1
-        return self.state.message
-
-flow = StateExampleFlow()
-final_output = flow.kickoff()
-print(f"Final Output: {final_output}")
-print("Final State:")
-print(flow.state)
-```
-
-```text Output
-Final Output: Hello from first_method - updated by second_method
-Final State:
-counter=2 message='Hello from first_method - updated by second_method'
-```
-
-</CodeGroup>
-
-In this example, the state is updated by both `first_method` and `second_method`.
-After the Flow has run, you can access the final state to see the updates made by these methods.
-
-By ensuring that the final method's output is returned and providing access to the state, CrewAI Flows make it easy to integrate the results of your AI workflows into larger applications or systems,
-while also maintaining and accessing the state throughout the Flow's execution.
-
-## Flow State Management
-
-Managing state effectively is crucial for building reliable and maintainable AI workflows. CrewAI Flows provides robust mechanisms for both unstructured and structured state management,
-allowing developers to choose the approach that best fits their application's needs.
-
-### Unstructured State Management
-
-In unstructured state management, all state is stored in the `state` attribute of the `Flow` class.
-This approach offers flexibility, enabling developers to add or modify state attributes on the fly without defining a strict schema.
-Even with unstructured states, CrewAI Flows automatically generates and maintains a unique identifier (UUID) for each state instance.
-
-```python Code
-from crewai.flow.flow import Flow, listen, start
-
-class UnstructuredExampleFlow(Flow):
-
-    @start()
-    def first_method(self):
-        # The state automatically includes an 'id' field
-        print(f"State ID: {self.state['id']}")
-        self.state['counter'] = 0
-        self.state['message'] = "Hello from structured flow"
-
-    @listen(first_method)
-    def second_method(self):
-        self.state['counter'] += 1
-        self.state['message'] += " - updated"
-
-    @listen(second_method)
-    def third_method(self):
-        self.state['counter'] += 1
-        self.state['message'] += " - updated again"
-
-        print(f"State after third_method: {self.state}")
-
-
-flow = UnstructuredExampleFlow()
-flow.kickoff()
-```
-
-**Note:** The `id` field is automatically generated and preserved throughout the flow's execution. You don't need to manage or set it manually, and it will be maintained even when updating the state with new data.
-
-**Key Points:**
-
-- **Flexibility:** You can dynamically add attributes to `self.state` without predefined constraints.
-- **Simplicity:** Ideal for straightforward workflows where state structure is minimal or varies significantly.
-
-### Structured State Management
-
-Structured state management leverages predefined schemas to ensure consistency and type safety across the workflow.
-By using models like Pydantic's `BaseModel`, developers can define the exact shape of the state, enabling better validation and auto-completion in development environments.
-
-Each state in CrewAI Flows automatically receives a unique identifier (UUID) to help track and manage state instances. This ID is automatically generated and managed by the Flow system.
-
-```python Code
-from crewai.flow.flow import Flow, listen, start
-from pydantic import BaseModel
-
-
-class ExampleState(BaseModel):
-    # Note: 'id' field is automatically added to all states
-    counter: int = 0
-    message: str = ""
-
-
-class StructuredExampleFlow(Flow[ExampleState]):
-
-    @start()
-    def first_method(self):
-        # Access the auto-generated ID if needed
-        print(f"State ID: {self.state.id}")
-        self.state.message = "Hello from structured flow"
-
-    @listen(first_method)
-    def second_method(self):
-        self.state.counter += 1
-        self.state.message += " - updated"
-
-    @listen(second_method)
-    def third_method(self):
-        self.state.counter += 1
-        self.state.message += " - updated again"
-
-        print(f"State after third_method: {self.state}")
-
-
-flow = StructuredExampleFlow()
-flow.kickoff()
-```
-
-**Key Points:**
-
-- **Defined Schema:** `ExampleState` clearly outlines the state structure, enhancing code readability and maintainability.
-- **Type Safety:** Leveraging Pydantic ensures that state attributes adhere to the specified types, reducing runtime errors.
-- **Auto-Completion:** IDEs can provide better auto-completion and error checking based on the defined state model.
-
-### Choosing Between Unstructured and Structured State Management
-
-- **Use Unstructured State Management when:**
-
-  - The workflow's state is simple or highly dynamic.
-  - Flexibility is prioritized over strict state definitions.
-  - Rapid prototyping is required without the overhead of defining schemas.
-
-- **Use Structured State Management when:**
-  - The workflow requires a well-defined and consistent state structure.
-  - Type safety and validation are important for your application's reliability.
-  - You want to leverage IDE features like auto-completion and type checking for better developer experience.
-
-By providing both unstructured and structured state management options, CrewAI Flows empowers developers to build AI workflows that are both flexible and robust, catering to a wide range of application requirements.
-
-## Flow Persistence
-
-The @persist decorator enables automatic state persistence in CrewAI Flows, allowing you to maintain flow state across restarts or different workflow executions. This decorator can be applied at either the class level or method level, providing flexibility in how you manage state persistence.
-
-### Class-Level Persistence
-
-When applied at the class level, the @persist decorator automatically persists all flow method states:
-
-```python
-@persist  # Using SQLiteFlowPersistence by default
-class MyFlow(Flow[MyState]):
-    @start()
-    def initialize_flow(self):
-        # This method will automatically have its state persisted
-        self.state.counter = 1
-        print("Initialized flow. State ID:", self.state.id)
-
-    @listen(initialize_flow)
-    def next_step(self):
-        # The state (including self.state.id) is automatically reloaded
-        self.state.counter += 1
-        print("Flow state is persisted. Counter:", self.state.counter)
-```
-
-### Method-Level Persistence
-
-For more granular control, you can apply @persist to specific methods:
-
-```python
-class AnotherFlow(Flow[dict]):
-    @persist  # Persists only this method's state
-    @start()
-    def begin(self):
-        if "runs" not in self.state:
-            self.state["runs"] = 0
-        self.state["runs"] += 1
-        print("Method-level persisted runs:", self.state["runs"])
-```
-
-### How It Works
-
-1. **Unique State Identification**
-   - Each flow state automatically receives a unique UUID
-   - The ID is preserved across state updates and method calls
-   - Supports both structured (Pydantic BaseModel) and unstructured (dictionary) states
-
-2. **Default SQLite Backend**
-   - SQLiteFlowPersistence is the default storage backend
-   - States are automatically saved to a local SQLite database
-   - Robust error handling ensures clear messages if database operations fail
-
-3. **Error Handling**
-   - Comprehensive error messages for database operations
-   - Automatic state validation during save and load
-   - Clear feedback when persistence operations encounter issues
-
-### Important Considerations
-
-- **State Types**: Both structured (Pydantic BaseModel) and unstructured (dictionary) states are supported
-- **Automatic ID**: The `id` field is automatically added if not present
-- **State Recovery**: Failed or restarted flows can automatically reload their previous state
-- **Custom Implementation**: You can provide your own FlowPersistence implementation for specialized storage needs
-
-### Technical Advantages
-
-1. **Precise Control Through Low-Level Access**
-   - Direct access to persistence operations for advanced use cases
-   - Fine-grained control via method-level persistence decorators
-   - Built-in state inspection and debugging capabilities
-   - Full visibility into state changes and persistence operations
-
-2. **Enhanced Reliability**
-   - Automatic state recovery after system failures or restarts
-   - Transaction-based state updates for data integrity
-   - Comprehensive error handling with clear error messages
-   - Robust validation during state save and load operations
-
-3. **Extensible Architecture**
-   - Customizable persistence backend through FlowPersistence interface
-   - Support for specialized storage solutions beyond SQLite
-   - Compatible with both structured (Pydantic) and unstructured (dict) states
-   - Seamless integration with existing CrewAI flow patterns
-
-The persistence system's architecture emphasizes technical precision and customization options, allowing developers to maintain full control over state management while benefiting from built-in reliability features.
-
-## Flow Control
-
-### Conditional Logic: `or`
-
-The `or_` function in Flows allows you to listen to multiple methods and trigger the listener method when any of the specified methods emit an output.
-
-<CodeGroup>
-
-```python Code
-from crewai.flow.flow import Flow, listen, or_, start
-
-class OrExampleFlow(Flow):
-
-    @start()
-    def start_method(self):
-        return "Hello from the start method"
-
-    @listen(start_method)
-    def second_method(self):
-        return "Hello from the second method"
-
-    @listen(or_(start_method, second_method))
-    def logger(self, result):
-        print(f"Logger: {result}")
-
-
-
-flow = OrExampleFlow()
-flow.kickoff()
-```
-
-```text Output
-Logger: Hello from the start method
-Logger: Hello from the second method
-```
-
-</CodeGroup>
-
-When you run this Flow, the `logger` method will be triggered by the output of either the `start_method` or the `second_method`.
-The `or_` function is used to listen to multiple methods and trigger the listener method when any of the specified methods emit an output.
-
-### Conditional Logic: `and`
-
-The `and_` function in Flows allows you to listen to multiple methods and trigger the listener method only when all the specified methods emit an output.
-
-<CodeGroup>
-
-```python Code
-from crewai.flow.flow import Flow, and_, listen, start
-
-class AndExampleFlow(Flow):
-
-    @start()
-    def start_method(self):
-        self.state["greeting"] = "Hello from the start method"
-
-    @listen(start_method)
-    def second_method(self):
-        self.state["joke"] = "What do computers eat? Microchips."
-
-    @listen(and_(start_method, second_method))
-    def logger(self):
-        print("---- Logger ----")
-        print(self.state)
-
-flow = AndExampleFlow()
-flow.kickoff()
-```
-
-```text Output
----- Logger ----
-{'greeting': 'Hello from the start method', 'joke': 'What do computers eat? Microchips.'}
-```
-
-</CodeGroup>
-
-When you run this Flow, the `logger` method will be triggered only when both the `start_method` and the `second_method` emit an output.
-The `and_` function is used to listen to multiple methods and trigger the listener method only when all the specified methods emit an output.
-
-### Router
-
-The `@router()` decorator in Flows allows you to define conditional routing logic based on the output of a method.
-You can specify different routes based on the output of the method, allowing you to control the flow of execution dynamically.
-
-<CodeGroup>
-
-```python Code
-import random
-from crewai.flow.flow import Flow, listen, router, start
-from pydantic import BaseModel
-
-class ExampleState(BaseModel):
-    success_flag: bool = False
-
-class RouterFlow(Flow[ExampleState]):
-
-    @start()
-    def start_method(self):
-        print("Starting the structured flow")
-        random_boolean = random.choice([True, False])
-        self.state.success_flag = random_boolean
-
-    @router(start_method)
-    def second_method(self):
-        if self.state.success_flag:
-            return "success"
-        else:
-            return "failed"
-
-    @listen("success")
-    def third_method(self):
-        print("Third method running")
-
-    @listen("failed")
-    def fourth_method(self):
-        print("Fourth method running")
-
-
-flow = RouterFlow()
-flow.kickoff()
-```
-
-```text Output
-Starting the structured flow
-Third method running
-Fourth method running
-```
-
-</CodeGroup>
-
-In the above example, the `start_method` generates a random boolean value and sets it in the state.
-The `second_method` uses the `@router()` decorator to define conditional routing logic based on the value of the boolean.
-If the boolean is `True`, the method returns `"success"`, and if it is `False`, the method returns `"failed"`.
-The `third_method` and `fourth_method` listen to the output of the `second_method` and execute based on the returned value.
-
-When you run this Flow, the output will change based on the random boolean value generated by the `start_method`.
-
-## Adding LiteAgent to Flows
-
-LiteAgents can be seamlessly integrated into your flows, providing a lightweight alternative to full Crews when you need simpler, focused task execution. Here's an example of how to use a LiteAgent within a flow to perform market research:
-
-```python
-from typing import List, cast
-from crewai_tools.tools.website_search.website_search_tool import WebsiteSearchTool
-from pydantic import BaseModel, Field
-from crewai.flow.flow import Flow, listen, start
-from crewai.lite_agent import LiteAgent
-
-# Define a structured output format
-class MarketAnalysis(BaseModel):
-    key_trends: List[str] = Field(description="List of identified market trends")
-    market_size: str = Field(description="Estimated market size")
-    competitors: List[str] = Field(description="Major competitors in the space")
-
-# Define flow state
-class MarketResearchState(BaseModel):
-    product: str = ""
-    analysis: MarketAnalysis | None = None
-
-class MarketResearchFlow(Flow[MarketResearchState]):
-    @start()
-    def initialize_research(self):
-        print(f"Starting market research for {self.state.product}")
-
-    @listen(initialize_research)
-    def analyze_market(self):
-        # Create a LiteAgent for market research
-        analyst = LiteAgent(
-            role="Market Research Analyst",
-            goal=f"Analyze the market for {self.state.product}",
-            backstory="You are an experienced market analyst with expertise in "
-            "identifying market trends and opportunities.",
-            llm="gpt-4o",
-            tools=[WebsiteSearchTool()],
-            verbose=True,
-            response_format=MarketAnalysis,
-        )
-
-        # Define the research query
-        query = f"""
-        Research the market for {self.state.product}. Include:
-        1. Key market trends
-        2. Market size
-        3. Major competitors
-        
-        Format your response according to the specified structure.
-        """
-
-        # Execute the analysis
-        result = analyst.kickoff(query)
-        self.state.analysis = cast(MarketAnalysis, result.pydantic)
-        return result.pydantic
-
-    @listen(analyze_market)
-    def present_results(self):
-        analysis = self.state.analysis
-        if analysis is None:
-            print("No analysis results available")
-            return
-
-        print("\nMarket Analysis Results")
-        print("=====================")
-
-        print("\nKey Market Trends:")
-        for trend in analysis.key_trends:
-            print(f"- {trend}")
-
-        print(f"\nMarket Size: {analysis.market_size}")
-
-        print("\nMajor Competitors:")
-        for competitor in analysis.competitors:
-            print(f"- {competitor}")
-
-# Usage example
-flow = MarketResearchFlow()
-result = flow.kickoff(inputs={"product": "AI-powered chatbots"})
-```
-
-This example demonstrates several key features of using LiteAgents in flows:
-
-1. **Structured Output**: Using Pydantic models to define the expected output format (`MarketAnalysis`) ensures type safety and structured data throughout the flow.
-
-2. **State Management**: The flow state (`MarketResearchState`) maintains context between steps and stores both inputs and outputs.
-
-3. **Tool Integration**: LiteAgents can use tools (like `WebsiteSearchTool`) to enhance their capabilities.
-
-If you want to learn more about LiteAgents, check out the [LiteAgent](/concepts/lite-agent) page.
-
-## Adding Crews to Flows
-
-Creating a flow with multiple crews in CrewAI is straightforward.
-
-You can generate a new CrewAI project that includes all the scaffolding needed to create a flow with multiple crews by running the following command:
-
-```bash
-crewai create flow name_of_flow
-```
-
-This command will generate a new CrewAI project with the necessary folder structure. The generated project includes a prebuilt crew called `poem_crew` that is already working. You can use this crew as a template by copying, pasting, and editing it to create other crews.
-
-### Folder Structure
-
-After running the `crewai create flow name_of_flow` command, you will see a folder structure similar to the following:
-
-| Directory/File         | Description                                                        |
-| :--------------------- | :----------------------------------------------------------------- |
-| `name_of_flow/`        | Root directory for the flow.                                       |
-| ├── `crews/`           | Contains directories for specific crews.                           |
-| │ └── `poem_crew/`     | Directory for the "poem_crew" with its configurations and scripts. |
-| │ ├── `config/`        | Configuration files directory for the "poem_crew".                 |
-| │ │ ├── `agents.yaml`  | YAML file defining the agents for "poem_crew".                     |
-| │ │ └── `tasks.yaml`   | YAML file defining the tasks for "poem_crew".                      |
-| │ ├── `poem_crew.py`   | Script for "poem_crew" functionality.                              |
-| ├── `tools/`           | Directory for additional tools used in the flow.                   |
-| │ └── `custom_tool.py` | Custom tool implementation.                                        |
-| ├── `main.py`          | Main script for running the flow.                                  |
-| ├── `README.md`        | Project description and instructions.                              |
-| ├── `pyproject.toml`   | Configuration file for project dependencies and settings.          |
-| └── `.gitignore`       | Specifies files and directories to ignore in version control.      |
-
-### Building Your Crews
-
-In the `crews` folder, you can define multiple crews. Each crew will have its own folder containing configuration files and the crew definition file. For example, the `poem_crew` folder contains:
-
-- `config/agents.yaml`: Defines the agents for the crew.
-- `config/tasks.yaml`: Defines the tasks for the crew.
-- `poem_crew.py`: Contains the crew definition, including agents, tasks, and the crew itself.
-
-You can copy, paste, and edit the `poem_crew` to create other crews.
-
-### Connecting Crews in `main.py`
-
-The `main.py` file is where you create your flow and connect the crews together. You can define your flow by using the `Flow` class and the decorators `@start` and `@listen` to specify the flow of execution.
-
-Here's an example of how you can connect the `poem_crew` in the `main.py` file:
-
-```python Code
-#!/usr/bin/env python
-from random import randint
-
-from pydantic import BaseModel
-from crewai.flow.flow import Flow, listen, start
-from .crews.poem_crew.poem_crew import PoemCrew
-
-class PoemState(BaseModel):
-    sentence_count: int = 1
-    poem: str = ""
-
-class PoemFlow(Flow[PoemState]):
-
-    @start()
-    def generate_sentence_count(self):
-        print("Generating sentence count")
-        self.state.sentence_count = randint(1, 5)
-
-    @listen(generate_sentence_count)
-    def generate_poem(self):
-        print("Generating poem")
-        result = PoemCrew().crew().kickoff(inputs={"sentence_count": self.state.sentence_count})
-
-        print("Poem generated", result.raw)
-        self.state.poem = result.raw
-
-    @listen(generate_poem)
-    def save_poem(self):
-        print("Saving poem")
-        with open("poem.txt", "w") as f:
-            f.write(self.state.poem)
-
-def kickoff():
-    poem_flow = PoemFlow()
-    poem_flow.kickoff()
-
-
-def plot():
-    poem_flow = PoemFlow()
-    poem_flow.plot()
-
-if __name__ == "__main__":
-    kickoff()
-```
-
-In this example, the `PoemFlow` class defines a flow that generates a sentence count, uses the `PoemCrew` to generate a poem, and then saves the poem to a file. The flow is kicked off by calling the `kickoff()` method.
-
-### Running the Flow
-
-(Optional) Before running the flow, you can install the dependencies by running:
-
-```bash
-crewai install
-```
-
-Once all of the dependencies are installed, you need to activate the virtual environment by running:
-
-```bash
-source .venv/bin/activate
-```
-
-After activating the virtual environment, you can run the flow by executing one of the following commands:
-
-```bash
-crewai flow kickoff
-```
-
-or
-
-```bash
-uv run kickoff
-```
-
-The flow will execute, and you should see the output in the console.
-
-## Plot Flows
-
-Visualizing your AI workflows can provide valuable insights into the structure and execution paths of your flows. CrewAI offers a powerful visualization tool that allows you to generate interactive plots of your flows, making it easier to understand and optimize your AI workflows.
-
-### What are Plots?
-
-Plots in CrewAI are graphical representations of your AI workflows. They display the various tasks, their connections, and the flow of data between them. This visualization helps in understanding the sequence of operations, identifying bottlenecks, and ensuring that the workflow logic aligns with your expectations.
-
-### How to Generate a Plot
-
-CrewAI provides two convenient methods to generate plots of your flows:
-
-#### Option 1: Using the `plot()` Method
-
-If you are working directly with a flow instance, you can generate a plot by calling the `plot()` method on your flow object. This method will create an HTML file containing the interactive plot of your flow.
-
-```python Code
-# Assuming you have a flow instance
-flow.plot("my_flow_plot")
-```
-
-This will generate a file named `my_flow_plot.html` in your current directory. You can open this file in a web browser to view the interactive plot.
-
-#### Option 2: Using the Command Line
-
-If you are working within a structured CrewAI project, you can generate a plot using the command line. This is particularly useful for larger projects where you want to visualize the entire flow setup.
-
-```bash
-crewai flow plot
-```
-
-This command will generate an HTML file with the plot of your flow, similar to the `plot()` method. The file will be saved in your project directory, and you can open it in a web browser to explore the flow.
-
-### Understanding the Plot
-
-The generated plot will display nodes representing the tasks in your flow, with directed edges indicating the flow of execution. The plot is interactive, allowing you to zoom in and out, and hover over nodes to see additional details.
-
-By visualizing your flows, you can gain a clearer understanding of the workflow's structure, making it easier to debug, optimize, and communicate your AI processes to others.
-
-### Conclusion
-
-Plotting your flows is a powerful feature of CrewAI that enhances your ability to design and manage complex AI workflows. Whether you choose to use the `plot()` method or the command line, generating plots will provide you with a visual representation of your workflows, aiding in both development and presentation.
-
-## Next Steps
-
-If you're interested in exploring additional examples of flows, we have a variety of recommendations in our examples repository. Here are four specific flow examples, each showcasing unique use cases to help you match your current problem type to a specific example:
-
-1. **Email Auto Responder Flow**: This example demonstrates an infinite loop where a background job continually runs to automate email responses. It's a great use case for tasks that need to be performed repeatedly without manual intervention. [View Example](https://github.com/crewAIInc/crewAI-examples/tree/main/email_auto_responder_flow)
-
-2. **Lead Score Flow**: This flow showcases adding human-in-the-loop feedback and handling different conditional branches using the router. It's an excellent example of how to incorporate dynamic decision-making and human oversight into your workflows. [View Example](https://github.com/crewAIInc/crewAI-examples/tree/main/lead-score-flow)
-
-3. **Write a Book Flow**: This example excels at chaining multiple crews together, where the output of one crew is used by another. Specifically, one crew outlines an entire book, and another crew generates chapters based on the outline. Eventually, everything is connected to produce a complete book. This flow is perfect for complex, multi-step processes that require coordination between different tasks. [View Example](https://github.com/crewAIInc/crewAI-examples/tree/main/write_a_book_with_flows)
-
-4. **Meeting Assistant Flow**: This flow demonstrates how to broadcast one event to trigger multiple follow-up actions. For instance, after a meeting is completed, the flow can update a Trello board, send a Slack message, and save the results. It's a great example of handling multiple outcomes from a single event, making it ideal for comprehensive task management and notification systems. [View Example](https://github.com/crewAIInc/crewAI-examples/tree/main/meeting_assistant_flow)
-
-By exploring these examples, you can gain insights into how to leverage CrewAI Flows for various use cases, from automating repetitive tasks to managing complex, multi-step processes with dynamic decision-making and human feedback.
-
-Also, check out our YouTube video on how to use flows in CrewAI below!
-
-<iframe
-  width="560"
-  height="315"
-  src="https://www.youtube.com/embed/MTb5my6VOT8"
-  title="YouTube video player"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-  referrerpolicy="strict-origin-when-cross-origin"
-  allowfullscreen
-></iframe>
-
-## Running Flows
-
-There are two ways to run a flow:
-
-### Using the Flow API
-
-You can run a flow programmatically by creating an instance of your flow class and calling the `kickoff()` method:
-
-```python
-flow = ExampleFlow()
-result = flow.kickoff()
-```
-
-### Using the CLI
-
-Starting from version 0.103.0, you can run flows using the `crewai run` command:
-
-```shell
-crewai run
-```
-
-This command automatically detects if your project is a flow (based on the `type = "flow"` setting in your pyproject.toml) and runs it accordingly. This is the recommended way to run flows from the command line.
-
-For backward compatibility, you can also use:
-
-```shell
-crewai flow kickoff
-```
-
-However, the `crewai run` command is now the preferred method as it works for both crews and flows.

docs/concepts/knowledge.mdx

@@ -1,626 +0,0 @@
----
-title: Knowledge
-description: What is knowledge in CrewAI and how to use it.
-icon: book
----
-
-## What is Knowledge?
-
-Knowledge in CrewAI is a powerful system that allows AI agents to access and utilize external information sources during their tasks.
-Think of it as giving your agents a reference library they can consult while working.
-
-<Info>
-  Key benefits of using Knowledge:
-  - Enhance agents with domain-specific information
-  - Support decisions with real-world data
-  - Maintain context across conversations
-  - Ground responses in factual information
-</Info>
-
-## Supported Knowledge Sources
-
-CrewAI supports various types of knowledge sources out of the box:
-
-<CardGroup cols={2}>
-  <Card title="Text Sources" icon="text">
-    - Raw strings
-    - Text files (.txt)
-    - PDF documents
-  </Card>
-  <Card title="Structured Data" icon="table">
-    - CSV files
-    - Excel spreadsheets
-    - JSON documents
-  </Card>
-</CardGroup>
-
-## Supported Knowledge Parameters
-
-| Parameter                    | Type                                | Required | Description                                                                                                                                           |
-| :--------------------------- | :---------------------------------- | :------- | :---------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `sources`                  | **List[BaseKnowledgeSource]**        | Yes      | List of knowledge sources that provide content to be stored and queried. Can include PDF, CSV, Excel, JSON, text files, or string content.           |
-| `collection_name`          | **str**                              | No       | Name of the collection where the knowledge will be stored. Used to identify different sets of knowledge. Defaults to "knowledge" if not provided.     |
-| `storage`                  | **Optional[KnowledgeStorage]**       | No       | Custom storage configuration for managing how the knowledge is stored and retrieved. If not provided, a default storage will be created.              |
-
-## Quickstart Example
-
-<Tip>
-For file-Based Knowledge Sources, make sure to place your files in a `knowledge` directory at the root of your project. 
-Also, use relative paths from the `knowledge` directory when creating the source.
-</Tip>
-
-Here's an example using string-based knowledge:
-
-```python Code
-from crewai import Agent, Task, Crew, Process, LLM
-from crewai.knowledge.source.string_knowledge_source import StringKnowledgeSource
-
-# Create a knowledge source
-content = "Users name is John. He is 30 years old and lives in San Francisco."
-string_source = StringKnowledgeSource(
-    content=content,
-)
-
-# Create an LLM with a temperature of 0 to ensure deterministic outputs
-llm = LLM(model="gpt-4o-mini", temperature=0)
-
-# Create an agent with the knowledge store
-agent = Agent(
-    role="About User",
-    goal="You know everything about the user.",
-    backstory="""You are a master at understanding people and their preferences.""",
-    verbose=True,
-    allow_delegation=False,
-    llm=llm,
-)
-task = Task(
-    description="Answer the following questions about the user: {question}",
-    expected_output="An answer to the question.",
-    agent=agent,
-)
-
-crew = Crew(
-    agents=[agent],
-    tasks=[task],
-    verbose=True,
-    process=Process.sequential,
-    knowledge_sources=[string_source], # Enable knowledge by adding the sources here. You can also add more sources to the sources list.
-)
-
-result = crew.kickoff(inputs={"question": "What city does John live in and how old is he?"})
-```
-
-
-Here's another example with the `CrewDoclingSource`. The CrewDoclingSource is actually quite versatile and can handle multiple file formats including MD, PDF, DOCX, HTML, and more. 
-
-<Note>
-  You need to install `docling` for the following example to work: `uv add docling`
-</Note>
-
-
-
-```python Code
-from crewai import LLM, Agent, Crew, Process, Task
-from crewai.knowledge.source.crew_docling_source import CrewDoclingSource
-
-# Create a knowledge source
-content_source = CrewDoclingSource(
-    file_paths=[
-        "https://lilianweng.github.io/posts/2024-11-28-reward-hacking",
-        "https://lilianweng.github.io/posts/2024-07-07-hallucination",
-    ],
-)
-
-# Create an LLM with a temperature of 0 to ensure deterministic outputs
-llm = LLM(model="gpt-4o-mini", temperature=0)
-
-# Create an agent with the knowledge store
-agent = Agent(
-    role="About papers",
-    goal="You know everything about the papers.",
-    backstory="""You are a master at understanding papers and their content.""",
-    verbose=True,
-    allow_delegation=False,
-    llm=llm,
-)
-task = Task(
-    description="Answer the following questions about the papers: {question}",
-    expected_output="An answer to the question.",
-    agent=agent,
-)
-
-crew = Crew(
-    agents=[agent],
-    tasks=[task],
-    verbose=True,
-    process=Process.sequential,
-    knowledge_sources=[
-        content_source
-    ],  # Enable knowledge by adding the sources here. You can also add more sources to the sources list.
-)
-
-result = crew.kickoff(
-    inputs={
-        "question": "What is the reward hacking paper about? Be sure to provide sources."
-    }
-)
-```
-
-## More Examples
-
-Here are examples of how to use different types of knowledge sources:
-
-Note: Please ensure that you create the ./knowldge folder. All source files (e.g., .txt, .pdf, .xlsx, .json) should be placed in this folder for centralized management.
-
-### Text File Knowledge Source
-```python
-from crewai.knowledge.source.text_file_knowledge_source import TextFileKnowledgeSource
-
-# Create a text file knowledge source
-text_source = TextFileKnowledgeSource(
-    file_paths=["document.txt", "another.txt"]
-)
-
-# Create crew with text file source on agents or crew level
-agent = Agent(
-    ...
-    knowledge_sources=[text_source]
-)
-
-crew = Crew(
-    ...
-    knowledge_sources=[text_source]
-)
-```
-
-### PDF Knowledge Source
-```python
-from crewai.knowledge.source.pdf_knowledge_source import PDFKnowledgeSource
-
-# Create a PDF knowledge source
-pdf_source = PDFKnowledgeSource(
-    file_paths=["document.pdf", "another.pdf"]
-)
-
-# Create crew with PDF knowledge source on agents or crew level
-agent = Agent(
-    ...
-    knowledge_sources=[pdf_source]
-)
-
-crew = Crew(
-    ...
-    knowledge_sources=[pdf_source]
-)
-```
-
-### CSV Knowledge Source
-```python
-from crewai.knowledge.source.csv_knowledge_source import CSVKnowledgeSource
-
-# Create a CSV knowledge source
-csv_source = CSVKnowledgeSource(
-    file_paths=["data.csv"]
-)
-
-# Create crew with CSV knowledge source or on agent level
-agent = Agent(
-    ...
-    knowledge_sources=[csv_source]
-)
-
-crew = Crew(
-    ...
-    knowledge_sources=[csv_source]
-)
-```
-
-### Excel Knowledge Source
-```python
-from crewai.knowledge.source.excel_knowledge_source import ExcelKnowledgeSource
-
-# Create an Excel knowledge source
-excel_source = ExcelKnowledgeSource(
-    file_paths=["spreadsheet.xlsx"]
-)
-
-# Create crew with Excel knowledge source on agents or crew level
-agent = Agent(
-    ...
-    knowledge_sources=[excel_source]
-)
-
-crew = Crew(
-    ...
-    knowledge_sources=[excel_source]
-)
-```
-
-### JSON Knowledge Source
-```python
-from crewai.knowledge.source.json_knowledge_source import JSONKnowledgeSource
-
-# Create a JSON knowledge source
-json_source = JSONKnowledgeSource(
-    file_paths=["data.json"]
-)
-
-# Create crew with JSON knowledge source on agents or crew level
-agent = Agent(
-    ...
-    knowledge_sources=[json_source]
-)
-
-crew = Crew(
-    ...
-    knowledge_sources=[json_source]
-)
-```
-
-## Knowledge Configuration
-
-### Chunking Configuration
-
-Knowledge sources automatically chunk content for better processing. 
-You can configure chunking behavior in your knowledge sources:
-
-```python
-from crewai.knowledge.source.string_knowledge_source import StringKnowledgeSource
-
-source = StringKnowledgeSource(
-    content="Your content here",
-    chunk_size=4000,      # Maximum size of each chunk (default: 4000)
-    chunk_overlap=200     # Overlap between chunks (default: 200)
-)
-```
-
-The chunking configuration helps in:
-- Breaking down large documents into manageable pieces
-- Maintaining context through chunk overlap
-- Optimizing retrieval accuracy
-
-### Embeddings Configuration
-
-You can also configure the embedder for the knowledge store. 
-This is useful if you want to use a different embedder for the knowledge store than the one used for the agents.
-The `embedder` parameter supports various embedding model providers that include:
-- `openai`: OpenAI's embedding models
-- `google`: Google's text embedding models
-- `azure`: Azure OpenAI embeddings
-- `ollama`: Local embeddings with Ollama
-- `vertexai`: Google Cloud VertexAI embeddings
-- `cohere`: Cohere's embedding models
-- `voyageai`: VoyageAI's embedding models
-- `bedrock`: AWS Bedrock embeddings
-- `huggingface`: Hugging Face models
-- `watson`: IBM Watson embeddings
-
-Here's an example of how to configure the embedder for the knowledge store using Google's `text-embedding-004` model:
-<CodeGroup>
-```python Example
-from crewai import Agent, Task, Crew, Process, LLM
-from crewai.knowledge.source.string_knowledge_source import StringKnowledgeSource
-import os
-
-# Get the GEMINI API key
-GEMINI_API_KEY = os.environ.get("GEMINI_API_KEY")
-
-# Create a knowledge source
-content = "Users name is John. He is 30 years old and lives in San Francisco."
-string_source = StringKnowledgeSource(
-    content=content,
-)
-
-# Create an LLM with a temperature of 0 to ensure deterministic outputs
-gemini_llm = LLM(
-    model="gemini/gemini-1.5-pro-002",
-    api_key=GEMINI_API_KEY,
-    temperature=0,
-)
-
-# Create an agent with the knowledge store
-agent = Agent(
-    role="About User",
-    goal="You know everything about the user.",
-    backstory="""You are a master at understanding people and their preferences.""",
-    verbose=True,
-    allow_delegation=False,
-    llm=gemini_llm,
-    embedder={
-        "provider": "google",
-        "config": {
-            "model": "models/text-embedding-004",
-            "api_key": GEMINI_API_KEY,
-        }
-    }
-)
-
-task = Task(
-    description="Answer the following questions about the user: {question}",
-    expected_output="An answer to the question.",
-    agent=agent,
-)
-
-crew = Crew(
-    agents=[agent],
-    tasks=[task],
-    verbose=True,
-    process=Process.sequential,
-    knowledge_sources=[string_source],
-    embedder={
-        "provider": "google",
-        "config": {
-            "model": "models/text-embedding-004",
-            "api_key": GEMINI_API_KEY,
-        }
-    }
-)
-
-result = crew.kickoff(inputs={"question": "What city does John live in and how old is he?"})
-```
-```text Output
-# Agent: About User
-## Task: Answer the following questions about the user: What city does John live in and how old is he?
-
-# Agent: About User
-## Final Answer: 
-John is 30 years old and lives in San Francisco.
-```
-</CodeGroup>
-## Clearing Knowledge
-
-If you need to clear the knowledge stored in CrewAI, you can use the `crewai reset-memories` command with the `--knowledge` option.
-
-```bash Command
-crewai reset-memories --knowledge
-```
-
-This is useful when you've updated your knowledge sources and want to ensure that the agents are using the most recent information.
-
-## Agent-Specific Knowledge
-
-While knowledge can be provided at the crew level using `crew.knowledge_sources`, individual agents can also have their own knowledge sources using the `knowledge_sources` parameter:
-
-```python Code
-from crewai import Agent, Task, Crew
-from crewai.knowledge.source.string_knowledge_source import StringKnowledgeSource
-
-# Create agent-specific knowledge about a product
-product_specs = StringKnowledgeSource(
-    content="""The XPS 13 laptop features:
-    - 13.4-inch 4K display
-    - Intel Core i7 processor
-    - 16GB RAM
-    - 512GB SSD storage
-    - 12-hour battery life""",
-    metadata={"category": "product_specs"}
-)
-
-# Create a support agent with product knowledge
-support_agent = Agent(
-    role="Technical Support Specialist",
-    goal="Provide accurate product information and support.",
-    backstory="You are an expert on our laptop products and specifications.",
-    knowledge_sources=[product_specs]  # Agent-specific knowledge
-)
-
-# Create a task that requires product knowledge
-support_task = Task(
-    description="Answer this customer question: {question}",
-    agent=support_agent
-)
-
-# Create and run the crew
-crew = Crew(
-    agents=[support_agent],
-    tasks=[support_task]
-)
-
-# Get answer about the laptop's specifications
-result = crew.kickoff(
-    inputs={"question": "What is the storage capacity of the XPS 13?"}
-)
-```
-
-<Info>
-  Benefits of agent-specific knowledge:
-  - Give agents specialized information for their roles
-  - Maintain separation of concerns between agents
-  - Combine with crew-level knowledge for layered information access
-</Info>
-
-## Custom Knowledge Sources
-
-CrewAI allows you to create custom knowledge sources for any type of data by extending the `BaseKnowledgeSource` class. Let's create a practical example that fetches and processes space news articles.
-
-#### Space News Knowledge Source Example
-
-<CodeGroup>
-
-```python Code
-from crewai import Agent, Task, Crew, Process, LLM
-from crewai.knowledge.source.base_knowledge_source import BaseKnowledgeSource
-import requests
-from datetime import datetime
-from typing import Dict, Any
-from pydantic import BaseModel, Field
-
-class SpaceNewsKnowledgeSource(BaseKnowledgeSource):
-    """Knowledge source that fetches data from Space News API."""
-
-    api_endpoint: str = Field(description="API endpoint URL")
-    limit: int = Field(default=10, description="Number of articles to fetch")
-
-    def load_content(self) -> Dict[Any, str]:
-        """Fetch and format space news articles."""
-        try:
-            response = requests.get(
-                f"{self.api_endpoint}?limit={self.limit}"
-            )
-            response.raise_for_status()
-
-            data = response.json()
-            articles = data.get('results', [])
-
-            formatted_data = self.validate_content(articles)
-            return {self.api_endpoint: formatted_data}
-        except Exception as e:
-            raise ValueError(f"Failed to fetch space news: {str(e)}")
-
-    def validate_content(self, articles: list) -> str:
-        """Format articles into readable text."""
-        formatted = "Space News Articles:\n\n"
-        for article in articles:
-            formatted += f"""
-                Title: {article['title']}
-                Published: {article['published_at']}
-                Summary: {article['summary']}
-                News Site: {article['news_site']}
-                URL: {article['url']}
-                -------------------"""
-        return formatted
-
-    def add(self) -> None:
-        """Process and store the articles."""
-        content = self.load_content()
-        for _, text in content.items():
-            chunks = self._chunk_text(text)
-            self.chunks.extend(chunks)
-
-        self._save_documents()
-
-# Create knowledge source
-recent_news = SpaceNewsKnowledgeSource(
-    api_endpoint="https://api.spaceflightnewsapi.net/v4/articles",
-    limit=10,
-)
-
-# Create specialized agent
-space_analyst = Agent(
-    role="Space News Analyst",
-    goal="Answer questions about space news accurately and comprehensively",
-    backstory="""You are a space industry analyst with expertise in space exploration,
-    satellite technology, and space industry trends. You excel at answering questions
-    about space news and providing detailed, accurate information.""",
-    knowledge_sources=[recent_news],
-    llm=LLM(model="gpt-4", temperature=0.0)
-)
-
-# Create task that handles user questions
-analysis_task = Task(
-    description="Answer this question about space news: {user_question}",
-    expected_output="A detailed answer based on the recent space news articles",
-    agent=space_analyst
-)
-
-# Create and run the crew
-crew = Crew(
-    agents=[space_analyst],
-    tasks=[analysis_task],
-    verbose=True,
-    process=Process.sequential
-)
-
-# Example usage
-result = crew.kickoff(
-    inputs={"user_question": "What are the latest developments in space exploration?"}
-)
-```
-
-```output Output
-# Agent: Space News Analyst
-## Task: Answer this question about space news: What are the latest developments in space exploration?
-
-
-# Agent: Space News Analyst
-## Final Answer:
-The latest developments in space exploration, based on recent space news articles, include the following:
-
-1. SpaceX has received the final regulatory approvals to proceed with the second integrated Starship/Super Heavy launch, scheduled for as soon as the morning of Nov. 17, 2023. This is a significant step in SpaceX's ambitious plans for space exploration and colonization. [Source: SpaceNews](https://spacenews.com/starship-cleared-for-nov-17-launch/)
-
-2. SpaceX has also informed the US Federal Communications Commission (FCC) that it plans to begin launching its first next-generation Starlink Gen2 satellites. This represents a major upgrade to the Starlink satellite internet service, which aims to provide high-speed internet access worldwide. [Source: Teslarati](https://www.teslarati.com/spacex-first-starlink-gen2-satellite-launch-2022/)
-
-3. AI startup Synthetaic has raised $15 million in Series B funding. The company uses artificial intelligence to analyze data from space and air sensors, which could have significant applications in space exploration and satellite technology. [Source: SpaceNews](https://spacenews.com/ai-startup-synthetaic-raises-15-million-in-series-b-funding/)
-
-4. The Space Force has formally established a unit within the U.S. Indo-Pacific Command, marking a permanent presence in the Indo-Pacific region. This could have significant implications for space security and geopolitics. [Source: SpaceNews](https://spacenews.com/space-force-establishes-permanent-presence-in-indo-pacific-region/)
-
-5. Slingshot Aerospace, a space tracking and data analytics company, is expanding its network of ground-based optical telescopes to increase coverage of low Earth orbit. This could improve our ability to track and analyze objects in low Earth orbit, including satellites and space debris. [Source: SpaceNews](https://spacenews.com/slingshots-space-tracking-network-to-extend-coverage-of-low-earth-orbit/)
-
-6. The National Natural Science Foundation of China has outlined a five-year project for researchers to study the assembly of ultra-large spacecraft. This could lead to significant advancements in spacecraft technology and space exploration capabilities. [Source: SpaceNews](https://spacenews.com/china-researching-challenges-of-kilometer-scale-ultra-large-spacecraft/)
-
-7. The Center for AEroSpace Autonomy Research (CAESAR) at Stanford University is focusing on spacecraft autonomy. The center held a kickoff event on May 22, 2024, to highlight the industry, academia, and government collaboration it seeks to foster. This could lead to significant advancements in autonomous spacecraft technology. [Source: SpaceNews](https://spacenews.com/stanford-center-focuses-on-spacecraft-autonomy/)
-```
-
-</CodeGroup>
-#### Key Components Explained
-
-1. **Custom Knowledge Source (`SpaceNewsKnowledgeSource`)**:
-
-   - Extends `BaseKnowledgeSource` for integration with CrewAI
-   - Configurable API endpoint and article limit
-   - Implements three key methods:
-     - `load_content()`: Fetches articles from the API
-     - `_format_articles()`: Structures the articles into readable text
-     - `add()`: Processes and stores the content
-
-2. **Agent Configuration**:
-
-   - Specialized role as a Space News Analyst
-   - Uses the knowledge source to access space news
-
-3. **Task Setup**:
-
-   - Takes a user question as input through `{user_question}`
-   - Designed to provide detailed answers based on the knowledge source
-
-4. **Crew Orchestration**:
-   - Manages the workflow between agent and task
-   - Handles input/output through the kickoff method
-
-This example demonstrates how to:
-
-- Create a custom knowledge source that fetches real-time data
-- Process and format external data for AI consumption
-- Use the knowledge source to answer specific user questions
-- Integrate everything seamlessly with CrewAI's agent system
-
-#### About the Spaceflight News API
-
-The example uses the [Spaceflight News API](https://api.spaceflightnewsapi.net/v4/docs/), which:
-
-- Provides free access to space-related news articles
-- Requires no authentication
-- Returns structured data about space news
-- Supports pagination and filtering
-
-You can customize the API query by modifying the endpoint URL:
-
-```python
-# Fetch more articles
-recent_news = SpaceNewsKnowledgeSource(
-    api_endpoint="https://api.spaceflightnewsapi.net/v4/articles",
-    limit=20,  # Increase the number of articles
-)
-
-# Add search parameters
-recent_news = SpaceNewsKnowledgeSource(
-    api_endpoint="https://api.spaceflightnewsapi.net/v4/articles?search=NASA", # Search for NASA news
-    limit=10,
-)
-```
-
-## Best Practices
-
-<AccordionGroup>
-  <Accordion title="Content Organization">
-    - Keep chunk sizes appropriate for your content type
-    - Consider content overlap for context preservation
-    - Organize related information into separate knowledge sources
-  </Accordion>
-
-  <Accordion title="Performance Tips">
-    - Adjust chunk sizes based on content complexity 
-    - Configure appropriate embedding models
-    - Consider using local embedding providers for faster processing
-  </Accordion>
-</AccordionGroup>

docs/concepts/langchain-tools.mdx

@@ -1,58 +0,0 @@
----
-title: Using LangChain Tools
-description: Learn how to integrate LangChain tools with CrewAI agents to enhance search-based queries and more.
-icon: link
----
-
-## Using LangChain Tools
-
-<Info>
-    CrewAI seamlessly integrates with LangChain's comprehensive [list of tools](https://python.langchain.com/docs/integrations/tools/), all of which can be used with CrewAI.
-</Info>
-
-```python Code
-import os
-from dotenv import load_dotenv
-from crewai import Agent, Task, Crew
-from crewai.tools import BaseTool
-from pydantic import Field
-from langchain_community.utilities import GoogleSerperAPIWrapper
-
-# Set up your SERPER_API_KEY key in an .env file, eg:
-# SERPER_API_KEY=<your api key>
-load_dotenv()
-
-search = GoogleSerperAPIWrapper()
-
-class SearchTool(BaseTool):
-    name: str = "Search"
-    description: str = "Useful for search-based queries. Use this to find current information about markets, companies, and trends."
-    search: GoogleSerperAPIWrapper = Field(default_factory=GoogleSerperAPIWrapper)
-
-    def _run(self, query: str) -> str:
-        """Execute the search query and return results"""
-        try:
-            return self.search.run(query)
-        except Exception as e:
-            return f"Error performing search: {str(e)}"
-
-# Create Agents
-researcher = Agent(
-    role='Research Analyst',
-    goal='Gather current market data and trends',
-    backstory="""You are an expert research analyst with years of experience in
-    gathering market intelligence. You're known for your ability to find
-    relevant and up-to-date market information and present it in a clear,
-    actionable format.""",
-    tools=[SearchTool()],
-    verbose=True
-)
-
-# rest of the code ...
-```
-
-## Conclusion
-
-Tools are pivotal in extending the capabilities of CrewAI agents, enabling them to undertake a broad spectrum of tasks and collaborate effectively.
-When building solutions with CrewAI, leverage both custom and existing tools to empower your agents and enhance the AI ecosystem. Consider utilizing error handling, caching mechanisms,
-and the flexibility of tool arguments to optimize your agents' performance and capabilities.

docs/concepts/lite-agent.mdx

@@ -1,242 +0,0 @@
----
-title: LiteAgent
-description: A lightweight, single-purpose agent for simple autonomous tasks within the CrewAI framework.
-icon: feather
----
-
-## Overview
-
-A `LiteAgent` is a streamlined version of CrewAI's Agent, designed for simpler, standalone tasks that don't require the full complexity of a crew-based workflow. It's perfect for quick automations, single-purpose tasks, or when you need a lightweight solution.
-
-<Tip>
-  Think of a LiteAgent as a specialized worker that excels at individual tasks.
-  While regular Agents are team players in a crew, LiteAgents are solo
-  performers optimized for specific operations.
-</Tip>
-
-## LiteAgent Attributes
-
-| Attribute                        | Parameter         | Type                   | Description                                                     |
-| :------------------------------- | :---------------- | :--------------------- | :-------------------------------------------------------------- |
-| **Role**                         | `role`            | `str`                  | Defines the agent's function and expertise.                     |
-| **Goal**                         | `goal`            | `str`                  | The specific objective that guides the agent's actions.         |
-| **Backstory**                    | `backstory`       | `str`                  | Provides context and personality to the agent.                  |
-| **LLM** _(optional)_             | `llm`             | `Union[str, LLM, Any]` | Language model powering the agent. Defaults to "gpt-4".         |
-| **Tools** _(optional)_           | `tools`           | `List[BaseTool]`       | Capabilities available to the agent. Defaults to an empty list. |
-| **Verbose** _(optional)_         | `verbose`         | `bool`                 | Enable detailed execution logs. Default is False.               |
-| **Response Format** _(optional)_ | `response_format` | `Type[BaseModel]`      | Pydantic model for structured output. Optional.                 |
-
-## Creating a LiteAgent
-
-Here's a simple example of creating and using a standalone LiteAgent:
-
-```python
-from typing import List, cast
-
-from crewai_tools import SerperDevTool
-from pydantic import BaseModel, Field
-
-from crewai.lite_agent import LiteAgent
-
-
-# Define a structured output format
-class MovieReview(BaseModel):
-    title: str = Field(description="The title of the movie")
-    rating: float = Field(description="Rating out of 10")
-    pros: List[str] = Field(description="List of positive aspects")
-    cons: List[str] = Field(description="List of negative aspects")
-
-
-# Create a LiteAgent
-critic = LiteAgent(
-    role="Movie Critic",
-    goal="Provide insightful movie reviews",
-    backstory="You are an experienced film critic known for balanced, thoughtful reviews.",
-    tools=[SerperDevTool()],
-    verbose=True,
-    response_format=MovieReview,
-)
-
-# Use the agent
-query = """
-Review the movie 'Inception'. Include:
-1. Your rating out of 10
-2. Key positive aspects
-3. Areas that could be improved
-"""
-
-result = critic.kickoff(query)
-
-
-# Access the structured output
-review = cast(MovieReview, result.pydantic)
-print(f"\nMovie Review: {review.title}")
-print(f"Rating: {review.rating}/10")
-print("\nPros:")
-for pro in review.pros:
-    print(f"- {pro}")
-print("\nCons:")
-for con in review.cons:
-    print(f"- {con}")
-
-```
-
-This example demonstrates the core features of a LiteAgent:
-
-- Structured output using Pydantic models
-- Tool integration with WebSearchTool
-- Simple execution with `kickoff()`
-- Easy access to both raw and structured results
-
-## Using LiteAgent in a Flow
-
-For more complex scenarios, you can integrate LiteAgents into a Flow. Here's an example of a market research flow:
-
-````python
-from typing import List
-from pydantic import BaseModel, Field
-from crewai.flow.flow import Flow, start, listen
-from crewai.lite_agent import LiteAgent
-from crewai.tools import WebSearchTool
-
-# Define a structured output format
-class MarketAnalysis(BaseModel):
-    key_trends: List[str] = Field(description="List of identified market trends")
-    market_size: str = Field(description="Estimated market size")
-    competitors: List[str] = Field(description="Major competitors in the space")
-
-# Define flow state
-class MarketResearchState(BaseModel):
-    product: str = ""
-    analysis: MarketAnalysis = None
-
-# Create a flow class
-class MarketResearchFlow(Flow[MarketResearchState]):
-    @start()
-    def initialize_research(self, product: str):
-        print(f"Starting market research for {product}")
-        self.state.product = product
-
-    @listen(initialize_research)
-    async def analyze_market(self):
-        # Create a LiteAgent for market research
-        analyst = LiteAgent(
-            role="Market Research Analyst",
-            goal=f"Analyze the market for {self.state.product}",
-            backstory="You are an experienced market analyst with expertise in "
-                     "identifying market trends and opportunities.",
-            tools=[WebSearchTool()],
-            verbose=True,
-            response_format=MarketAnalysis
-        )
-
-        # Define the research query
-        query = f"""
-        Research the market for {self.state.product}. Include:
-        1. Key market trends
-        2. Market size
-        3. Major competitors
-
-        Format your response according to the specified structure.
-        """
-
-        # Execute the analysis
-        result = await analyst.kickoff_async(query)
-        self.state.analysis = result.pydantic
-        return result.pydantic
-
-    @listen(analyze_market)
-    def present_results(self):
-        analysis = self.state.analysis
-        print("\nMarket Analysis Results")
-        print("=====================")
-
-        print("\nKey Market Trends:")
-        for trend in analysis.key_trends:
-            print(f"- {trend}")
-
-        print(f"\nMarket Size: {analysis.market_size}")
-
-        print("\nMajor Competitors:")
-        for competitor in analysis.competitors:
-            print(f"- {competitor}")
-
-# Usage example
-import asyncio
-
-async def run_flow():
-    flow = MarketResearchFlow()
-    result = await flow.kickoff(inputs={"product": "AI-powered chatbots"})
-    return result
-
-# Run the flow
-if __name__ == "__main__":
-    asyncio.run(run_flow())
-
-## Key Features
-
-### 1. Simplified Setup
-Unlike regular Agents, LiteAgents are designed for quick setup and standalone operation. They don't require crew configuration or task management.
-
-### 2. Structured Output
-LiteAgents support Pydantic models for response formatting, making it easy to get structured, type-safe data from your agent's operations.
-
-### 3. Tool Integration
-Just like regular Agents, LiteAgents can use tools to enhance their capabilities:
-```python
-from crewai.tools import SerperDevTool, CalculatorTool
-
-agent = LiteAgent(
-    role="Research Assistant",
-    goal="Find and analyze information",
-    tools=[SerperDevTool(), CalculatorTool()],
-    verbose=True
-)
-````
-
-### 4. Async Support
-
-LiteAgents support asynchronous execution through the `kickoff_async` method, making them suitable for non-blocking operations in your application.
-
-## Response Formatting
-
-LiteAgents support structured output through Pydantic models using the `response_format` parameter. This feature ensures type safety and consistent output structure, making it easier to work with agent responses in your application.
-
-### Basic Usage
-
-```python
-from pydantic import BaseModel, Field
-
-class SearchResult(BaseModel):
-    title: str = Field(description="The title of the found content")
-    summary: str = Field(description="A brief summary of the content")
-    relevance_score: float = Field(description="Relevance score from 0 to 1")
-
-agent = LiteAgent(
-    role="Search Specialist",
-    goal="Find and summarize relevant information",
-    response_format=SearchResult
-)
-
-result = await agent.kickoff_async("Find information about quantum computing")
-print(f"Title: {result.pydantic.title}")
-print(f"Summary: {result.pydantic.summary}")
-print(f"Relevance: {result.pydantic.relevance_score}")
-```
-
-### Handling Responses
-
-When using `response_format`, the agent's response will be available in two forms:
-
-1. **Raw Response**: Access the unstructured string response
-
-   ```python
-   result = await agent.kickoff_async("Analyze the market")
-   print(result.raw)  # Original LLM response
-   ```
-
-2. **Structured Response**: Access the parsed Pydantic model
-   ```python
-   print(result.pydantic)  # Parsed response as Pydantic model
-   print(result.pydantic.dict())  # Convert to dictionary
-   ```

docs/concepts/llamaindex-tools.mdx

@@ -1,71 +0,0 @@
----
-title: Using LlamaIndex Tools
-description: Learn how to integrate LlamaIndex tools with CrewAI agents to enhance search-based queries and more.
-icon: toolbox
----
-
-## Using LlamaIndex Tools
-
-<Info>
-    CrewAI seamlessly integrates with LlamaIndex’s comprehensive toolkit for RAG (Retrieval-Augmented Generation) and agentic pipelines, enabling advanced search-based queries and more. 
-</Info>
-
-Here are the available built-in tools offered by LlamaIndex.
-
-```python Code
-from crewai import Agent
-from crewai_tools import LlamaIndexTool
-
-# Example 1: Initialize from FunctionTool
-from llama_index.core.tools import FunctionTool
-
-your_python_function = lambda ...: ...
-og_tool = FunctionTool.from_defaults(
-    your_python_function, 
-    name="<name>", 
-    description='<description>'
-)
-tool = LlamaIndexTool.from_tool(og_tool)
-
-# Example 2: Initialize from LlamaHub Tools
-from llama_index.tools.wolfram_alpha import WolframAlphaToolSpec
-wolfram_spec = WolframAlphaToolSpec(app_id="<app_id>")
-wolfram_tools = wolfram_spec.to_tool_list()
-tools = [LlamaIndexTool.from_tool(t) for t in wolfram_tools]
-
-# Example 3: Initialize Tool from a LlamaIndex Query Engine
-query_engine = index.as_query_engine()
-query_tool = LlamaIndexTool.from_query_engine(
-    query_engine,
-    name="Uber 2019 10K Query Tool",
-    description="Use this tool to lookup the 2019 Uber 10K Annual Report"
-)
-
-# Create and assign the tools to an agent
-agent = Agent(
-    role='Research Analyst',
-    goal='Provide up-to-date market analysis',
-    backstory='An expert analyst with a keen eye for market trends.',
-    tools=[tool, *tools, query_tool]
-)
-
-# rest of the code ...
-```
-
-## Steps to Get Started
-
-To effectively use the LlamaIndexTool, follow these steps:
-
-<Steps>
-    <Step title="Package Installation">
-    Make sure that `crewai[tools]` package is installed in your Python environment:
-    <CodeGroup>
-        ```shell Terminal
-        pip install 'crewai[tools]'
-        ```
-    </CodeGroup>
-    </Step>
-    <Step title="Install and Use LlamaIndex">
-    Follow the LlamaIndex documentation [LlamaIndex Documentation](https://docs.llamaindex.ai/) to set up a RAG/agent pipeline.
-    </Step>
-</Steps>

docs/concepts/llms.mdx

@@ -1,795 +0,0 @@
----
-title: 'LLMs'
-description: 'A comprehensive guide to configuring and using Large Language Models (LLMs) in your CrewAI projects'
-icon: 'microchip-ai'
----
-
-<Note>
-  CrewAI integrates with multiple LLM providers through LiteLLM, giving you the flexibility to choose the right model for your specific use case. This guide will help you understand how to configure and use different LLM providers in your CrewAI projects.
-</Note>
-
-## What are LLMs?
-
-Large Language Models (LLMs) are the core intelligence behind CrewAI agents. They enable agents to understand context, make decisions, and generate human-like responses. Here's what you need to know:
-
-<CardGroup cols={2}>
-  <Card title="LLM Basics" icon="brain">
-    Large Language Models are AI systems trained on vast amounts of text data. They power the intelligence of your CrewAI agents, enabling them to understand and generate human-like text.
-  </Card>
-  <Card title="Context Window" icon="window">
-    The context window determines how much text an LLM can process at once. Larger windows (e.g., 128K tokens) allow for more context but may be more expensive and slower.
-  </Card>
-  <Card title="Temperature" icon="temperature-three-quarters">
-    Temperature (0.0 to 1.0) controls response randomness. Lower values (e.g., 0.2) produce more focused, deterministic outputs, while higher values (e.g., 0.8) increase creativity and variability.
-  </Card>
-  <Card title="Provider Selection" icon="server">
-    Each LLM provider (e.g., OpenAI, Anthropic, Google) offers different models with varying capabilities, pricing, and features. Choose based on your needs for accuracy, speed, and cost.
-  </Card>
-</CardGroup>
-
-## Setting Up Your LLM
-
-There are three ways to configure LLMs in CrewAI. Choose the method that best fits your workflow:
-
-<Tabs>
-  <Tab title="1. Environment Variables">
-    The simplest way to get started. Set these variables in your environment:
-
-    ```bash
-    # Required: Your API key for authentication
-    OPENAI_API_KEY=<your-api-key>
-
-    # Optional: Default model selection
-    OPENAI_MODEL_NAME=gpt-4o-mini  # Default if not set
-
-    # Optional: Organization ID (if applicable)
-    OPENAI_ORGANIZATION_ID=<your-org-id>
-    ```
-
-    <Warning>
-      Never commit API keys to version control. Use environment files (.env) or your system's secret management.
-    </Warning>
-  </Tab>
-  <Tab title="2. YAML Configuration">
-    Create a YAML file to define your agent configurations. This method is great for version control and team collaboration:
-
-    ```yaml
-    researcher:
-        role: Research Specialist
-        goal: Conduct comprehensive research and analysis
-        backstory: A dedicated research professional with years of experience
-        verbose: true
-        llm: openai/gpt-4o-mini # your model here
-        # (see provider configuration examples below for more)
-    ```
-
-    <Info>
-      The YAML configuration allows you to:
-      - Version control your agent settings
-      - Easily switch between different models
-      - Share configurations across team members
-      - Document model choices and their purposes
-    </Info>
-  </Tab>
-  <Tab title="3. Direct Code">
-    For maximum flexibility, configure LLMs directly in your Python code:
-
-    ```python
-    from crewai import LLM
-
-    # Basic configuration
-    llm = LLM(model="gpt-4")
-
-    # Advanced configuration with detailed parameters
-    llm = LLM(
-        model="gpt-4o-mini",
-        temperature=0.7,        # Higher for more creative outputs
-        timeout=120,           # Seconds to wait for response
-        max_tokens=4000,       # Maximum length of response
-        top_p=0.9,            # Nucleus sampling parameter
-        frequency_penalty=0.1, # Reduce repetition
-        presence_penalty=0.1,  # Encourage topic diversity
-        response_format={"type": "json"},  # For structured outputs
-        seed=42               # For reproducible results
-    )
-    ```
-
-    <Info>
-      Parameter explanations:
-      - `temperature`: Controls randomness (0.0-1.0)
-      - `timeout`: Maximum wait time for response
-      - `max_tokens`: Limits response length
-      - `top_p`: Alternative to temperature for sampling
-      - `frequency_penalty`: Reduces word repetition
-      - `presence_penalty`: Encourages new topics
-      - `response_format`: Specifies output structure
-      - `seed`: Ensures consistent outputs
-    </Info>
-  </Tab>
-</Tabs>
-
-## Provider Configuration Examples
-
-
-CrewAI supports a multitude of LLM providers, each offering unique features, authentication methods, and model capabilities.
-In this section, you'll find detailed examples that help you select, configure, and optimize the LLM that best fits your project's needs.
-
-<AccordionGroup>
-  <Accordion title="OpenAI">
-    Set the following environment variables in your `.env` file:
-
-    ```toml Code
-    # Required
-    OPENAI_API_KEY=sk-...
-
-    # Optional
-    OPENAI_API_BASE=<custom-base-url>
-    OPENAI_ORGANIZATION=<your-org-id>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    from crewai import LLM
-
-    llm = LLM(
-        model="openai/gpt-4", # call model by provider/model_name
-        temperature=0.8,
-        max_tokens=150,
-        top_p=0.9,
-        frequency_penalty=0.1,
-        presence_penalty=0.1,
-        stop=["END"],
-        seed=42
-    )
-    ```
-
-    OpenAI is one of the leading providers of LLMs with a wide range of models and features.
-
-    | Model               | Context Window   | Best For                                      |
-    |---------------------|------------------|-----------------------------------------------|
-    | GPT-4               | 8,192 tokens     | High-accuracy tasks, complex reasoning        |
-    | GPT-4 Turbo         | 128,000 tokens   | Long-form content, document analysis          |
-    | GPT-4o & GPT-4o-mini  | 128,000 tokens  | Cost-effective large context processing       |
-    | o3-mini             | 200,000 tokens   | Fast reasoning, complex reasoning             |
-    | o1-mini             | 128,000 tokens   | Fast reasoning, complex reasoning             |
-    | o1-preview          | 128,000 tokens   | Fast reasoning, complex reasoning             |
-    | o1                  | 200,000 tokens   | Fast reasoning, complex reasoning             |
-  </Accordion>
-
-  <Accordion title="Anthropic">
-    ```toml Code
-    # Required
-    ANTHROPIC_API_KEY=sk-ant-...
-
-    # Optional
-    ANTHROPIC_API_BASE=<custom-base-url>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="anthropic/claude-3-sonnet-20240229-v1:0",
-        temperature=0.7
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Google">
-    Set the following environment variables in your `.env` file:
-
-    ```toml Code
-    # Option 1: Gemini accessed with an API key.
-    # https://ai.google.dev/gemini-api/docs/api-key
-    GEMINI_API_KEY=<your-api-key>
-
-    # Option 2: Vertex AI IAM credentials for Gemini, Anthropic, and Model Garden.
-    # https://cloud.google.com/vertex-ai/generative-ai/docs/overview
-    ```
-
-    Get credentials from your Google Cloud Console and save it to a JSON file with the following code:
-    ```python Code
-    import json
-
-    file_path = 'path/to/vertex_ai_service_account.json'
-
-    # Load the JSON file
-    with open(file_path, 'r') as file:
-        vertex_credentials = json.load(file)
-
-    # Convert the credentials to a JSON string
-    vertex_credentials_json = json.dumps(vertex_credentials)
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    from crewai import LLM
-
-    llm = LLM(
-        model="gemini/gemini-1.5-pro-latest",
-        temperature=0.7,
-        vertex_credentials=vertex_credentials_json
-    )
-    ```
-    Google offers a range of powerful models optimized for different use cases:
-
-    | Model                  | Context Window | Best For                                                          |
-    |-----------------------|----------------|------------------------------------------------------------------|
-    | gemini-2.0-flash-exp  | 1M tokens      | Higher quality at faster speed, multimodal model, good for most tasks |
-    | gemini-1.5-flash      | 1M tokens      | Balanced multimodal model, good for most tasks                    |
-    | gemini-1.5-flash-8B   | 1M tokens      | Fastest, most cost-efficient, good for high-frequency tasks       |
-    | gemini-1.5-pro        | 2M tokens      | Best performing, wide variety of reasoning tasks including logical reasoning, coding, and creative collaboration |
-  </Accordion>
-
-  <Accordion title="Azure">
-    ```toml Code
-    # Required
-    AZURE_API_KEY=<your-api-key>
-    AZURE_API_BASE=<your-resource-url>
-    AZURE_API_VERSION=<api-version>
-
-    # Optional
-    AZURE_AD_TOKEN=<your-azure-ad-token>
-    AZURE_API_TYPE=<your-azure-api-type>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="azure/gpt-4",
-        api_version="2023-05-15"
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="AWS Bedrock">
-    ```toml Code
-    AWS_ACCESS_KEY_ID=<your-access-key>
-    AWS_SECRET_ACCESS_KEY=<your-secret-key>
-    AWS_DEFAULT_REGION=<your-region>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="bedrock/anthropic.claude-3-sonnet-20240229-v1:0"
-    )
-    ```
-
-    Before using Amazon Bedrock, make sure you have boto3 installed in your environment
-
-    [Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html) is a managed service that provides access to multiple foundation models from top AI companies through a unified API, enabling secure and responsible AI application development.
-
-    | Model                   | Context Window       | Best For                                                          |
-    |-------------------------|----------------------|-------------------------------------------------------------------|
-    | Amazon Nova Pro         | Up to 300k tokens    | High-performance, model balancing accuracy, speed, and cost-effectiveness across diverse tasks. |
-    | Amazon Nova Micro       | Up to 128k tokens    | High-performance, cost-effective text-only model optimized for lowest latency responses. |
-    | Amazon Nova Lite        | Up to 300k tokens    | High-performance, affordable multimodal processing for images, video, and text with real-time capabilities. |
-    | Claude 3.7 Sonnet       | Up to 128k tokens    | High-performance, best for complex reasoning, coding & AI agents |
-    | Claude 3.5 Sonnet v2    | Up to 200k tokens    | State-of-the-art model specialized in software engineering, agentic capabilities, and computer interaction at optimized cost. |
-    | Claude 3.5 Sonnet       | Up to 200k tokens    | High-performance model delivering superior intelligence and reasoning across diverse tasks with optimal speed-cost balance. |
-    | Claude 3.5 Haiku        | Up to 200k tokens    | Fast, compact multimodal model optimized for quick responses and seamless human-like interactions |
-    | Claude 3 Sonnet         | Up to 200k tokens    | Multimodal model balancing intelligence and speed for high-volume deployments. |
-    | Claude 3 Haiku          | Up to 200k tokens    | Compact, high-speed multimodal model optimized for quick responses and natural conversational interactions |
-    | Claude 3 Opus           | Up to 200k tokens    | Most advanced multimodal model exceling at complex tasks with human-like reasoning and superior contextual understanding. |
-    | Claude 2.1              | Up to 200k tokens    | Enhanced version with expanded context window, improved reliability, and reduced hallucinations for long-form and RAG applications |
-    | Claude                  | Up to 100k tokens    | Versatile model excelling in sophisticated dialogue, creative content, and precise instruction following. |
-    | Claude Instant          | Up to 100k tokens    | Fast, cost-effective model for everyday tasks like dialogue, analysis, summarization, and document Q&A |
-    | Llama 3.1 405B Instruct | Up to 128k tokens    | Advanced LLM for synthetic data generation, distillation, and inference for chatbots, coding, and domain-specific tasks. |
-    | Llama 3.1 70B Instruct  | Up to 128k tokens    | Powers complex conversations with superior contextual understanding, reasoning and text generation. |
-    | Llama 3.1 8B Instruct   | Up to 128k tokens    | Advanced state-of-the-art model with language understanding, superior reasoning, and text generation. |
-    | Llama 3 70B Instruct    | Up to 8k tokens      | Powers complex conversations with superior contextual understanding, reasoning and text generation. |
-    | Llama 3 8B Instruct     | Up to 8k tokens      | Advanced state-of-the-art LLM with language understanding, superior reasoning, and text generation. |
-    | Titan Text G1 - Lite    | Up to 4k tokens      | Lightweight, cost-effective model optimized for English tasks and fine-tuning with focus on summarization and content generation. |
-    | Titan Text G1 - Express | Up to 8k tokens      | Versatile model for general language tasks, chat, and RAG applications with support for English and 100+ languages. |
-    | Cohere Command          | Up to 4k tokens      | Model specialized in following user commands and delivering practical enterprise solutions. |
-    | Jurassic-2 Mid          | Up to 8,191 tokens   | Cost-effective model balancing quality and affordability for diverse language tasks like Q&A, summarization, and content generation. |
-    | Jurassic-2 Ultra        | Up to 8,191 tokens   | Model for advanced text generation and comprehension, excelling in complex tasks like analysis and content creation. |
-    | Jamba-Instruct          | Up to 256k tokens    | Model with extended context window optimized for cost-effective text generation, summarization, and Q&A. |
-    | Mistral 7B Instruct     | Up to 32k tokens     | This LLM follows instructions, completes requests, and generates creative text. |
-    | Mistral 8x7B Instruct   | Up to 32k tokens     | An MOE LLM that follows instructions, completes requests, and generates creative text. |
-
-  </Accordion>
-
-  <Accordion title="Amazon SageMaker">
-    ```toml Code
-    AWS_ACCESS_KEY_ID=<your-access-key>
-    AWS_SECRET_ACCESS_KEY=<your-secret-key>
-    AWS_DEFAULT_REGION=<your-region>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="sagemaker/<my-endpoint>"
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Mistral">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    MISTRAL_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="mistral/mistral-large-latest",
-        temperature=0.7
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Nvidia NIM">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    NVIDIA_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="nvidia_nim/meta/llama3-70b-instruct",
-        temperature=0.7
-    )
-    ```
-
-    Nvidia NIM provides a comprehensive suite of models for various use cases, from general-purpose tasks to specialized applications.
-
-    | Model                                                                   | Context Window | Best For                                                          |
-    |-------------------------------------------------------------------------|----------------|-------------------------------------------------------------------|
-    | nvidia/mistral-nemo-minitron-8b-8k-instruct                              | 8,192 tokens   | State-of-the-art small language model delivering superior accuracy for chatbot, virtual assistants, and content generation. |
-    | nvidia/nemotron-4-mini-hindi-4b-instruct                                 | 4,096 tokens   | A bilingual Hindi-English SLM for on-device inference, tailored specifically for Hindi Language. |
-    | nvidia/llama-3.1-nemotron-70b-instruct                                  | 128k tokens    | Customized for enhanced helpfulness in responses                  |
-    | nvidia/llama3-chatqa-1.5-8b                                                | 128k tokens    | Advanced LLM to generate high-quality, context-aware responses for chatbots and search engines. |
-    | nvidia/llama3-chatqa-1.5-70b                                               | 128k tokens    | Advanced LLM to generate high-quality, context-aware responses for chatbots and search engines. |
-    | nvidia/vila                                                             | 128k tokens    | Multi-modal vision-language model that understands text/img/video and creates informative responses |
-    | nvidia/neva-22                                                          | 4,096 tokens   | Multi-modal vision-language model that understands text/images and generates informative responses |
-    | nvidia/nemotron-mini-4b-instruct                                         | 8,192 tokens   | General-purpose tasks |
-    | nvidia/usdcode-llama3-70b-instruct                                       | 128k tokens    | State-of-the-art LLM that answers OpenUSD knowledge queries and generates USD-Python code. |
-    | nvidia/nemotron-4-340b-instruct                                          | 4,096 tokens   | Creates diverse synthetic data that mimics the characteristics of real-world data. |
-    | meta/codellama-70b                                                      | 100k tokens    | LLM capable of generating code from natural language and vice versa. |
-    | meta/llama2-70b                                                         | 4,096 tokens   | Cutting-edge large language AI model capable of generating text and code in response to prompts. |
-    | meta/llama3-8b-instruct                                                | 8,192 tokens   | Advanced state-of-the-art LLM with language understanding, superior reasoning, and text generation. |
-    | meta/llama3-70b-instruct                                               | 8,192 tokens   | Powers complex conversations with superior contextual understanding, reasoning and text generation. |
-    | meta/llama-3.1-8b-instruct                                             | 128k tokens    | Advanced state-of-the-art model with language understanding, superior reasoning, and text generation. |
-    | meta/llama-3.1-70b-instruct                                            | 128k tokens    | Powers complex conversations with superior contextual understanding, reasoning and text generation. |
-    | meta/llama-3.1-405b-instruct                                           | 128k tokens    | Advanced LLM for synthetic data generation, distillation, and inference for chatbots, coding, and domain-specific tasks. |
-    | meta/llama-3.2-1b-instruct                                             | 128k tokens    | Advanced state-of-the-art small language model with language understanding, superior reasoning, and text generation. |
-    | meta/llama-3.2-3b-instruct                                             | 128k tokens    | Advanced state-of-the-art small language model with language understanding, superior reasoning, and text generation. |
-    | meta/llama-3.2-11b-vision-instruct                                     | 128k tokens    | Advanced state-of-the-art small language model with language understanding, superior reasoning, and text generation. |
-    | meta/llama-3.2-90b-vision-instruct                                     | 128k tokens    | Advanced state-of-the-art small language model with language understanding, superior reasoning, and text generation. |
-    | google/gemma-7b                                                        | 8,192 tokens   | Cutting-edge text generation model text understanding, transformation, and code generation. |
-    | google/gemma-2b                                                        | 8,192 tokens   | Cutting-edge text generation model text understanding, transformation, and code generation. |
-    | google/codegemma-7b                                                    | 8,192 tokens   | Cutting-edge model built on Google's Gemma-7B specialized for code generation and code completion. |
-    | google/codegemma-1.1-7b                                               | 8,192 tokens   | Advanced programming model for code generation, completion, reasoning, and instruction following. |
-    | google/recurrentgemma-2b                                              | 8,192 tokens   | Novel recurrent architecture based language model for faster inference when generating long sequences. |
-    | google/gemma-2-9b-it                                                  | 8,192 tokens   | Cutting-edge text generation model text understanding, transformation, and code generation. |
-    | google/gemma-2-27b-it                                                 | 8,192 tokens   | Cutting-edge text generation model text understanding, transformation, and code generation. |
-    | google/gemma-2-2b-it                                                  | 8,192 tokens   | Cutting-edge text generation model text understanding, transformation, and code generation. |
-    | google/deplot                                                         | 512 tokens     | One-shot visual language understanding model that translates images of plots into tables. |
-    | google/paligemma                                                      | 8,192 tokens   | Vision language model adept at comprehending text and visual inputs to produce informative responses. |
-    | mistralai/mistral-7b-instruct-v0.2                                   | 32k tokens     | This LLM follows instructions, completes requests, and generates creative text. |
-    | mistralai/mixtral-8x7b-instruct-v0.1                                 | 8,192 tokens   | An MOE LLM that follows instructions, completes requests, and generates creative text. |
-    | mistralai/mistral-large                                              | 4,096 tokens   | Creates diverse synthetic data that mimics the characteristics of real-world data. |
-    | mistralai/mixtral-8x22b-instruct-v0.1                               | 8,192 tokens   | Creates diverse synthetic data that mimics the characteristics of real-world data. |
-    | mistralai/mistral-7b-instruct-v0.3                                  | 32k tokens     | This LLM follows instructions, completes requests, and generates creative text. |
-    | nv-mistralai/mistral-nemo-12b-instruct                              | 128k tokens    | Most advanced language model for reasoning, code, multilingual tasks; runs on a single GPU. |
-    | mistralai/mamba-codestral-7b-v0.1                                   | 256k tokens    | Model for writing and interacting with code across a wide range of programming languages and tasks. |
-    | microsoft/phi-3-mini-128k-instruct                                  | 128K tokens    | Lightweight, state-of-the-art open LLM with strong math and logical reasoning skills. |
-    | microsoft/phi-3-mini-4k-instruct                                    | 4,096 tokens   | Lightweight, state-of-the-art open LLM with strong math and logical reasoning skills. |
-    | microsoft/phi-3-small-8k-instruct                                   | 8,192 tokens   | Lightweight, state-of-the-art open LLM with strong math and logical reasoning skills. |
-    | microsoft/phi-3-small-128k-instruct                                 | 128K tokens    | Lightweight, state-of-the-art open LLM with strong math and logical reasoning skills. |
-    | microsoft/phi-3-medium-4k-instruct                                  | 4,096 tokens   | Lightweight, state-of-the-art open LLM with strong math and logical reasoning skills. |
-    | microsoft/phi-3-medium-128k-instruct                                | 128K tokens    | Lightweight, state-of-the-art open LLM with strong math and logical reasoning skills. |
-    | microsoft/phi-3.5-mini-instruct                                     | 128K tokens    | Lightweight multilingual LLM powering AI applications in latency bound, memory/compute constrained environments |
-    | microsoft/phi-3.5-moe-instruct                                      | 128K tokens    | Advanced LLM based on Mixture of Experts architecure to deliver compute efficient content generation |
-    | microsoft/kosmos-2                                                  | 1,024 tokens   | Groundbreaking multimodal model designed to understand and reason about visual elements in images. |
-    | microsoft/phi-3-vision-128k-instruct                               | 128k tokens    | Cutting-edge open multimodal model exceling in high-quality reasoning from images. |
-    | microsoft/phi-3.5-vision-instruct                                  | 128k tokens    | Cutting-edge open multimodal model exceling in high-quality reasoning from images. |
-    | databricks/dbrx-instruct                                           | 12k tokens     | A general-purpose LLM with state-of-the-art performance in language understanding, coding, and RAG. |
-    | snowflake/arctic                                                   | 1,024 tokens   | Delivers high efficiency inference for enterprise applications focused on SQL generation and coding. |
-    | aisingapore/sea-lion-7b-instruct                                  | 4,096 tokens   | LLM to represent and serve the linguistic and cultural diversity of Southeast Asia |
-    | ibm/granite-8b-code-instruct                                      | 4,096 tokens   | Software programming LLM for code generation, completion, explanation, and multi-turn conversion. |
-    | ibm/granite-34b-code-instruct                                     | 8,192 tokens   | Software programming LLM for code generation, completion, explanation, and multi-turn conversion. |
-    | ibm/granite-3.0-8b-instruct                                       | 4,096 tokens   | Advanced Small Language Model supporting RAG, summarization, classification, code, and agentic AI |
-    | ibm/granite-3.0-3b-a800m-instruct                                | 4,096 tokens   | Highly efficient Mixture of Experts model for RAG, summarization, entity extraction, and classification |
-    | mediatek/breeze-7b-instruct                                       | 4,096 tokens   | Creates diverse synthetic data that mimics the characteristics of real-world data. |
-    | upstage/solar-10.7b-instruct                                      | 4,096 tokens   | Excels in NLP tasks, particularly in instruction-following, reasoning, and mathematics. |
-    | writer/palmyra-med-70b-32k                                        | 32k tokens     | Leading LLM for accurate, contextually relevant responses in the medical domain. |
-    | writer/palmyra-med-70b                                            | 32k tokens     | Leading LLM for accurate, contextually relevant responses in the medical domain. |
-    | writer/palmyra-fin-70b-32k                                        | 32k tokens     | Specialized LLM for financial analysis, reporting, and data processing |
-    | 01-ai/yi-large                                                    | 32k tokens     | Powerful model trained on English and Chinese for diverse tasks including chatbot and creative writing. |
-    | deepseek-ai/deepseek-coder-6.7b-instruct                         | 2k tokens      | Powerful coding model offering advanced capabilities in code generation, completion, and infilling |
-    | rakuten/rakutenai-7b-instruct                                     | 1,024 tokens   | Advanced state-of-the-art LLM with language understanding, superior reasoning, and text generation. |
-    | rakuten/rakutenai-7b-chat                                         | 1,024 tokens   | Advanced state-of-the-art LLM with language understanding, superior reasoning, and text generation. |
-    | baichuan-inc/baichuan2-13b-chat                                  | 4,096 tokens   | Support Chinese and English chat, coding, math, instruction following, solving quizzes |
-  </Accordion>
-
-  <Accordion title="Local NVIDIA NIM Deployed using WSL2">
-    
-    NVIDIA NIM enables you to run powerful LLMs locally on your Windows machine using WSL2 (Windows Subsystem for Linux). 
-    This approach allows you to leverage your NVIDIA GPU for private, secure, and cost-effective AI inference without relying on cloud services. 
-    Perfect for development, testing, or production scenarios where data privacy or offline capabilities are required.
-    
-    Here is a step-by-step guide to setting up a local NVIDIA NIM model:
-    
-    1. Follow installation instructions from [NVIDIA Website](https://docs.nvidia.com/nim/wsl2/latest/getting-started.html)
-
-    2. Install the local model. For Llama 3.1-8b follow [instructions](https://build.nvidia.com/meta/llama-3_1-8b-instruct/deploy)
-
-    3. Configure your crewai local models:
-  
-    ```python Code
-    from crewai.llm import LLM
-
-    local_nvidia_nim_llm = LLM(
-        model="openai/meta/llama-3.1-8b-instruct", # it's an openai-api compatible model
-        base_url="http://localhost:8000/v1",
-        api_key="<your_api_key|any text if you have not configured it>", # api_key is required, but you can use any text
-    )
-
-    # Then you can use it in your crew:
-
-    @CrewBase
-    class MyCrew():
-        # ...
-
-        @agent
-        def researcher(self) -> Agent:
-            return Agent(
-                config=self.agents_config['researcher'],
-                llm=local_nvidia_nim_llm
-            )
-        
-        # ...
-    ```
-  </Accordion>
-
-  <Accordion title="Groq">
-    Set the following environment variables in your `.env` file:
-
-    ```toml Code
-    GROQ_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="groq/llama-3.2-90b-text-preview",
-        temperature=0.7
-    )
-    ```
-    | Model             | Context Window   | Best For                                   |
-    |-------------------|------------------|--------------------------------------------|
-    | Llama 3.1 70B/8B  | 131,072 tokens   | High-performance, large context tasks      |
-    | Llama 3.2 Series  | 8,192 tokens     | General-purpose tasks                      |
-    | Mixtral 8x7B      | 32,768 tokens    | Balanced performance and context           |
-  </Accordion>
-
-  <Accordion title="IBM watsonx.ai">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    # Required
-    WATSONX_URL=<your-url>
-    WATSONX_APIKEY=<your-apikey>
-    WATSONX_PROJECT_ID=<your-project-id>
-
-    # Optional
-    WATSONX_TOKEN=<your-token>
-    WATSONX_DEPLOYMENT_SPACE_ID=<your-space-id>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="watsonx/meta-llama/llama-3-1-70b-instruct",
-        base_url="https://api.watsonx.ai/v1"
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Ollama (Local LLMs)">
-    1. Install Ollama: [ollama.ai](https://ollama.ai/)
-    2. Run a model: `ollama run llama3`
-    3. Configure:
-
-    ```python Code
-    llm = LLM(
-        model="ollama/llama3:70b",
-        base_url="http://localhost:11434"
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Fireworks AI">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    FIREWORKS_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="fireworks_ai/accounts/fireworks/models/llama-v3-70b-instruct",
-        temperature=0.7
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Perplexity AI">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    PERPLEXITY_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="llama-3.1-sonar-large-128k-online",
-        base_url="https://api.perplexity.ai/"
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="Hugging Face">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    HUGGINGFACE_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="huggingface/meta-llama/Meta-Llama-3.1-8B-Instruct",
-        base_url="your_api_endpoint"
-    )
-    ```
-  </Accordion>
-
-  <Accordion title="SambaNova">
-    Set the following environment variables in your `.env` file:
-
-    ```toml Code
-    SAMBANOVA_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="sambanova/Meta-Llama-3.1-8B-Instruct",
-        temperature=0.7
-    )
-    ```
-    | Model              | Context Window         | Best For                                     |
-    |--------------------|------------------------|----------------------------------------------|
-    | Llama 3.1 70B/8B   | Up to 131,072 tokens   | High-performance, large context tasks        |
-    | Llama 3.1 405B     | 8,192 tokens           | High-performance and output quality          |
-    | Llama 3.2 Series   | 8,192 tokens           | General-purpose, multimodal tasks            |
-    | Llama 3.3 70B      | Up to 131,072 tokens   | High-performance and output quality          |
-    | Qwen2 familly      | 8,192 tokens           | High-performance and output quality          |
-  </Accordion>
-
-  <Accordion title="Cerebras">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    # Required
-    CEREBRAS_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="cerebras/llama3.1-70b",
-        temperature=0.7,
-        max_tokens=8192
-    )
-    ```
-
-    <Info>
-      Cerebras features:
-      - Fast inference speeds
-      - Competitive pricing
-      - Good balance of speed and quality
-      - Support for long context windows
-    </Info>
-  </Accordion>
-
-  <Accordion title="Open Router">
-    Set the following environment variables in your `.env` file:
-    ```toml Code
-    OPENROUTER_API_KEY=<your-api-key>
-    ```
-
-    Example usage in your CrewAI project:
-    ```python Code
-    llm = LLM(
-        model="openrouter/deepseek/deepseek-r1",
-        base_url="https://openrouter.ai/api/v1",
-        api_key=OPENROUTER_API_KEY
-    )
-    ```
-
-    <Info>
-      Open Router models:
-      - openrouter/deepseek/deepseek-r1
-      - openrouter/deepseek/deepseek-chat
-    </Info>
-  </Accordion>
-</AccordionGroup>
-
-## Streaming Responses
-
-CrewAI supports streaming responses from LLMs, allowing your application to receive and process outputs in real-time as they're generated.
-
-<Tabs>
-  <Tab title="Basic Setup">
-    Enable streaming by setting the `stream` parameter to `True` when initializing your LLM:
-
-    ```python
-    from crewai import LLM
-
-    # Create an LLM with streaming enabled
-    llm = LLM(
-        model="openai/gpt-4o",
-        stream=True  # Enable streaming
-    )
-    ```
-
-    When streaming is enabled, responses are delivered in chunks as they're generated, creating a more responsive user experience.
-  </Tab>
-  
-  <Tab title="Event Handling">
-    CrewAI emits events for each chunk received during streaming:
-    
-    ```python
-    from crewai import LLM
-    from crewai.utilities.events import EventHandler, LLMStreamChunkEvent
-    
-    class MyEventHandler(EventHandler):
-        def on_llm_stream_chunk(self, event: LLMStreamChunkEvent):
-            # Process each chunk as it arrives
-            print(f"Received chunk: {event.chunk}")
-    
-    # Register the event handler
-    from crewai.utilities.events import crewai_event_bus
-    crewai_event_bus.register_handler(MyEventHandler())
-    ```
-  </Tab>
-</Tabs>
-
-## Structured LLM Calls
-
-CrewAI supports structured responses from LLM calls by allowing you to define a `response_format` using a Pydantic model. This enables the framework to automatically parse and validate the output, making it easier to integrate the response into your application without manual post-processing.
-
-For example, you can define a Pydantic model to represent the expected response structure and pass it as the `response_format` when instantiating the LLM. The model will then be used to convert the LLM output into a structured Python object.
-
-```python Code
-from crewai import LLM
-
-class Dog(BaseModel):
-    name: str
-    age: int
-    breed: str
-
-
-llm = LLM(model="gpt-4o", response_format=Dog)
-
-response = llm.call(
-    "Analyze the following messages and return the name, age, and breed. "
-    "Meet Kona! She is 3 years old and is a black german shepherd."
-)
-print(response)
-
-# Output:
-# Dog(name='Kona', age=3, breed='black german shepherd')
-```
-
-## Advanced Features and Optimization
-
-Learn how to get the most out of your LLM configuration:
-
-<AccordionGroup>
-  <Accordion title="Context Window Management">
-    CrewAI includes smart context management features:
-
-    ```python
-    from crewai import LLM
-
-    # CrewAI automatically handles:
-    # 1. Token counting and tracking
-    # 2. Content summarization when needed
-    # 3. Task splitting for large contexts
-
-    llm = LLM(
-        model="gpt-4",
-        max_tokens=4000,  # Limit response length
-    )
-    ```
-
-    <Info>
-      Best practices for context management:
-      1. Choose models with appropriate context windows
-      2. Pre-process long inputs when possible
-      3. Use chunking for large documents
-      4. Monitor token usage to optimize costs
-    </Info>
-  </Accordion>
-
-  <Accordion title="Performance Optimization">
-    <Steps>
-      <Step title="Token Usage Optimization">
-        Choose the right context window for your task:
-        - Small tasks (up to 4K tokens): Standard models
-        - Medium tasks (between 4K-32K): Enhanced models
-        - Large tasks (over 32K): Large context models
-
-        ```python
-        # Configure model with appropriate settings
-        llm = LLM(
-            model="openai/gpt-4-turbo-preview",
-            temperature=0.7,    # Adjust based on task
-            max_tokens=4096,    # Set based on output needs
-            timeout=300        # Longer timeout for complex tasks
-        )
-        ```
-        <Tip>
-          - Lower temperature (0.1 to 0.3) for factual responses
-          - Higher temperature (0.7 to 0.9) for creative tasks
-        </Tip>
-      </Step>
-
-      <Step title="Best Practices">
-        1. Monitor token usage
-        2. Implement rate limiting
-        3. Use caching when possible
-        4. Set appropriate max_tokens limits
-      </Step>
-    </Steps>
-
-    <Info>
-      Remember to regularly monitor your token usage and adjust your configuration as needed to optimize costs and performance.
-    </Info>
-  </Accordion>
-</AccordionGroup>
-
-## Common Issues and Solutions
-
-<Tabs>
-  <Tab title="Authentication">
-    <Warning>
-      Most authentication issues can be resolved by checking API key format and environment variable names.
-    </Warning>
-
-    ```bash
-    # OpenAI
-    OPENAI_API_KEY=sk-...
-
-    # Anthropic
-    ANTHROPIC_API_KEY=sk-ant-...
-    ```
-  </Tab>
-  <Tab title="Model Names">
-    <Check>
-      Always include the provider prefix in model names
-    </Check>
-
-    ```python
-    # Correct
-    llm = LLM(model="openai/gpt-4")
-
-    # Incorrect
-    llm = LLM(model="gpt-4")
-    ```
-  </Tab>
-  <Tab title="Context Length">
-    <Tip>
-      Use larger context models for extensive tasks
-    </Tip>
-    
-    ```python
-    # Large context model
-    llm = LLM(model="openai/gpt-4o")  # 128K tokens
-    ```
-  </Tab>
-</Tabs>

docs/concepts/memory.mdx

@@ -1,728 +0,0 @@
----
-title: Memory
-description: Leveraging memory systems in the CrewAI framework to enhance agent capabilities.
-icon: database
----
-
-## Introduction to Memory Systems in CrewAI
-
-The crewAI framework introduces a sophisticated memory system designed to significantly enhance the capabilities of AI agents. 
-This system comprises `short-term memory`, `long-term memory`, `entity memory`, and `contextual memory`, each serving a unique purpose in aiding agents to remember, 
-reason, and learn from past interactions.
-
-## Memory System Components
-
-| Component            | Description                                                                                                             |
-| :------------------- | :---------------------------------------------------------------------------------------------------------------------- |
-| **Short-Term Memory**| Temporarily stores recent interactions and outcomes using `RAG`, enabling agents to recall and utilize information relevant to their current context during the current executions.|
-| **Long-Term Memory** | Preserves valuable insights and learnings from past executions, allowing agents to build and refine their knowledge over time. |
-| **Entity Memory**    | Captures and organizes information about entities (people, places, concepts) encountered during tasks, facilitating deeper understanding and relationship mapping. Uses `RAG` for storing entity information. |
-| **Contextual Memory**| Maintains the context of interactions by combining `ShortTermMemory`, `LongTermMemory`, and `EntityMemory`, aiding in the coherence and relevance of agent responses over a sequence of tasks or a conversation. |
-| **External Memory**  | Enables integration with external memory systems and providers (like Mem0), allowing for specialized memory storage and retrieval across different applications. Supports custom storage implementations for flexible memory management. |
-| **User Memory**      | ⚠️ **DEPRECATED**: This component is deprecated and will be removed in a future version. Please use [External Memory](#using-external-memory) instead. |
-
-## How Memory Systems Empower Agents
-
-1. **Contextual Awareness**: With short-term and contextual memory, agents gain the ability to maintain context over a conversation or task sequence, leading to more coherent and relevant responses.
-
-2. **Experience Accumulation**: Long-term memory allows agents to accumulate experiences, learning from past actions to improve future decision-making and problem-solving.
-
-3. **Entity Understanding**: By maintaining entity memory, agents can recognize and remember key entities, enhancing their ability to process and interact with complex information.
-
-## Implementing Memory in Your Crew
-
-When configuring a crew, you can enable and customize each memory component to suit the crew's objectives and the nature of tasks it will perform.
-By default, the memory system is disabled, and you can ensure it is active by setting `memory=True` in the crew configuration. 
-The memory will use OpenAI embeddings by default, but you can change it by setting `embedder` to a different model. 
-It's also possible to initialize the memory instance with your own instance.
-
-The 'embedder' only applies to **Short-Term Memory** which uses Chroma for RAG.
-The **Long-Term Memory** uses SQLite3 to store task results. Currently, there is no way to override these storage implementations.
-The data storage files are saved into a platform-specific location found using the appdirs package,
-and the name of the project can be overridden using the **CREWAI_STORAGE_DIR** environment variable.
-
-### Example: Configuring Memory for a Crew
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-# Assemble your crew with memory capabilities
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True
-)
-```
-
-### Example: Use Custom Memory Instances e.g FAISS as the VectorDB
-
-```python Code
-from crewai import Crew, Process
-from crewai.memory import LongTermMemory, ShortTermMemory, EntityMemory
-from crewai.memory.storage.rag_storage import RAGStorage
-from crewai.memory.storage.ltm_sqlite_storage import LTMSQLiteStorage
-from typing import List, Optional
-
-# Assemble your crew with memory capabilities
-my_crew: Crew = Crew(
-    agents = [...],
-    tasks = [...],
-    process = Process.sequential,
-    memory = True,
-    # Long-term memory for persistent storage across sessions
-    long_term_memory = LongTermMemory(
-        storage=LTMSQLiteStorage(
-            db_path="/my_crew1/long_term_memory_storage.db"
-        )
-    ),
-    # Short-term memory for current context using RAG
-    short_term_memory = ShortTermMemory(
-        storage = RAGStorage(
-                embedder_config={
-                    "provider": "openai",
-                    "config": {
-                        "model": 'text-embedding-3-small'
-                    }
-                },
-                type="short_term",
-                path="/my_crew1/"
-            )
-        ),
-    ),
-    # Entity memory for tracking key information about entities
-    entity_memory = EntityMemory(
-        storage=RAGStorage(
-            embedder_config={
-                "provider": "openai",
-                "config": {
-                    "model": 'text-embedding-3-small'
-                }
-            },
-            type="short_term",
-            path="/my_crew1/"
-        )
-    ),
-    verbose=True,
-)
-```
-
-## Security Considerations
-
-When configuring memory storage:
-- Use environment variables for storage paths (e.g., `CREWAI_STORAGE_DIR`)
-- Never hardcode sensitive information like database credentials
-- Consider access permissions for storage directories
-- Use relative paths when possible to maintain portability
-
-Example using environment variables:
-```python
-import os
-from crewai import Crew
-from crewai.memory import LongTermMemory
-from crewai.memory.storage.ltm_sqlite_storage import LTMSQLiteStorage
-
-# Configure storage path using environment variable
-storage_path = os.getenv("CREWAI_STORAGE_DIR", "./storage")
-crew = Crew(
-    memory=True,
-    long_term_memory=LongTermMemory(
-        storage=LTMSQLiteStorage(
-            db_path="{storage_path}/memory.db".format(storage_path=storage_path)
-        )
-    )
-)
-```
-
-## Configuration Examples
-
-### Basic Memory Configuration
-```python
-from crewai import Crew
-from crewai.memory import LongTermMemory
-
-# Simple memory configuration
-crew = Crew(memory=True)  # Uses default storage locations
-```
-
-### Custom Storage Configuration
-```python
-from crewai import Crew
-from crewai.memory import LongTermMemory
-from crewai.memory.storage.ltm_sqlite_storage import LTMSQLiteStorage
-
-# Configure custom storage paths
-crew = Crew(
-    memory=True,
-    long_term_memory=LongTermMemory(
-        storage=LTMSQLiteStorage(db_path="./memory.db")
-    )
-)
-```
-
-## Integrating Mem0 for Enhanced User Memory
-
-[Mem0](https://mem0.ai/) is a self-improving memory layer for LLM applications, enabling personalized AI experiences. 
-
-
-### Using Mem0 API platform
-
-To include user-specific memory you can get your API key [here](https://app.mem0.ai/dashboard/api-keys) and refer the [docs](https://docs.mem0.ai/platform/quickstart#4-1-create-memories) for adding user preferences. In this case `user_memory` is set to `MemoryClient` from mem0.
-
-
-```python Code
-import os
-from crewai import Crew, Process
-from mem0 import MemoryClient
-
-# Set environment variables for Mem0
-os.environ["MEM0_API_KEY"] = "m0-xx"
-
-# Step 1: Create a Crew with User Memory
-
-crew = Crew(
-    agents=[...],
-    tasks=[...],
-    verbose=True,
-    process=Process.sequential,
-    memory=True,
-    memory_config={
-        "provider": "mem0",
-        "config": {"user_id": "john"},
-        "user_memory" : {} #Set user_memory explicitly to a dictionary, we are working on this issue.
-    },
-)
-```
-
-#### Additional Memory Configuration Options
-If you want to access a specific organization and project, you can set the `org_id` and `project_id` parameters in the memory configuration.
-
-```python Code
-from crewai import Crew
-
-crew = Crew(
-    agents=[...],
-    tasks=[...],
-    verbose=True,
-    memory=True,
-    memory_config={
-        "provider": "mem0",
-        "config": {"user_id": "john", "org_id": "my_org_id", "project_id": "my_project_id"},
-        "user_memory" : {} #Set user_memory explicitly to a dictionary, we are working on this issue.
-    },
-)
-```
-
-### Using Local Mem0 memory
-If you want to use local mem0 memory, with a custom configuration, you can set a parameter `local_mem0_config` in the config itself.
-If both os environment key is set and local_mem0_config is given, the API platform takes higher priority over the local configuration.
-Check [this](https://docs.mem0.ai/open-source/python-quickstart#run-mem0-locally) mem0 local configuration docs for more understanding.
-In this case `user_memory` is set to `Memory` from mem0.
-
-
-```python Code
-from crewai import Crew
-
-
-#local mem0 config
-config = {
-    "vector_store": {
-        "provider": "qdrant",
-        "config": {
-            "host": "localhost",
-            "port": 6333
-        }
-    },
-    "llm": {
-        "provider": "openai",
-        "config": {
-            "api_key": "your-api-key",
-            "model": "gpt-4"
-        }
-    },
-    "embedder": {
-        "provider": "openai",
-        "config": {
-            "api_key": "your-api-key",
-            "model": "text-embedding-3-small"
-        }
-    },
-    "graph_store": {
-        "provider": "neo4j",
-        "config": {
-            "url": "neo4j+s://your-instance",
-            "username": "neo4j",
-            "password": "password"
-        }
-    },
-    "history_db_path": "/path/to/history.db",
-    "version": "v1.1",
-    "custom_fact_extraction_prompt": "Optional custom prompt for fact extraction for memory",
-    "custom_update_memory_prompt": "Optional custom prompt for update memory"
-}
-
-crew = Crew(
-    agents=[...],
-    tasks=[...],
-    verbose=True,
-    memory=True,
-    memory_config={
-        "provider": "mem0",
-        "config": {"user_id": "john", 'local_mem0_config': config},
-        "user_memory" : {} #Set user_memory explicitly to a dictionary, we are working on this issue.
-    },
-)
-```
-
-### Using External Memory
-
-External Memory is a powerful feature that allows you to integrate external memory systems with your CrewAI applications. This is particularly useful when you want to use specialized memory providers or maintain memory across different applications.
-
-#### Basic Usage with Mem0
-
-The most common way to use External Memory is with Mem0 as the provider:
-
-```python
-from crewai import Agent, Crew, Process, Task
-from crewai.memory.external.external_memory import ExternalMemory
-
-agent = Agent(
-    role="You are a helpful assistant",
-    goal="Plan a vacation for the user",
-    backstory="You are a helpful assistant that can plan a vacation for the user",
-    verbose=True,
-)
-task = Task(
-    description="Give things related to the user's vacation",
-    expected_output="A plan for the vacation",
-    agent=agent,
-)
-
-crew = Crew(
-    agents=[agent],
-    tasks=[task],
-    verbose=True,
-    process=Process.sequential,
-    memory=True,
-    external_memory=ExternalMemory(
-        embedder_config={"provider": "mem0", "config": {"user_id": "U-123"}} # you can provide an entire Mem0 configuration
-    ),
-)
-
-crew.kickoff(
-    inputs={"question": "which destination is better for a beach vacation?"}
-)
-```
-
-#### Using External Memory with Custom Storage
-
-You can also create custom storage implementations for External Memory. Here's an example of how to create a custom storage:
-
-```python
-from crewai import Agent, Crew, Process, Task
-from crewai.memory.external.external_memory import ExternalMemory
-from crewai.memory.storage.interface import Storage
-
-
-class CustomStorage(Storage):
-    def __init__(self):
-        self.memories = []
-
-    def save(self, value, metadata=None, agent=None):
-        self.memories.append({"value": value, "metadata": metadata, "agent": agent})
-
-    def search(self, query, limit=10, score_threshold=0.5):
-        # Implement your search logic here
-        return []
-
-    def reset(self):
-        self.memories = []
-
-
-# Create external memory with custom storage
-external_memory = ExternalMemory(
-    storage=CustomStorage(),
-    embedder_config={"provider": "mem0", "config": {"user_id": "U-123"}},
-)
-
-agent = Agent(
-    role="You are a helpful assistant",
-    goal="Plan a vacation for the user",
-    backstory="You are a helpful assistant that can plan a vacation for the user",
-    verbose=True,
-)
-task = Task(
-    description="Give things related to the user's vacation",
-    expected_output="A plan for the vacation",
-    agent=agent,
-)
-
-crew = Crew(
-    agents=[agent],
-    tasks=[task],
-    verbose=True,
-    process=Process.sequential,
-    memory=True,
-    external_memory=external_memory,
-)
-
-crew.kickoff(
-    inputs={"question": "which destination is better for a beach vacation?"}
-)
-```
-
-
-## Additional Embedding Providers
-
-### Using OpenAI embeddings (already default)
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "openai",
-        "config": {
-            "model": 'text-embedding-3-small'
-        }
-    }
-)
-```
-Alternatively, you can directly pass the OpenAIEmbeddingFunction to the embedder parameter.
-
-Example:
-```python Code
-from crewai import Crew, Agent, Task, Process
-from chromadb.utils.embedding_functions import OpenAIEmbeddingFunction
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "openai",
-        "config": {
-            "model": 'text-embedding-3-small'
-        }
-    }
-)
-```
-
-### Using Ollama embeddings
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "ollama",
-        "config": {
-            "model": "mxbai-embed-large"
-        }
-    }
-)
-```
-
-### Using Google AI embeddings
-
-#### Prerequisites
-Before using Google AI embeddings, ensure you have:
-- Access to the Gemini API
-- The necessary API keys and permissions
-
-You will need to update your *pyproject.toml* dependencies:
-```YAML
-dependencies = [
-    "google-generativeai>=0.8.4", #main version in January/2025 - crewai v.0.100.0 and crewai-tools 0.33.0
-    "crewai[tools]>=0.100.0,<1.0.0"
-]
-```
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "google",
-        "config": {
-            "api_key": "<YOUR_API_KEY>",
-            "model": "<model_name>"
-        }
-    }
-)
-```
-
-### Using Azure OpenAI embeddings
-
-```python Code
-from chromadb.utils.embedding_functions import OpenAIEmbeddingFunction
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "openai",
-        "config": {
-            "api_key": "YOUR_API_KEY",
-            "api_base": "YOUR_API_BASE_PATH",
-            "api_version": "YOUR_API_VERSION",
-            "model_name": 'text-embedding-3-small'
-        }
-    }
-)
-```
-
-### Using Vertex AI embeddings
-
-```python Code
-from chromadb.utils.embedding_functions import GoogleVertexEmbeddingFunction
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "vertexai",
-        "config": {
-            "project_id"="YOUR_PROJECT_ID",
-            "region"="YOUR_REGION",
-            "api_key"="YOUR_API_KEY",
-            "model_name"="textembedding-gecko"
-        }
-    }
-)
-```
-
-### Using Cohere embeddings
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "cohere",
-        "config": {
-            "api_key": "YOUR_API_KEY",
-            "model": "<model_name>"
-        }
-    }
-)
-```
-### Using VoyageAI embeddings
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "voyageai",
-        "config": {
-            "api_key": "YOUR_API_KEY",
-            "model": "<model_name>"
-        }
-    }
-)
-```
-### Using HuggingFace embeddings
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "huggingface",
-        "config": {
-            "api_url": "<api_url>",
-        }
-    }
-)
-```
-
-### Using Watson embeddings
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-# Note: Ensure you have installed and imported `ibm_watsonx_ai` for Watson embeddings to work.
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "watson",
-        "config": {
-            "model": "<model_name>",
-            "api_url": "<api_url>",
-            "api_key": "<YOUR_API_KEY>",
-            "project_id": "<YOUR_PROJECT_ID>",
-        }
-    }
-)
-```
-
-### Using Amazon Bedrock embeddings
-
-```python Code
-# Note: Ensure you have installed `boto3` for Bedrock embeddings to work.
-
-import os
-import boto3
-from crewai import Crew, Agent, Task, Process
-
-boto3_session = boto3.Session(
-    region_name=os.environ.get("AWS_REGION_NAME"),
-    aws_access_key_id=os.environ.get("AWS_ACCESS_KEY_ID"),
-    aws_secret_access_key=os.environ.get("AWS_SECRET_ACCESS_KEY")
-)
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    embedder={
-    "provider": "bedrock",
-        "config":{
-            "session": boto3_session,
-            "model": "amazon.titan-embed-text-v2:0",
-            "vector_dimension": 1024
-        }
-    }
-    verbose=True
-)
-```
-
-### Adding Custom Embedding Function
-
-```python Code
-from crewai import Crew, Agent, Task, Process
-from chromadb import Documents, EmbeddingFunction, Embeddings
-
-# Create a custom embedding function
-class CustomEmbedder(EmbeddingFunction):
-    def __call__(self, input: Documents) -> Embeddings:
-        # generate embeddings
-        return [1, 2, 3] # this is a dummy embedding
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "custom",
-        "config": {
-            "embedder": CustomEmbedder()
-        }
-    }
-)
-```
-
-### Resetting Memory via cli
-
-```shell
-crewai reset-memories [OPTIONS]
-```
-
-#### Resetting Memory Options
-
-| Option             | Description                      | Type           | Default |
-| :----------------- | :------------------------------- | :------------- | :------ |
-| `-l`, `--long`     | Reset LONG TERM memory.          | Flag (boolean) | False   |
-| `-s`, `--short`    | Reset SHORT TERM memory.         | Flag (boolean) | False   |
-| `-e`, `--entities` | Reset ENTITIES memory.           | Flag (boolean) | False   |
-| `-k`, `--kickoff-outputs` | Reset LATEST KICKOFF TASK OUTPUTS. | Flag (boolean) | False   |
-| `-kn`, `--knowledge` | Reset KNOWLEDEGE storage | Flag (boolean) | False   |
-| `-a`, `--all`      | Reset ALL memories.              | Flag (boolean) | False   |
-
-Note: To use the cli command you need to have your crew in a file called crew.py in the same directory.
-
-
-
-
-### Resetting Memory via crew object
-
-```python
-
-my_crew = Crew(
-    agents=[...],
-    tasks=[...],
-    process=Process.sequential,
-    memory=True,
-    verbose=True,
-    embedder={
-        "provider": "custom",
-        "config": {
-            "embedder": CustomEmbedder()
-        }
-    }
-)
-
-my_crew.reset_memories(command_type = 'all') # Resets all the memory
-```
-
-#### Resetting Memory Options
-
-| Command Type       | Description                      |
-| :----------------- | :------------------------------- |
-| `long`             | Reset LONG TERM memory.          | 
-| `short`            | Reset SHORT TERM memory.         | 
-| `entities`         | Reset ENTITIES memory.           | 
-| `kickoff_outputs`  | Reset LATEST KICKOFF TASK OUTPUTS. |
-| `knowledge`        | Reset KNOWLEDGE memory.          |
-| `all`              | Reset ALL memories.              |
-
-
-## Benefits of Using CrewAI's Memory System
-
-- 🦾 **Adaptive Learning:** Crews become more efficient over time, adapting to new information and refining their approach to tasks.
-- 🫡 **Enhanced Personalization:** Memory enables agents to remember user preferences and historical interactions, leading to personalized experiences.
-- 🧠 **Improved Problem Solving:** Access to a rich memory store aids agents in making more informed decisions, drawing on past learnings and contextual insights.
-
-## Conclusion
-
-Integrating CrewAI's memory system into your projects is straightforward. By leveraging the provided memory components and configurations, 
-you can quickly empower your agents with the ability to remember, reason, and learn from their interactions, unlocking new levels of intelligence and capability.

docs/concepts/planning.mdx

@@ -1,150 +0,0 @@
----
-title: Planning
-description: Learn how to add planning to your CrewAI Crew and improve their performance.
-icon: brain
----
-
-## Introduction
-
-The planning feature in CrewAI allows you to add planning capability to your crew. When enabled, before each Crew iteration, 
-all Crew information is sent to an AgentPlanner that will plan the tasks step by step, and this plan will be added to each task description.
-
-### Using the Planning Feature
-
-Getting started with the planning feature is very easy, the only step required is to add `planning=True` to your Crew:
-
-<CodeGroup>
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-# Assemble your crew with planning capabilities
-my_crew = Crew(
-    agents=self.agents,
-    tasks=self.tasks,
-    process=Process.sequential,
-    planning=True,
-)
-```
-</CodeGroup>
-
-From this point on, your crew will have planning enabled, and the tasks will be planned before each iteration.
-
-#### Planning LLM
-
-Now you can define the LLM that will be used to plan the tasks. 
-
-When running the base case example, you will see something like the output below, which represents the output of the `AgentPlanner` 
-responsible for creating the step-by-step logic to add to the Agents' tasks.
-
-<CodeGroup>
-```python Code
-from crewai import Crew, Agent, Task, Process
-
-# Assemble your crew with planning capabilities and custom LLM
-my_crew = Crew(
-    agents=self.agents,
-    tasks=self.tasks,
-    process=Process.sequential,
-    planning=True,
-    planning_llm="gpt-4o"
-)
-
-# Run the crew
-my_crew.kickoff()
-```
-
-```markdown Result
-[2024-07-15 16:49:11][INFO]: Planning the crew execution
-**Step-by-Step Plan for Task Execution**
-
-**Task Number 1: Conduct a thorough research about AI LLMs**
-
-**Agent:** AI LLMs Senior Data Researcher
-
-**Agent Goal:** Uncover cutting-edge developments in AI LLMs
-
-**Task Expected Output:** A list with 10 bullet points of the most relevant information about AI LLMs
-
-**Task Tools:** None specified
-
-**Agent Tools:** None specified
-
-**Step-by-Step Plan:**
-
-1. **Define Research Scope:**
-
-   - Determine the specific areas of AI LLMs to focus on, such as advancements in architecture, use cases, ethical considerations, and performance metrics.
-
-2. **Identify Reliable Sources:**
-
-   - List reputable sources for AI research, including academic journals, industry reports, conferences (e.g., NeurIPS, ACL), AI research labs (e.g., OpenAI, Google AI), and online databases (e.g., IEEE Xplore, arXiv).
-
-3. **Collect Data:**
-
-   - Search for the latest papers, articles, and reports published in 2024 and early 2025.
-   - Use keywords like "Large Language Models 2025", "AI LLM advancements", "AI ethics 2025", etc.
-
-4. **Analyze Findings:**
-
-   - Read and summarize the key points from each source.
-   - Highlight new techniques, models, and applications introduced in the past year.
-
-5. **Organize Information:**
-
-   - Categorize the information into relevant topics (e.g., new architectures, ethical implications, real-world applications).
-   - Ensure each bullet point is concise but informative.
-
-6. **Create the List:**
-
-   - Compile the 10 most relevant pieces of information into a bullet point list.
-   - Review the list to ensure clarity and relevance.
-
-**Expected Output:**
-
-A list with 10 bullet points of the most relevant information about AI LLMs.
-
----
-
-**Task Number 2: Review the context you got and expand each topic into a full section for a report**
-
-**Agent:** AI LLMs Reporting Analyst
-
-**Agent Goal:** Create detailed reports based on AI LLMs data analysis and research findings
-
-**Task Expected Output:** A fully fledged report with the main topics, each with a full section of information. Formatted as markdown without '```'
-
-**Task Tools:** None specified
-
-**Agent Tools:** None specified
-
-**Step-by-Step Plan:**
-
-1. **Review the Bullet Points:**
-   - Carefully read through the list of 10 bullet points provided by the AI LLMs Senior Data Researcher.
-
-2. **Outline the Report:**
-   - Create an outline with each bullet point as a main section heading.
-   - Plan sub-sections under each main heading to cover different aspects of the topic.
-
-3. **Research Further Details:**
-   - For each bullet point, conduct additional research if necessary to gather more detailed information.
-   - Look for case studies, examples, and statistical data to support each section.
-
-4. **Write Detailed Sections:**
-   - Expand each bullet point into a comprehensive section.
-   - Ensure each section includes an introduction, detailed explanation, examples, and a conclusion.
-   - Use markdown formatting for headings, subheadings, lists, and emphasis.
-
-5. **Review and Edit:**
-   - Proofread the report for clarity, coherence, and correctness.
-   - Make sure the report flows logically from one section to the next.
-   - Format the report according to markdown standards.
-
-6. **Finalize the Report:**
-   - Ensure the report is complete with all sections expanded and detailed.
-   - Double-check formatting and make any necessary adjustments.
-
-**Expected Output:**
-A fully fledged report with the main topics, each with a full section of information. Formatted as markdown without '```'.
-```
-</CodeGroup>

docs/concepts/processes.mdx

@@ -1,65 +0,0 @@
----
-title: Processes
-description: Detailed guide on workflow management through processes in CrewAI, with updated implementation details.
-icon: bars-staggered
----
-
-## Understanding Processes
-<Tip>
-  Processes orchestrate the execution of tasks by agents, akin to project management in human teams. 
-  These processes ensure tasks are distributed and executed efficiently, in alignment with a predefined strategy.
-</Tip>
-
-## Process Implementations
-
-- **Sequential**: Executes tasks sequentially, ensuring tasks are completed in an orderly progression.
-- **Hierarchical**: Organizes tasks in a managerial hierarchy, where tasks are delegated and executed based on a structured chain of command. A manager language model (`manager_llm`) or a custom manager agent (`manager_agent`) must be specified in the crew to enable the hierarchical process, facilitating the creation and management of tasks by the manager.
-- **Consensual Process (Planned)**: Aiming for collaborative decision-making among agents on task execution, this process type introduces a democratic approach to task management within CrewAI. It is planned for future development and is not currently implemented in the codebase.
-
-## The Role of Processes in Teamwork
-Processes enable individual agents to operate as a cohesive unit, streamlining their efforts to achieve common objectives with efficiency and coherence.
-
-## Assigning Processes to a Crew
-To assign a process to a crew, specify the process type upon crew creation to set the execution strategy. For a hierarchical process, ensure to define `manager_llm` or `manager_agent` for the manager agent.
-
-```python
-from crewai import Crew, Process
-
-# Example: Creating a crew with a sequential process
-crew = Crew(
-    agents=my_agents,
-    tasks=my_tasks,
-    process=Process.sequential
-)
-
-# Example: Creating a crew with a hierarchical process
-# Ensure to provide a manager_llm or manager_agent
-crew = Crew(
-    agents=my_agents,
-    tasks=my_tasks,
-    process=Process.hierarchical,
-    manager_llm="gpt-4o"
-    # or
-    # manager_agent=my_manager_agent
-)
-```
-**Note:** Ensure `my_agents` and `my_tasks` are defined prior to creating a `Crew` object, and for the hierarchical process, either `manager_llm` or `manager_agent` is also required.
-
-## Sequential Process
-
-This method mirrors dynamic team workflows, progressing through tasks in a thoughtful and systematic manner. Task execution follows the predefined order in the task list, with the output of one task serving as context for the next.
-
-To customize task context, utilize the `context` parameter in the `Task` class to specify outputs that should be used as context for subsequent tasks.
-
-## Hierarchical Process
-
-Emulates a corporate hierarchy, CrewAI allows specifying a custom manager agent or automatically creates one, requiring the specification of a manager language model (`manager_llm`). This agent oversees task execution, including planning, delegation, and validation. Tasks are not pre-assigned; the manager allocates tasks to agents based on their capabilities, reviews outputs, and assesses task completion.
-
-## Process Class: Detailed Overview
-
-The `Process` class is implemented as an enumeration (`Enum`), ensuring type safety and restricting process values to the defined types (`sequential`, `hierarchical`). The consensual process is planned for future inclusion, emphasizing our commitment to continuous development and innovation.
-
-## Conclusion
-
-The structured collaboration facilitated by processes within CrewAI is crucial for enabling systematic teamwork among agents. 
-This documentation has been updated to reflect the latest features, enhancements, and the planned integration of the Consensual Process, ensuring users have access to the most current and comprehensive information.

docs/concepts/tasks.mdx

@@ -1,909 +0,0 @@
----
-title: Tasks
-description: Detailed guide on managing and creating tasks within the CrewAI framework.
-icon: list-check
----
-
-## Overview of a Task
-
-In the CrewAI framework, a `Task` is a specific assignment completed by an `Agent`.
-
-Tasks provide all necessary details for execution, such as a description, the agent responsible, required tools, and more, facilitating a wide range of action complexities.
-
-Tasks within CrewAI can be collaborative, requiring multiple agents to work together. This is managed through the task properties and orchestrated by the Crew's process, enhancing teamwork and efficiency.
-
-<Note type="info" title="Enterprise Enhancement: Visual Task Builder">
-CrewAI Enterprise includes a Visual Task Builder in Crew Studio that simplifies complex task creation and chaining. Design your task flows visually and test them in real-time without writing code.
-
-![Task Builder Screenshot](../images/enterprise/crew-studio-quickstart.png)
-
-The Visual Task Builder enables:
-- Drag-and-drop task creation
-- Visual task dependencies and flow
-- Real-time testing and validation
-- Easy sharing and collaboration
-</Note>
-
-### Task Execution Flow
-
-Tasks can be executed in two ways:
-- **Sequential**: Tasks are executed in the order they are defined
-- **Hierarchical**: Tasks are assigned to agents based on their roles and expertise
-
-The execution flow is defined when creating the crew:
-```python Code
-crew = Crew(
-    agents=[agent1, agent2],
-    tasks=[task1, task2],
-    process=Process.sequential  # or Process.hierarchical
-)
-```
-
-## Task Attributes
-
-| Attribute                        | Parameters        | Type                          | Description                                                                                                          |
-| :------------------------------- | :---------------- | :---------------------------- | :------------------------------------------------------------------------------------------------------------------- |
-| **Description**                  | `description`     | `str`                         | A clear, concise statement of what the task entails.                                                                 |
-| **Expected Output**              | `expected_output` | `str`                         | A detailed description of what the task's completion looks like.                                                     |
-| **Name** _(optional)_            | `name`            | `Optional[str]`               | A name identifier for the task.                                                                                      |
-| **Agent** _(optional)_           | `agent`           | `Optional[BaseAgent]`         | The agent responsible for executing the task.                                                                        |
-| **Tools** _(optional)_           | `tools`           | `List[BaseTool]`              | The tools/resources the agent is limited to use for this task.                                                       |
-| **Context** _(optional)_         | `context`         | `Optional[List["Task"]]`      | Other tasks whose outputs will be used as context for this task.                                                     |
-| **Async Execution** _(optional)_ | `async_execution` | `Optional[bool]`              | Whether the task should be executed asynchronously. Defaults to False.                                               |
-| **Human Input** _(optional)_     | `human_input`     | `Optional[bool]`              | Whether the task should have a human review the final answer of the agent. Defaults to False.                        |
-| **Config** _(optional)_          | `config`          | `Optional[Dict[str, Any]]`    | Task-specific configuration parameters.                                                                              |
-| **Output File** _(optional)_     | `output_file`     | `Optional[str]`               | File path for storing the task output.                                                                               |
-| **Output JSON** _(optional)_     | `output_json`     | `Optional[Type[BaseModel]]`   | A Pydantic model to structure the JSON output.                                                                       |
-| **Output Pydantic** _(optional)_ | `output_pydantic` | `Optional[Type[BaseModel]]`   | A Pydantic model for task output.                                                                                    |
-| **Callback** _(optional)_        | `callback`        | `Optional[Any]`               | Function/object to be executed after task completion.                                                                |
-
-## Creating Tasks
-
-There are two ways to create tasks in CrewAI: using **YAML configuration (recommended)** or defining them **directly in code**.
-
-### YAML Configuration (Recommended)
-
-Using YAML configuration provides a cleaner, more maintainable way to define tasks. We strongly recommend using this approach to define tasks in your CrewAI projects.
-
-After creating your CrewAI project as outlined in the [Installation](/installation) section, navigate to the `src/latest_ai_development/config/tasks.yaml` file and modify the template to match your specific task requirements.
-
-<Note>
-Variables in your YAML files (like `{topic}`) will be replaced with values from your inputs when running the crew:
-```python Code
-crew.kickoff(inputs={'topic': 'AI Agents'})
-```
-</Note>
-
-Here's an example of how to configure tasks using YAML:
-
-```yaml 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.md
-```
-
-To use this YAML configuration in your code, create a crew class that inherits from `CrewBase`:
-
-```python crew.py
-# src/latest_ai_development/crew.py
-
-from crewai import Agent, Crew, Process, Task
-from crewai.project import CrewBase, agent, crew, task
-from crewai_tools import SerperDevTool
-
-@CrewBase
-class LatestAiDevelopmentCrew():
-  """LatestAiDevelopment crew"""
-
-  @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']
-    )
-
-  @crew
-  def crew(self) -> Crew:
-    return Crew(
-      agents=[
-        self.researcher(),
-        self.reporting_analyst()
-      ],
-      tasks=[
-        self.research_task(),
-        self.reporting_task()
-      ],
-      process=Process.sequential
-    )
-```
-
-<Note>
-The names you use in your YAML files (`agents.yaml` and `tasks.yaml`) should match the method names in your Python code.
-</Note>
-
-### Direct Code Definition (Alternative)
-
-Alternatively, you can define tasks directly in your code without using YAML configuration:
-
-```python task.py
-from crewai import Task
-
-research_task = Task(
-    description="""
-        Conduct a thorough research about AI Agents.
-        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 AI Agents
-    """,
-    agent=researcher
-)
-
-reporting_task = 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.md"
-)
-```
-
-<Tip>
-  Directly specify an `agent` for assignment or let the `hierarchical` CrewAI's process decide based on roles, availability, etc.
-</Tip>
-
-## Task Output
-
-Understanding task outputs is crucial for building effective AI workflows. CrewAI provides a structured way to handle task results through the `TaskOutput` class, which supports multiple output formats and can be easily passed between tasks.
-
-The output of a task in CrewAI framework is encapsulated within the `TaskOutput` class. This class provides a structured way to access results of a task, including various formats such as raw output, JSON, and Pydantic models.
-
-By default, the `TaskOutput` will only include the `raw` output. A `TaskOutput` will only include the `pydantic` or `json_dict` output if the original `Task` object was configured with `output_pydantic` or `output_json`, respectively.
-
-### Task Output Attributes
-
-| Attribute         | Parameters      | Type                       | Description                                                                                        |
-| :---------------- | :-------------- | :------------------------- | :------------------------------------------------------------------------------------------------- |
-| **Description**   | `description`   | `str`                      | Description of the task.                                                                           |
-| **Summary**       | `summary`       | `Optional[str]`            | Summary of the task, auto-generated from the first 10 words of the description.                    |
-| **Raw**           | `raw`           | `str`                      | The raw output of the task. This is the default format for the output.                             |
-| **Pydantic**      | `pydantic`      | `Optional[BaseModel]`      | A Pydantic model object representing the structured output of the task.                            |
-| **JSON Dict**     | `json_dict`     | `Optional[Dict[str, Any]]` | A dictionary representing the JSON output of the task.                                             |
-| **Agent**         | `agent`         | `str`                      | The agent that executed the task.                                                                  |
-| **Output Format** | `output_format` | `OutputFormat`             | The format of the task output, with options including RAW, JSON, and Pydantic. The default is RAW. |
-
-### Task Methods and Properties
-
-| Method/Property | Description                                                                                       |
-| :-------------- | :------------------------------------------------------------------------------------------------ |
-| **json**        | Returns the JSON string representation of the task output if the output format is JSON.           |
-| **to_dict**     | Converts the JSON and Pydantic outputs to a dictionary.                                           |
-| **str**         | Returns the string representation of the task output, prioritizing Pydantic, then JSON, then raw. |
-
-### Accessing Task Outputs
-
-Once a task has been executed, its output can be accessed through the `output` attribute of the `Task` object. The `TaskOutput` class provides various ways to interact with and present this output.
-
-#### Example
-
-```python Code
-# Example task
-task = Task(
-    description='Find and summarize the latest AI news',
-    expected_output='A bullet list summary of the top 5 most important AI news',
-    agent=research_agent,
-    tools=[search_tool]
-)
-
-# Execute the crew
-crew = Crew(
-    agents=[research_agent],
-    tasks=[task],
-    verbose=True
-)
-
-result = crew.kickoff()
-
-# Accessing the task output
-task_output = task.output
-
-print(f"Task Description: {task_output.description}")
-print(f"Task Summary: {task_output.summary}")
-print(f"Raw Output: {task_output.raw}")
-if task_output.json_dict:
-    print(f"JSON Output: {json.dumps(task_output.json_dict, indent=2)}")
-if task_output.pydantic:
-    print(f"Pydantic Output: {task_output.pydantic}")
-```
-
-## Task Dependencies and Context
-
-Tasks can depend on the output of other tasks using the `context` attribute. For example:
-
-```python Code
-research_task = Task(
-    description="Research the latest developments in AI",
-    expected_output="A list of recent AI developments",
-    agent=researcher
-)
-
-analysis_task = Task(
-    description="Analyze the research findings and identify key trends",
-    expected_output="Analysis report of AI trends",
-    agent=analyst,
-    context=[research_task]  # This task will wait for research_task to complete
-)
-```
-
-## Task Guardrails
-
-Task guardrails provide a way to validate and transform task outputs before they
-are passed to the next task. This feature helps ensure data quality and provides
-feedback to agents when their output doesn't meet specific criteria.
-
-### Using Task Guardrails
-
-To add a guardrail to a task, provide a validation function through the `guardrail` parameter:
-
-```python Code
-from typing import Tuple, Union, Dict, Any
-
-def validate_blog_content(result: str) -> Tuple[bool, Union[Dict[str, Any], str]]:
-    """Validate blog content meets requirements."""
-    try:
-        # Check word count
-        word_count = len(result.split())
-        if word_count > 200:
-            return (False, {
-                "error": "Blog content exceeds 200 words",
-                "code": "WORD_COUNT_ERROR",
-                "context": {"word_count": word_count}
-            })
-
-        # Additional validation logic here
-        return (True, result.strip())
-    except Exception as e:
-        return (False, {
-            "error": "Unexpected error during validation",
-            "code": "SYSTEM_ERROR"
-        })
-
-blog_task = Task(
-    description="Write a blog post about AI",
-    expected_output="A blog post under 200 words",
-    agent=blog_agent,
-    guardrail=validate_blog_content  # Add the guardrail function
-)
-```
-
-### Guardrail Function Requirements
-
-1. **Function Signature**:
-   - Must accept exactly one parameter (the task output)
-   - Should return a tuple of `(bool, Any)`
-   - Type hints are recommended but optional
-
-2. **Return Values**:
-   - Success: Return `(True, validated_result)`
-   - Failure: Return `(False, error_details)`
-
-### Error Handling Best Practices
-
-1. **Structured Error Responses**:
-```python Code
-def validate_with_context(result: str) -> Tuple[bool, Union[Dict[str, Any], str]]:
-    try:
-        # Main validation logic
-        validated_data = perform_validation(result)
-        return (True, validated_data)
-    except ValidationError as e:
-        return (False, {
-            "error": str(e),
-            "code": "VALIDATION_ERROR",
-            "context": {"input": result}
-        })
-    except Exception as e:
-        return (False, {
-            "error": "Unexpected error",
-            "code": "SYSTEM_ERROR"
-        })
-```
-
-2. **Error Categories**:
-   - Use specific error codes
-   - Include relevant context
-   - Provide actionable feedback
-
-3. **Validation Chain**:
-```python Code
-from typing import Any, Dict, List, Tuple, Union
-
-def complex_validation(result: str) -> Tuple[bool, Union[str, Dict[str, Any]]]:
-    """Chain multiple validation steps."""
-    # Step 1: Basic validation
-    if not result:
-        return (False, {"error": "Empty result", "code": "EMPTY_INPUT"})
-
-    # Step 2: Content validation
-    try:
-        validated = validate_content(result)
-        if not validated:
-            return (False, {"error": "Invalid content", "code": "CONTENT_ERROR"})
-
-        # Step 3: Format validation
-        formatted = format_output(validated)
-        return (True, formatted)
-    except Exception as e:
-        return (False, {
-            "error": str(e),
-            "code": "VALIDATION_ERROR",
-            "context": {"step": "content_validation"}
-        })
-```
-
-### Handling Guardrail Results
-
-When a guardrail returns `(False, error)`:
-1. The error is sent back to the agent
-2. The agent attempts to fix the issue
-3. The process repeats until:
-   - The guardrail returns `(True, result)`
-   - Maximum retries are reached
-
-Example with retry handling:
-```python Code
-from typing import Optional, Tuple, Union
-
-def validate_json_output(result: str) -> Tuple[bool, Union[Dict[str, Any], str]]:
-    """Validate and parse JSON output."""
-    try:
-        # Try to parse as JSON
-        data = json.loads(result)
-        return (True, data)
-    except json.JSONDecodeError as e:
-        return (False, {
-            "error": "Invalid JSON format",
-            "code": "JSON_ERROR",
-            "context": {"line": e.lineno, "column": e.colno}
-        })
-
-task = Task(
-    description="Generate a JSON report",
-    expected_output="A valid JSON object",
-    agent=analyst,
-    guardrail=validate_json_output,
-    max_retries=3  # Limit retry attempts
-)
-```
-
-## Getting Structured Consistent Outputs from Tasks
-
-<Note>
-It's also important to note that the output of the final task of a crew becomes the final output of the actual crew itself.
-</Note>
-
-### Using `output_pydantic`
-The `output_pydantic` property allows you to define a Pydantic model that the task output should conform to. This ensures that the output is not only structured but also validated according to the Pydantic model.
-
-Here's an example demonstrating how to use output_pydantic:
-
-```python Code
-import json
-
-from crewai import Agent, Crew, Process, Task
-from pydantic import BaseModel
-
-
-class Blog(BaseModel):
-    title: str
-    content: str
-
-
-blog_agent = Agent(
-    role="Blog Content Generator Agent",
-    goal="Generate a blog title and content",
-    backstory="""You are an expert content creator, skilled in crafting engaging and informative blog posts.""",
-    verbose=False,
-    allow_delegation=False,
-    llm="gpt-4o",
-)
-
-task1 = Task(
-    description="""Create a blog title and content on a given topic. Make sure the content is under 200 words.""",
-    expected_output="A compelling blog title and well-written content.",
-    agent=blog_agent,
-    output_pydantic=Blog,
-)
-
-# Instantiate your crew with a sequential process
-crew = Crew(
-    agents=[blog_agent],
-    tasks=[task1],
-    verbose=True,
-    process=Process.sequential,
-)
-
-result = crew.kickoff()
-
-# Option 1: Accessing Properties Using Dictionary-Style Indexing
-print("Accessing Properties - Option 1")
-title = result["title"]
-content = result["content"]
-print("Title:", title)
-print("Content:", content)
-
-# Option 2: Accessing Properties Directly from the Pydantic Model
-print("Accessing Properties - Option 2")
-title = result.pydantic.title
-content = result.pydantic.content
-print("Title:", title)
-print("Content:", content)
-
-# Option 3: Accessing Properties Using the to_dict() Method
-print("Accessing Properties - Option 3")
-output_dict = result.to_dict()
-title = output_dict["title"]
-content = output_dict["content"]
-print("Title:", title)
-print("Content:", content)
-
-# Option 4: Printing the Entire Blog Object
-print("Accessing Properties - Option 5")
-print("Blog:", result)
-
-```
-In this example:
-* A Pydantic model Blog is defined with title and content fields.
-* The task task1 uses the output_pydantic property to specify that its output should conform to the Blog model.
-* After executing the crew, you can access the structured output in multiple ways as shown.
-
-#### Explanation of Accessing the Output
-1. Dictionary-Style Indexing: You can directly access the fields using result["field_name"]. This works because the CrewOutput class implements the __getitem__ method.
-2. Directly from Pydantic Model: Access the attributes directly from the result.pydantic object.
-3. Using to_dict() Method: Convert the output to a dictionary and access the fields.
-4. Printing the Entire Object: Simply print the result object to see the structured output.
-
-### Using `output_json`
-The `output_json` property allows you to define the expected output in JSON format. This ensures that the task's output is a valid JSON structure that can be easily parsed and used in your application.
-
-Here's an example demonstrating how to use `output_json`:
-
-```python Code
-import json
-
-from crewai import Agent, Crew, Process, Task
-from pydantic import BaseModel
-
-
-# Define the Pydantic model for the blog
-class Blog(BaseModel):
-    title: str
-    content: str
-
-
-# Define the agent
-blog_agent = Agent(
-    role="Blog Content Generator Agent",
-    goal="Generate a blog title and content",
-    backstory="""You are an expert content creator, skilled in crafting engaging and informative blog posts.""",
-    verbose=False,
-    allow_delegation=False,
-    llm="gpt-4o",
-)
-
-# Define the task with output_json set to the Blog model
-task1 = Task(
-    description="""Create a blog title and content on a given topic. Make sure the content is under 200 words.""",
-    expected_output="A JSON object with 'title' and 'content' fields.",
-    agent=blog_agent,
-    output_json=Blog,
-)
-
-# Instantiate the crew with a sequential process
-crew = Crew(
-    agents=[blog_agent],
-    tasks=[task1],
-    verbose=True,
-    process=Process.sequential,
-)
-
-# Kickoff the crew to execute the task
-result = crew.kickoff()
-
-# Option 1: Accessing Properties Using Dictionary-Style Indexing
-print("Accessing Properties - Option 1")
-title = result["title"]
-content = result["content"]
-print("Title:", title)
-print("Content:", content)
-
-# Option 2: Printing the Entire Blog Object
-print("Accessing Properties - Option 2")
-print("Blog:", result)
-```
-
-In this example:
-* A Pydantic model Blog is defined with title and content fields, which is used to specify the structure of the JSON output.
-* The task task1 uses the output_json property to indicate that it expects a JSON output conforming to the Blog model.
-* After executing the crew, you can access the structured JSON output in two ways as shown.
-
-#### Explanation of Accessing the Output
-
-1. Accessing Properties Using Dictionary-Style Indexing: You can access the fields directly using result["field_name"]. This is possible because the CrewOutput class implements the __getitem__ method, allowing you to treat the output like a dictionary. In this option, we're retrieving the title and content from the result.
-2. Printing the Entire Blog Object: By printing result, you get the string representation of the CrewOutput object. Since the __str__ method is implemented to return the JSON output, this will display the entire output as a formatted string representing the Blog object.
-
----
-
-By using output_pydantic or output_json, you ensure that your tasks produce outputs in a consistent and structured format, making it easier to process and utilize the data within your application or across multiple tasks.
-
-## Integrating Tools with Tasks
-
-Leverage tools from the [CrewAI Toolkit](https://github.com/joaomdmoura/crewai-tools) and [LangChain Tools](https://python.langchain.com/docs/integrations/tools) for enhanced task performance and agent interaction.
-
-## Creating a Task with Tools
-
-```python Code
-import os
-os.environ["OPENAI_API_KEY"] = "Your Key"
-os.environ["SERPER_API_KEY"] = "Your Key" # serper.dev API key
-
-from crewai import Agent, Task, Crew
-from crewai_tools import SerperDevTool
-
-research_agent = Agent(
-  role='Researcher',
-  goal='Find and summarize the latest AI news',
-  backstory="""You're a researcher at a large company.
-  You're responsible for analyzing data and providing insights
-  to the business.""",
-  verbose=True
-)
-
-# to perform a semantic search for a specified query from a text's content across the internet
-search_tool = SerperDevTool()
-
-task = Task(
-  description='Find and summarize the latest AI news',
-  expected_output='A bullet list summary of the top 5 most important AI news',
-  agent=research_agent,
-  tools=[search_tool]
-)
-
-crew = Crew(
-    agents=[research_agent],
-    tasks=[task],
-    verbose=True
-)
-
-result = crew.kickoff()
-print(result)
-```
-
-This demonstrates how tasks with specific tools can override an agent's default set for tailored task execution.
-
-## Referring to Other Tasks
-
-In CrewAI, the output of one task is automatically relayed into the next one, but you can specifically define what tasks' output, including multiple, should be used as context for another task.
-
-This is useful when you have a task that depends on the output of another task that is not performed immediately after it. This is done through the `context` attribute of the task:
-
-```python Code
-# ...
-
-research_ai_task = Task(
-    description="Research the latest developments in AI",
-    expected_output="A list of recent AI developments",
-    async_execution=True,
-    agent=research_agent,
-    tools=[search_tool]
-)
-
-research_ops_task = Task(
-    description="Research the latest developments in AI Ops",
-    expected_output="A list of recent AI Ops developments",
-    async_execution=True,
-    agent=research_agent,
-    tools=[search_tool]
-)
-
-write_blog_task = Task(
-    description="Write a full blog post about the importance of AI and its latest news",
-    expected_output="Full blog post that is 4 paragraphs long",
-    agent=writer_agent,
-    context=[research_ai_task, research_ops_task]
-)
-
-#...
-```
-
-## Asynchronous Execution
-
-You can define a task to be executed asynchronously. This means that the crew will not wait for it to be completed to continue with the next task. This is useful for tasks that take a long time to be completed, or that are not crucial for the next tasks to be performed.
-
-You can then use the `context` attribute to define in a future task that it should wait for the output of the asynchronous task to be completed.
-
-```python Code
-#...
-
-list_ideas = Task(
-    description="List of 5 interesting ideas to explore for an article about AI.",
-    expected_output="Bullet point list of 5 ideas for an article.",
-    agent=researcher,
-    async_execution=True # Will be executed asynchronously
-)
-
-list_important_history = Task(
-    description="Research the history of AI and give me the 5 most important events.",
-    expected_output="Bullet point list of 5 important events.",
-    agent=researcher,
-    async_execution=True # Will be executed asynchronously
-)
-
-write_article = Task(
-    description="Write an article about AI, its history, and interesting ideas.",
-    expected_output="A 4 paragraph article about AI.",
-    agent=writer,
-    context=[list_ideas, list_important_history] # Will wait for the output of the two tasks to be completed
-)
-
-#...
-```
-
-## Callback Mechanism
-
-The callback function is executed after the task is completed, allowing for actions or notifications to be triggered based on the task's outcome.
-
-```python Code
-# ...
-
-def callback_function(output: TaskOutput):
-    # Do something after the task is completed
-    # Example: Send an email to the manager
-    print(f"""
-        Task completed!
-        Task: {output.description}
-        Output: {output.raw}
-    """)
-
-research_task = Task(
-    description='Find and summarize the latest AI news',
-    expected_output='A bullet list summary of the top 5 most important AI news',
-    agent=research_agent,
-    tools=[search_tool],
-    callback=callback_function
-)
-
-#...
-```
-
-## Accessing a Specific Task Output
-
-Once a crew finishes running, you can access the output of a specific task by using the `output` attribute of the task object:
-
-```python Code
-# ...
-task1 = Task(
-    description='Find and summarize the latest AI news',
-    expected_output='A bullet list summary of the top 5 most important AI news',
-    agent=research_agent,
-    tools=[search_tool]
-)
-
-#...
-
-crew = Crew(
-    agents=[research_agent],
-    tasks=[task1, task2, task3],
-    verbose=True
-)
-
-result = crew.kickoff()
-
-# Returns a TaskOutput object with the description and results of the task
-print(f"""
-    Task completed!
-    Task: {task1.output.description}
-    Output: {task1.output.raw}
-""")
-```
-
-## Tool Override Mechanism
-
-Specifying tools in a task allows for dynamic adaptation of agent capabilities, emphasizing CrewAI's flexibility.
-
-## Error Handling and Validation Mechanisms
-
-While creating and executing tasks, certain validation mechanisms are in place to ensure the robustness and reliability of task attributes. These include but are not limited to:
-
-- Ensuring only one output type is set per task to maintain clear output expectations.
-- Preventing the manual assignment of the `id` attribute to uphold the integrity of the unique identifier system.
-
-These validations help in maintaining the consistency and reliability of task executions within the crewAI framework.
-
-## Task Guardrails
-
-Task guardrails provide a powerful way to validate, transform, or filter task outputs before they are passed to the next task. Guardrails are optional functions that execute before the next task starts, allowing you to ensure that task outputs meet specific requirements or formats.
-
-### Basic Usage
-
-```python Code
-from typing import Tuple, Union
-from crewai import Task
-
-def validate_json_output(result: str) -> Tuple[bool, Union[dict, str]]:
-    """Validate that the output is valid JSON."""
-    try:
-        json_data = json.loads(result)
-        return (True, json_data)
-    except json.JSONDecodeError:
-        return (False, "Output must be valid JSON")
-
-task = Task(
-    description="Generate JSON data",
-    expected_output="Valid JSON object",
-    guardrail=validate_json_output
-)
-```
-
-### How Guardrails Work
-
-1. **Optional Attribute**: Guardrails are an optional attribute at the task level, allowing you to add validation only where needed.
-2. **Execution Timing**: The guardrail function is executed before the next task starts, ensuring valid data flow between tasks.
-3. **Return Format**: Guardrails must return a tuple of `(success, data)`:
-   - If `success` is `True`, `data` is the validated/transformed result
-   - If `success` is `False`, `data` is the error message
-4. **Result Routing**:
-   - On success (`True`), the result is automatically passed to the next task
-   - On failure (`False`), the error is sent back to the agent to generate a new answer
-
-### Common Use Cases
-
-#### Data Format Validation
-```python Code
-def validate_email_format(result: str) -> Tuple[bool, Union[str, str]]:
-    """Ensure the output contains a valid email address."""
-    import re
-    email_pattern = r'^[\w\.-]+@[\w\.-]+\.\w+$'
-    if re.match(email_pattern, result.strip()):
-        return (True, result.strip())
-    return (False, "Output must be a valid email address")
-```
-
-#### Content Filtering
-```python Code
-def filter_sensitive_info(result: str) -> Tuple[bool, Union[str, str]]:
-    """Remove or validate sensitive information."""
-    sensitive_patterns = ['SSN:', 'password:', 'secret:']
-    for pattern in sensitive_patterns:
-        if pattern.lower() in result.lower():
-            return (False, f"Output contains sensitive information ({pattern})")
-    return (True, result)
-```
-
-#### Data Transformation
-```python Code
-def normalize_phone_number(result: str) -> Tuple[bool, Union[str, str]]:
-    """Ensure phone numbers are in a consistent format."""
-    import re
-    digits = re.sub(r'\D', '', result)
-    if len(digits) == 10:
-        formatted = f"({digits[:3]}) {digits[3:6]}-{digits[6:]}"
-        return (True, formatted)
-    return (False, "Output must be a 10-digit phone number")
-```
-
-### Advanced Features
-
-#### Chaining Multiple Validations
-```python Code
-def chain_validations(*validators):
-    """Chain multiple validators together."""
-    def combined_validator(result):
-        for validator in validators:
-            success, data = validator(result)
-            if not success:
-                return (False, data)
-            result = data
-        return (True, result)
-    return combined_validator
-
-# Usage
-task = Task(
-    description="Get user contact info",
-    expected_output="Email and phone",
-    guardrail=chain_validations(
-        validate_email_format,
-        filter_sensitive_info
-    )
-)
-```
-
-#### Custom Retry Logic
-```python Code
-task = Task(
-    description="Generate data",
-    expected_output="Valid data",
-    guardrail=validate_data,
-    max_retries=5  # Override default retry limit
-)
-```
-
-## Creating Directories when Saving Files
-
-You can now specify if a task should create directories when saving its output to a file. This is particularly useful for organizing outputs and ensuring that file paths are correctly structured.
-
-```python Code
-# ...
-
-save_output_task = Task(
-    description='Save the summarized AI news to a file',
-    expected_output='File saved successfully',
-    agent=research_agent,
-    tools=[file_save_tool],
-    output_file='outputs/ai_news_summary.txt',
-    create_directory=True
-)
-
-#...
-```
-
-Check out the video below to see how to use structured outputs in CrewAI:
-
-<iframe
-  width="560"
-  height="315"
-  src="https://www.youtube.com/embed/dNpKQk5uxHw"
-  title="YouTube video player"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-  referrerpolicy="strict-origin-when-cross-origin"
-  allowfullscreen
-></iframe>
-
-## Conclusion
-
-Tasks are the driving force behind the actions of agents in CrewAI.
-By properly defining tasks and their outcomes, you set the stage for your AI agents to work effectively, either independently or as a collaborative unit.
-Equipping tasks with appropriate tools, understanding the execution process, and following robust validation practices are crucial for maximizing CrewAI's potential,
-ensuring agents are effectively prepared for their assignments and that tasks are executed as intended.

docs/concepts/testing.mdx

@@ -1,48 +0,0 @@
----
-title: Testing
-description: Learn how to test your CrewAI Crew and evaluate their performance.
-icon: vial
----
-
-## Introduction
-
-Testing is a crucial part of the development process, and it is essential to ensure that your crew is performing as expected. With crewAI, you can easily test your crew and evaluate its performance using the built-in testing capabilities.
-
-### Using the Testing Feature
-
-We added the CLI command `crewai test` to make it easy to test your crew. This command will run your crew for a specified number of iterations and provide detailed performance metrics. The parameters are `n_iterations` and `model`, which are optional and default to 2 and `gpt-4o-mini` respectively. For now, the only provider available is OpenAI.
-
-```bash
-crewai test
-```
-
-If you want to run more iterations or use a different model, you can specify the parameters like this:
-
-```bash
-crewai test --n_iterations 5 --model gpt-4o
-```
-
-or using the short forms:
-
-```bash
-crewai test -n 5 -m gpt-4o
-```
-
-When you run the `crewai test` command, the crew will be executed for the specified number of iterations, and the performance metrics will be displayed at the end of the run.
-
-A table of scores at the end will show the performance of the crew in terms of the following metrics:
-
-<center>**Tasks Scores (1-10 Higher is better)**</center>
-
-| Tasks/Crew/Agents  | Run 1 | Run 2 | Avg. Total | Agents                         | Additional Info                  |
-|:------------------|:-----:|:-----:|:----------:|:------------------------------:|:---------------------------------|
-| Task 1        |  9.0  |  9.5  |    **9.2**     | Professional Insights          |                                  |
-|                    |       |       |            | Researcher                     |                                  |
-| Task 2        |  9.0  | 10.0  |    **9.5**     | Company Profile Investigator   |                                  |
-| Task 3        |  9.0  |  9.0  |    **9.0**     | Automation Insights            |                                  |
-|                    |       |       |            | Specialist                     |                                  |
-| Task 4        |  9.0  |  9.0  |    **9.0**     | Final Report Compiler          | Automation Insights Specialist   |
-| Crew         | 9.00  | 9.38  |    **9.2**     |                                |                                  |
-| Execution Time (s) |  126  |  145  |    **135**     |                                |                                  |
-
-The example above shows the test results for two runs of the crew with two tasks, with the average total score for each task and the crew as a whole.

docs/concepts/tools.mdx

@@ -1,272 +0,0 @@
----
-title: Tools
-description: Understanding and leveraging tools within the CrewAI framework for agent collaboration and task execution.
-icon: screwdriver-wrench
----
-
-## Introduction
-
-CrewAI tools empower agents with capabilities ranging from web searching and data analysis to collaboration and delegating tasks among coworkers.
-This documentation outlines how to create, integrate, and leverage these tools within the CrewAI framework, including a new focus on collaboration tools.
-
-## What is a Tool?
-
-A tool in CrewAI is a skill or function that agents can utilize to perform various actions.
-This includes tools from the [CrewAI Toolkit](https://github.com/joaomdmoura/crewai-tools) and [LangChain Tools](https://python.langchain.com/docs/integrations/tools),
-enabling everything from simple searches to complex interactions and effective teamwork among agents.
-
-<Note type="info" title="Enterprise Enhancement: Tools Repository">
-CrewAI Enterprise provides a comprehensive Tools Repository with pre-built integrations for common business systems and APIs. Deploy agents with enterprise tools in minutes instead of days.
-
-![Tools Repository Screenshot](../images/enterprise/tools-repository.png)
-
-The Enterprise Tools Repository includes:
-- Pre-built connectors for popular enterprise systems
-- Custom tool creation interface
-- Version control and sharing capabilities
-- Security and compliance features
-</Note>
-
-## Key Characteristics of Tools
-
-- **Utility**: Crafted for tasks such as web searching, data analysis, content generation, and agent collaboration.
-- **Integration**: Boosts agent capabilities by seamlessly integrating tools into their workflow.
-- **Customizability**: Provides the flexibility to develop custom tools or utilize existing ones, catering to the specific needs of agents.
-- **Error Handling**: Incorporates robust error handling mechanisms to ensure smooth operation.
-- **Caching Mechanism**: Features intelligent caching to optimize performance and reduce redundant operations.
-
-## Using CrewAI Tools
-
-To enhance your agents' capabilities with crewAI tools, begin by installing our extra tools package:
-
-```bash
-pip install 'crewai[tools]'
-```
-
-Here's an example demonstrating their use:
-
-```python Code
-import os
-from crewai import Agent, Task, Crew
-# Importing crewAI tools
-from crewai_tools import (
-    DirectoryReadTool,
-    FileReadTool,
-    SerperDevTool,
-    WebsiteSearchTool
-)
-
-# Set up API keys
-os.environ["SERPER_API_KEY"] = "Your Key" # serper.dev API key
-os.environ["OPENAI_API_KEY"] = "Your Key"
-
-# Instantiate tools
-docs_tool = DirectoryReadTool(directory='./blog-posts')
-file_tool = FileReadTool()
-search_tool = SerperDevTool()
-web_rag_tool = WebsiteSearchTool()
-
-# Create agents
-researcher = Agent(
-    role='Market Research Analyst',
-    goal='Provide up-to-date market analysis of the AI industry',
-    backstory='An expert analyst with a keen eye for market trends.',
-    tools=[search_tool, web_rag_tool],
-    verbose=True
-)
-
-writer = Agent(
-    role='Content Writer',
-    goal='Craft engaging blog posts about the AI industry',
-    backstory='A skilled writer with a passion for technology.',
-    tools=[docs_tool, file_tool],
-    verbose=True
-)
-
-# Define tasks
-research = Task(
-    description='Research the latest trends in the AI industry and provide a summary.',
-    expected_output='A summary of the top 3 trending developments in the AI industry with a unique perspective on their significance.',
-    agent=researcher
-)
-
-write = Task(
-    description='Write an engaging blog post about the AI industry, based on the research analyst's summary. Draw inspiration from the latest blog posts in the directory.',
-    expected_output='A 4-paragraph blog post formatted in markdown with engaging, informative, and accessible content, avoiding complex jargon.',
-    agent=writer,
-    output_file='blog-posts/new_post.md'  # The final blog post will be saved here
-)
-
-# Assemble a crew with planning enabled
-crew = Crew(
-    agents=[researcher, writer],
-    tasks=[research, write],
-    verbose=True,
-    planning=True,  # Enable planning feature
-)
-
-# Execute tasks
-crew.kickoff()
-```
-
-## Available CrewAI Tools
-
-- **Error Handling**: All tools are built with error handling capabilities, allowing agents to gracefully manage exceptions and continue their tasks.
-- **Caching Mechanism**: All tools support caching, enabling agents to efficiently reuse previously obtained results, reducing the load on external resources and speeding up the execution time. You can also define finer control over the caching mechanism using the `cache_function` attribute on the tool.
-
-Here is a list of the available tools and their descriptions:
-
-| Tool                             | Description                                                                                    |
-| :------------------------------- | :--------------------------------------------------------------------------------------------- |
-| **ApifyActorsTool**              | A tool that integrates Apify Actors with your workflows for web scraping and automation tasks. |
-| **BrowserbaseLoadTool**          | A tool for interacting with and extracting data from web browsers.                             |
-| **CodeDocsSearchTool**           | A RAG tool optimized for searching through code documentation and related technical documents. |
-| **CodeInterpreterTool**          | A tool for interpreting python code.                                                           |
-| **ComposioTool**                 | Enables use of Composio tools.                                                                 |
-| **CSVSearchTool**                | A RAG tool designed for searching within CSV files, tailored to handle structured data.        |
-| **DALL-E Tool**                  | A tool for generating images using the DALL-E API.                                             |
-| **DirectorySearchTool**          | A RAG tool for searching within directories, useful for navigating through file systems.       |
-| **DOCXSearchTool**               | A RAG tool aimed at searching within DOCX documents, ideal for processing Word files.          |
-| **DirectoryReadTool**            | Facilitates reading and processing of directory structures and their contents.                 |
-| **EXASearchTool**                | A tool designed for performing exhaustive searches across various data sources.                |
-| **FileReadTool**                 | Enables reading and extracting data from files, supporting various file formats.               |
-| **FirecrawlSearchTool**          | A tool to search webpages using Firecrawl and return the results.                              |
-| **FirecrawlCrawlWebsiteTool**    | A tool for crawling webpages using Firecrawl.                                                  |
-| **FirecrawlScrapeWebsiteTool**   | A tool for scraping webpages URL using Firecrawl and returning its contents.                   |
-| **GithubSearchTool**             | A RAG tool for searching within GitHub repositories, useful for code and documentation search. |
-| **SerperDevTool**                | A specialized tool for development purposes, with specific functionalities under development.  |
-| **TXTSearchTool**                | A RAG tool focused on searching within text (.txt) files, suitable for unstructured data.      |
-| **JSONSearchTool**               | A RAG tool designed for searching within JSON files, catering to structured data handling.     |
-| **LlamaIndexTool**               | Enables the use of LlamaIndex tools.                                                           |
-| **MDXSearchTool**                | A RAG tool tailored for searching within Markdown (MDX) files, useful for documentation.       |
-| **PDFSearchTool**                | A RAG tool aimed at searching within PDF documents, ideal for processing scanned documents.    |
-| **PGSearchTool**                 | A RAG tool optimized for searching within PostgreSQL databases, suitable for database queries. |
-| **Vision Tool**                  | A tool for generating images using the DALL-E API.                                             |
-| **RagTool**                      | A general-purpose RAG tool capable of handling various data sources and types.                 |
-| **ScrapeElementFromWebsiteTool** | Enables scraping specific elements from websites, useful for targeted data extraction.         |
-| **ScrapeWebsiteTool**            | Facilitates scraping entire websites, ideal for comprehensive data collection.                 |
-| **WebsiteSearchTool**            | A RAG tool for searching website content, optimized for web data extraction.                   |
-| **XMLSearchTool**                | A RAG tool designed for searching within XML files, suitable for structured data formats.      |
-| **YoutubeChannelSearchTool**     | A RAG tool for searching within YouTube channels, useful for video content analysis.           |
-| **YoutubeVideoSearchTool**       | A RAG tool aimed at searching within YouTube videos, ideal for video data extraction.          |
-
-## Creating your own Tools
-
-<Tip>
-  Developers can craft `custom tools` tailored for their agent's needs or
-  utilize pre-built options.
-</Tip>
-
-There are two main ways for one to create a CrewAI tool:
-
-### Subclassing `BaseTool`
-
-```python Code
-from crewai.tools import BaseTool
-from pydantic import BaseModel, Field
-
-class MyToolInput(BaseModel):
-    """Input schema for MyCustomTool."""
-    argument: str = Field(..., description="Description of the argument.")
-
-class MyCustomTool(BaseTool):
-    name: str = "Name of my tool"
-    description: str = "What this tool does. It's vital for effective utilization."
-    args_schema: Type[BaseModel] = MyToolInput
-
-    def _run(self, argument: str) -> str:
-        # Your tool's logic here
-        return "Tool's result"
-```
-
-### Utilizing the `tool` Decorator
-
-```python Code
-from crewai.tools import tool
-@tool("Name of my tool")
-def my_tool(question: str) -> str:
-    """Clear description for what this tool is useful for, your agent will need this information to use it."""
-    # Function logic here
-    return "Result from your custom tool"
-```
-
-### Structured Tools
-
-The `StructuredTool` class wraps functions as tools, providing flexibility and validation while reducing boilerplate. It supports custom schemas and dynamic logic for seamless integration of complex functionalities.
-
-#### Example:
-Using `StructuredTool.from_function`, you can wrap a function that interacts with an external API or system, providing a structured interface. This enables robust validation and consistent execution, making it easier to integrate complex functionalities into your applications as demonstrated in the following example:
-
-```python
-from crewai.tools.structured_tool import CrewStructuredTool
-from pydantic import BaseModel
-
-# Define the schema for the tool's input using Pydantic
-class APICallInput(BaseModel):
-    endpoint: str
-    parameters: dict
-
-# Wrapper function to execute the API call
-def tool_wrapper(*args, **kwargs):
-    # Here, you would typically call the API using the parameters
-    # For demonstration, we'll return a placeholder string
-    return f"Call the API at {kwargs['endpoint']} with parameters {kwargs['parameters']}"
-
-# Create and return the structured tool
-def create_structured_tool():
-    return CrewStructuredTool.from_function(
-        name='Wrapper API',
-        description="A tool to wrap API calls with structured input.",
-        args_schema=APICallInput,
-        func=tool_wrapper,
-    )
-
-# Example usage
-structured_tool = create_structured_tool()
-
-# Execute the tool with structured input
-result = structured_tool._run(**{
-    "endpoint": "https://example.com/api",
-    "parameters": {"key1": "value1", "key2": "value2"}
-})
-print(result)  # Output: Call the API at https://example.com/api with parameters {'key1': 'value1', 'key2': 'value2'}
-```
-
-### Custom Caching Mechanism
-
-<Tip>
-  Tools can optionally implement a `cache_function` to fine-tune caching
-  behavior. This function determines when to cache results based on specific
-  conditions, offering granular control over caching logic.
-</Tip>
-
-```python Code
-from crewai.tools import tool
-
-@tool
-def multiplication_tool(first_number: int, second_number: int) -> str:
-    """Useful for when you need to multiply two numbers together."""
-    return first_number * second_number
-
-def cache_func(args, result):
-    # In this case, we only cache the result if it's a multiple of 2
-    cache = result % 2 == 0
-    return cache
-
-multiplication_tool.cache_function = cache_func
-
-writer1 = Agent(
-        role="Writer",
-        goal="You write lessons of math for kids.",
-        backstory="You're an expert in writing and you love to teach kids but you know nothing of math.",
-        tools=[multiplication_tool],
-        allow_delegation=False,
-    )
-    #...
-```
-
-## Conclusion
-
-Tools are pivotal in extending the capabilities of CrewAI agents, enabling them to undertake a broad spectrum of tasks and collaborate effectively.
-When building solutions with CrewAI, leverage both custom and existing tools to empower your agents and enhance the AI ecosystem. Consider utilizing error handling,
-caching mechanisms, and the flexibility of tool arguments to optimize your agents' performance and capabilities.