Merge branch 'main' into docupdates-nicola1

2026-01-23 07:08:14 +00:00 · 2026-01-14 05:51:50 -05:00
parent 6f6bcb21d4 9edbf89b68
commit d79c31ea6e
37 changed files with 3352 additions and 54 deletions
--- a/docs/en/changelog.mdx
+++ b/docs/en/changelog.mdx
@@ -4,6 +4,516 @@ description: "Product updates, improvements, and bug fixes for CrewAI"
 icon: "clock"
 mode: "wide"
 ---
+<Update label="Jan 08, 2026">
+  ## v1.8.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.8.0)
+
+  ## What's Changed
+
+  ### Features
+  - Add native async chain for a2a
+  - Add a2a update mechanisms (poll/stream/push) with handlers and config
+  - Introduce global flow configuration for human-in-the-loop feedback
+  - Add streaming tool call events and fix provider ID tracking
+  - Introduce production-ready Flows and Crews architecture
+  - Add HITL for Flows
+  - Improve EventListener and TraceCollectionListener for enhanced event handling
+
+  ### Bug Fixes
+  - Handle missing a2a dependency as optional
+  - Correct error fetching for WorkOS login polling
+  - Fix wrong trigger name in sample documentation
+
+  ### Documentation
+  - Update webhook-streaming documentation
+  - Adjust AOP to AMP documentation language
+
+  ### Contributors
+  @Vidit-Ostwal, @greysonlalonde, @heitorado, @joaomdmoura, @lorenzejay, @lucasgomide, @mplachta
+
+</Update>
+
+<Update label="Dec 19, 2025">
+  ## v1.7.2
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.7.2)
+
+  ## What's Changed
+
+  ### Bug Fixes
+  - Resolve connection issues
+
+  ### Documentation
+  - Update api-reference/status docs page
+
+  ### Contributors
+  @greysonlalonde, @heitorado, @lorenzejay, @lucasgomide
+
+</Update>
+
+<Update label="Dec 16, 2025">
+  ## v1.7.1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.7.1)
+
+  ## What's Changed
+
+  ### Improvements
+  - Add `--no-commit` flag to bump command
+  - Use JSON schema for tool argument serialization
+
+  ### Bug Fixes
+  - Fix error message display from response when tool repository login fails
+  - Fix graceful termination of future when executing a task asynchronously
+  - Fix task ordering by adding index
+  - Fix platform compatibility checks for Windows signals
+  - Fix RPM controller timer to prevent process hang
+  - Fix token usage recording and validate response model on stream
+
+  ### Documentation
+  - Add translated documentation for async
+  - Add documentation for AOP Deploy API
+  - Add documentation for the agent handler connector
+  - Add documentation on native async
+
+  ### Contributors
+  @Llamrei, @dragosmc, @gilfeig, @greysonlalonde, @heitorado, @lorenzejay, @mattatcha, @vinibrsl
+
+</Update>
+
+<Update label="Dec 09, 2025">
+  ## v1.7.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.7.0)
+
+  ## What's Changed
+
+  ### Features
+  - Add async flow kickoff
+  - Add async crew support
+  - Add async task support
+  - Add async knowledge support
+  - Add async memory support
+  - Add async support for tools and agent executor; improve typing and docs
+  - Implement a2a extensions API and async agent card caching; fix task propagation & streaming
+  - Add native async tool support
+  - Add async llm support
+  - Create sys event types and handler
+
+  ### Bug Fixes
+  - Fix issue to ensure nonetypes are not passed to otel
+  - Fix deadlock in token store file operations
+  - Fix to ensure otel span is closed
+  - Use HuggingFaceEmbeddingFunction for embeddings, update keys and add tests
+  - Fix to ensure supports_tools is true for all supported anthropic models
+  - Ensure hooks work with lite agents flows
+
+  ### Contributors
+  @greysonlalonde, @lorenzejay
+
+</Update>
+
+<Update label="Nov 29, 2025">
+  ## v1.6.1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.6.1)
+
+  ## What's Changed
+
+  ### Bug Fixes
+  - Fix ChatCompletionsClient call to ensure proper functionality
+  - Ensure async methods are executable for annotations
+  - Fix parameters in RagTool.add, add typing, and tests
+  - Remove invalid parameter from SSE client
+  - Erase 'oauth2_extra' setting on 'crewai config reset' command
+
+  ### Refactoring
+  - Enhance model validation and provider inference in LLM class
+
+  ### Contributors
+  @Vidit-Ostwal, @greysonlalonde, @heitorado, @lorenzejay
+
+</Update>
+
+<Update label="Nov 25, 2025">
+  ## v1.6.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.6.0)
+
+  ## What's Changed
+
+  ### Features
+  - Add streaming result support to flows and crews
+  - Add gemini-3-pro-preview
+  - Support CLI login with Entra ID
+  - Add Merge Agent Handler tool
+  - Enhance flow event state management
+
+  ### Bug Fixes
+  - Ensure custom rag store persist path is set if passed
+  - Ensure fuzzy returns are more strict and show type warning
+  - Re-add openai response_format parameter and add test
+  - Fix rag tool embeddings configuration
+  - Ensure flow execution start panel is not shown on plot
+
+  ### Documentation
+  - Update references from AMP to AOP in documentation
+  - Update AMP to AOP
+
+  ### Contributors
+  @Vidit-Ostwal, @gilfeig, @greysonlalonde, @heitorado, @joaomdmoura, @lorenzejay, @markmcd
+
+</Update>
+
+<Update label="Nov 22, 2025">
+  ## v0.203.2
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/0.203.2)
+
+  ## What's Changed
+
+  - Hotfix version bump from 0.203.1 to 0.203.2
+
+</Update>
+
+<Update label="Nov 16, 2025">
+  ## v1.5.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.5.0)
+
+  ## What's Changed
+
+  ### Features
+  - Add a2a trust remote completion status flag
+  - Fetch and store more data about Okta authorization server
+  - Implement before and after LLM call hooks in CrewAgentExecutor
+  - Expose messages to TaskOutput and LiteAgentOutputs
+  - Enhance schema description of QdrantVectorSearchTool
+
+  ### Bug Fixes
+  - Ensure tracing instrumentation flags are correctly applied
+  - Fix custom tool documentation links and add Mintlify broken links action
+
+  ### Documentation
+  - Enhance task guardrail documentation with LLM-based validation support
+
+  ### Contributors
+  @danielfsbarreto, @greysonlalonde, @heitorado, @lorenzejay, @theCyberTech
+
+</Update>
+
+<Update label="Nov 07, 2025">
+  ## v1.4.1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.4.1)
+
+  ## What's Changed
+
+  ### Bug Fixes
+  - Fix handling of agent max iterations
+  - Resolve routing issues for LLM model syntax to respected providers
+
+  ### Contributors
+  @greysonlalonde
+
+</Update>
+
+<Update label="Nov 07, 2025">
+  ## v1.4.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.4.0)
+
+  ## What's Changed
+
+  ### Features
+  - Add support for non-AST plot routes
+  - Implement first-class support for MCP
+  - Add Pydantic validation dunder to BaseInterceptor
+  - Add support for LLM message interceptor hooks
+  - Cache i18n prompts for efficient use
+  - Enhance QdrantVectorSearchTool
+
+  ### Bug Fixes
+  - Fix issues with keeping stopwords updated
+  - Resolve unpickleable values in flow state
+  - Ensure lite agents course-correct on validation errors
+  - Fix callback argument hashing to ensure caching works
+  - Allow adding RAG source content from valid URLs
+  - Make plot node selection smoother
+  - Fix duplicating document IDs for knowledge
+
+  ### Refactoring
+  - Improve MCP tool execution handling with concurrent futures
+  - Simplify flow handling, typing, and logging; update UI and tests
+  - Refactor stop word management to a property
+
+  ### Documentation
+  - Migrate embedder to embedding_model and require vectordb across tool docs; add provider examples (en/ko/pt-BR)
+
+  ### Contributors
+  @danielfsbarreto, @greysonlalonde, @lorenzejay, @lucasgomide, @tonykipkemboi
+
+</Update>
+
+<Update label="Nov 01, 2025">
+  ## v1.3.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.3.0)
+
+  ## What's Changed
+
+  ### Features
+  - Refactor flow handling, typing, and logging
+  - Enhance QdrantVectorSearchTool
+
+  ### Bug Fixes
+  - Fix Firecrawl tools and add tests
+  - Refactor use_stop_words to property and add check for stop words
+
+  ### Documentation
+  - Migrate embedder to embedding_model and require vectordb across tool docs
+  - Add provider examples in English, Korean, and Portuguese
+
+  ### Refactoring
+  - Improve flow handling and UI updates
+
+  ### Contributors
+  @danielfsbarreto, @greysonlalonde, @lorenzejay, @lucasgomide, @tonykipkemboi
+
+</Update>
+
+<Update label="Oct 27, 2025">
+  ## v1.2.1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.2.1)
+
+  ## What's Changed
+
+  ### Features
+  - Add support for Datadog integration
+  - Support apps and mcps in liteagent
+
+  ### Documentation
+  - Describe mandatory environment variable for calling Platform tools for each integration
+  - Add Datadog integration documentation
+
+  ### Contributors
+  @barieom, @lorenzejay, @lucasgomide, @sabrenner
+
+</Update>
+
+<Update label="Oct 24, 2025">
+  ## v1.2.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.2.0)
+
+  ## What's Changed
+
+  ### Bug Fixes
+  - Update default LLM model and improve error logging in LLM utilities
+  - Change flow visualization directory and method inspection
+
+  ### Dropping Unused
+  - Remove aisuite
+
+  ### Contributors
+  @greysonlalonde, @lorenzejay
+
+</Update>
+
+<Update label="Oct 21, 2025">
+  ## v1.1.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.1.0)
+
+  ## What's Changed
+
+  ### Features
+  - Enhance InternalInstructor to support multiple LLM providers
+  - Implement mypy plugin base
+  - Improve QdrantVectorSearchTool
+
+  ### Bug Fixes
+  - Correct broken integration documentation links
+  - Fix double trace call and add types
+  - Pin template versions to latest
+
+  ### Documentation
+  - Update LLM integration details and examples
+
+  ### Refactoring
+  - Improve CrewBase typing
+
+  ### Contributors
+  @cwarre33, @danielfsbarreto, @greysonlalonde, @lorenzejay
+
+</Update>
+
+<Update label="Oct 20, 2025">
+  ## v1.0.0
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0)
+
+  ## What's Changed
+
+  ### Features
+  - Bump versions to 1.0.0
+  - Enhance knowledge and guardrail event handling in Agent class
+  - Inject tool repository credentials in crewai run command
+
+  ### Bug Fixes
+  - Preserve nested condition structure in Flow decorators
+  - Add standard print parameters to Printer.print method
+  - Fix errors when there is no input() available
+  - Add a leeway of 10s when decoding JWT
+  - Revert bad cron schedule
+  - Correct cron schedule to run every 5 days at specific dates
+  - Use system PATH for Docker binary instead of hardcoded path
+  - Add CodeQL configuration to properly exclude template directories
+
+  ### Documentation
+  - Update security policy for vulnerability reporting
+  - Add guide for capturing telemetry logs in CrewAI AMP
+  - Add missing /resume files
+  - Clarify webhook URL parameter in HITL workflows
+
+  ### Contributors
+  @Vidit-Ostwal, @greysonlalonde, @heitorado, @joaomdmoura, @lorenzejay, @lucasgomide, @mplachta, @theCyberTech
+
+</Update>
+
+<Update label="Oct 18, 2025">
+  ## v1.0.0b3 (Pre-release)
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0b3)
+
+  ## What's Changed
+
+  ### Features
+  - Enhance task guardrail functionality and validation
+  - Improve support for importing native SDK
+  - Add Azure native tests
+  - Enhance BedrockCompletion class with advanced features
+  - Enhance GeminiCompletion class with client parameter support
+  - Enhance AnthropicCompletion class with additional client parameters
+
+  ### Bug Fixes
+  - Preserve nested condition structure in Flow decorators
+  - Add standard print parameters to Printer.print method
+  - Remove stdout prints and improve test determinism
+
+  ### Refactoring
+  - Convert project module to metaclass with full typing
+
+  ### Contributors
+  @greysonlalonde, @lorenzejay
+
+</Update>
+
+<Update label="Oct 16, 2025">
+  ## v1.0.0b2 (Pre-release)
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0b2)
+
+  ## What's Changed
+
+  ### Features
+  - Enhance OpenAICompletion class with additional client parameters
+  - Improve event bus thread safety and async support
+  - Inject tool repository credentials in crewai run command
+
+  ### Bug Fixes
+  - Fix issue where it errors out if there is no input() available
+  - Add a leeway of 10s when decoding JWT
+  - Fix copying and adding NOT_SPECIFIED check in task.py
+
+  ### Documentation
+  - Ensure CREWAI_PLATFORM_INTEGRATION_TOKEN is mentioned in documentation
+  - Update triggers documentation
+
+  ### Contributors
+  @Vidit-Ostwal, @greysonlalonde, @heitorado, @joaomdmoura, @lorenzejay, @lucasgomide
+
+</Update>
+
+<Update label="Oct 14, 2025">
+  ## v1.0.0b1 (Pre-release)
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0b1)
+
+  ## What's Changed
+
+  ### Features
+  - Enhance OpenAICompletion class with additional client parameters
+  - Improve event bus thread safety and async support
+  - Implement Bedrock LLM integration
+
+  ### Bug Fixes
+  - Fix issue with missing input() availability
+  - Resolve JWT decoding error by adding a leeway of 10 seconds
+  - Inject tool repository credentials in crewai run command
+  - Fix copy and add NOT_SPECIFIED check in task.py
+
+  ### Documentation
+  - Ensure CREWAI_PLATFORM_INTEGRATION_TOKEN is mentioned in documentation
+  - Update triggers documentation
+
+  ### Contributors
+  @Vidit-Ostwal, @greysonlalonde, @heitorado, @joaomdmoura, @lorenzejay, @lucasgomide
+
+</Update>
+
+<Update label="Oct 13, 2025">
+  ## v0.203.1
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/0.203.1)
+
+  ## What's Changed
+
+  ### Core Improvements & Fixes
+  - Fixed injection of tool repository credentials into the `crewai run` command
+  - Added a 10-second leeway when decoding JWTs to reduce token validation errors
+  - Corrected (then reverted) cron schedule fix intended to run jobs every 5 days at specific dates
+
+  ### Documentation & Guides
+  - Updated security policy to clarify the process for vulnerability reporting
+
+</Update>
+
+<Update label="Oct 09, 2025">
+  ## v1.0.0a4 (Pre-release)
+
+  [View release on GitHub](https://github.com/crewAIInc/crewAI/releases/tag/1.0.0a4)
+
+  ## What's Changed
+
+  ### Features
+  - Enhance knowledge and guardrail event handling in Agent class
+  - Introduce trigger listing and execution commands for local development
+  - Update documentation with new approach to consume Platform Actions
+  - Add guide for capturing telemetry logs in CrewAI AMP
+
+  ### Bug Fixes
+  - Revert bad cron schedule
+  - Correct cron schedule to run every 5 days at specific dates
+  - Remove duplicate line and add explicit environment variable
+  - Resolve linting errors across the codebase
+  - Replace print statements with logger in agent and memory handling
+  - Use system PATH for Docker binary instead of hardcoded path
+  - Allow failed PyPI publish
+  - Match tag and release title, ignore devtools build for PyPI
+
+  ### Documentation
+  - Update security policy for vulnerability reporting
+  - Add missing /resume files
+  - Clarify webhook URL parameter in HITL workflows
+
+  ### Contributors
+  @Vidit-Ostwal, @greysonlalonde, @lorenzejay, @lucasgomide, @theCyberTech
+
+</Update>
+
 <Update label="Sep 30, 2025">
  ## v1.0.0a1

--- a/docs/en/concepts/flows.mdx
+++ b/docs/en/concepts/flows.mdx
@@ -574,6 +574,10 @@ When you run this Flow, the output will change based on the random boolean value

 ### Human in the Loop (human feedback)

+<Note>
+The `@human_feedback` decorator requires **CrewAI version 1.8.0 or higher**.
+</Note>
+
 The `@human_feedback` decorator enables human-in-the-loop workflows by pausing flow execution to collect feedback from a human. This is useful for approval gates, quality review, and decision points that require human judgment.

 ```python Code
--- a/docs/en/enterprise/features/pii-trace-redactions.mdx
+++ b/docs/en/enterprise/features/pii-trace-redactions.mdx
@@ -0,0 +1,342 @@
+---
+title: PII Redaction for Traces
+description: "Automatically redact sensitive data from crew and flow execution traces"
+icon: "lock"
+mode: "wide"
+---
+
+## Overview
+
+PII Redaction is a CrewAI AMP feature that automatically detects and masks Personally Identifiable Information (PII) in your crew and flow execution traces. This ensures sensitive data like credit card numbers, social security numbers, email addresses, and names are not exposed in your CrewAI AMP traces. You can also create custom recognizers to protect organization-specific data.
+
+
+<Info>
+  PII Redaction is available on the Enterprise plan.
+  Deployment must be version 1.8.0 or higher.
+</Info>
+
+
+<Frame>
+  ![PII Redaction Overview](/images/enterprise/pii_mask_recognizer_trace_example.png)
+</Frame>
+
+
+## Why PII Redaction Matters
+
+When running AI agents in production, sensitive information often flows through your crews:
+
+- Customer data from CRM integrations
+- Financial information from payment processors
+- Personal details from form submissions
+- Internal employee data
+
+Without proper redaction, this data appears in traces, making compliance with regulations like GDPR, HIPAA, and PCI-DSS challenging. PII Redaction solves this by automatically masking sensitive data before it's stored in traces.
+
+## How It Works
+
+1. **Detect** - Scan trace event data for known PII patterns
+2. **Classify** - Identify the type of sensitive data (credit card, SSN, email, etc.)
+3. **Mask/Redact** - Replace the sensitive data with masked values based on your configuration
+
+```
+Original: "Contact john.doe@company.com or call 555-123-4567"
+Redacted: "Contact <EMAIL_ADDRESS> or call <PHONE_NUMBER>"
+```
+
+## Enabling PII Redaction
+
+<Info>
+  You must be on the Enterprise plan and your deployment must be version 1.8.0 or higher to use this feature.
+</Info>
+
+<Steps>
+  <Step title="Navigate to Crew Settings">
+    In the CrewAI AMP dashboard, select your deployed crew and go to one of your deployments/automations, then navigate to **Settings** → **PII Protection**.
+  </Step>
+
+  <Step title="Enable PII Protection">
+    Toggle on **PII Redaction for Traces**. This will enable automatic scanning and redaction of trace data.
+
+    <Info>
+      You need to manually enable PII Redaction for each deployment.
+    </Info>
+
+    <Frame>
+      ![Enable PII Redaction](/images/enterprise/pii_mask_recognizer_enable.png)
+    </Frame>
+  </Step>
+
+  <Step title="Configure Entity Types">
+    Select which types of PII to detect and redact. Each entity can be individually enabled or disabled.
+
+    <Frame>
+      ![Configure Entities](/images/enterprise/pii_mask_recognizer_supported_entities.png)
+    </Frame>
+  </Step>
+
+  <Step title="Save">
+    Save your configuration. PII redaction will be active on all subsequent crew executions, no redeployment is needed.
+  </Step>
+</Steps>
+
+## Supported Entity Types
+
+CrewAI supports the following PII entity types, organized by category.
+
+### Global Entities
+
+| Entity | Description | Example |
+|--------|-------------|---------|
+| `CREDIT_CARD` | Credit/debit card numbers | "4111-1111-1111-1111" |
+| `CRYPTO` | Cryptocurrency wallet addresses | "bc1qxy2kgd..." |
+| `DATE_TIME` | Dates and times | "January 15, 2024" |
+| `EMAIL_ADDRESS` | Email addresses | "john@example.com" |
+| `IBAN_CODE` | International bank account numbers | "DE89 3704 0044 0532 0130 00" |
+| `IP_ADDRESS` | IPv4 and IPv6 addresses | "192.168.1.1" |
+| `LOCATION` | Geographic locations | "New York City" |
+| `MEDICAL_LICENSE` | Medical license numbers | "MD12345" |
+| `NRP` | Nationalities, religious, or political groups | - |
+| `PERSON` | Personal names | "John Doe" |
+| `PHONE_NUMBER` | Phone numbers in various formats | "+1 (555) 123-4567" |
+| `URL` | Web URLs | "https://example.com" |
+
+### US-Specific Entities
+
+| Entity | Description | Example |
+|--------|-------------|---------|
+| `US_BANK_NUMBER` | US Bank account numbers | "1234567890" |
+| `US_DRIVER_LICENSE` | US Driver's license numbers | "D1234567" |
+| `US_ITIN` | Individual Taxpayer ID | "900-70-0000" |
+| `US_PASSPORT` | US Passport numbers | "123456789" |
+| `US_SSN` | Social Security Numbers | "123-45-6789" |
+
+## Redaction Actions
+
+For each enabled entity, you can configure how the data is redacted:
+
+| Action | Description | Example Output |
+|--------|-------------|----------------|
+| `mask` | Replace with the entity type label | `<CREDIT_CARD>` |
+| `redact` | Completely remove the text | *(empty)* |
+
+## Custom Recognizers
+
+In addition to built-in entities, you can create **custom recognizers** to detect organization-specific PII patterns.
+
+<Frame>
+  ![Custom Recognizers](/images/enterprise/pii_mask_recognizer.png)
+</Frame>
+
+### Recognizer Types
+
+You have two options for custom recognizers:
+
+| Type | Best For | Example Use Case |
+|------|----------|------------------|
+| **Pattern-based (Regex)** | Structured data with predictable formats | Salary amounts, employee IDs, project codes |
+| **Deny-list** | Exact string matches | Company names, internal codenames, specific terms |
+
+### Creating a Custom Recognizer
+
+<Steps>
+  <Step title="Navigate to Custom Recognizers">
+    Go to your Organization **Settings** → **Organization** → **Add Recognizer**.
+  </Step>
+
+  <Step title="Configure the Recognizer">
+    <Frame>
+      ![Configure Recognizer](/images/enterprise/pii_mask_recognizer_create.png)
+    </Frame>
+
+    Configure the following fields:
+    - **Name**: A descriptive name for the recognizer
+    - **Entity Type**: The entity label that will appear in redacted output (e.g., `EMPLOYEE_ID`, `SALARY`)
+    - **Type**: Choose between Regex Pattern or Deny List
+    - **Pattern/Values**: Regex pattern or list of strings to match
+    - **Confidence Threshold**: Minimum score (0.0-1.0) required for a match to trigger redaction. Higher values (e.g., 0.8) reduce false positives but may miss some matches. Lower values (e.g., 0.5) catch more matches but may over-redact. Default is 0.8.
+    - **Context Words** (optional): Words that increase detection confidence when found nearby
+  </Step>
+
+  <Step title="Save">
+    Save the recognizer. It will be available to enable on your deployments.
+  </Step>
+</Steps>
+
+### Understanding Entity Types
+
+The **Entity Type** determines how matched content appears in redacted traces:
+
+```
+Entity Type: SALARY
+Pattern: salary:\s*\$\s*\d+
+Input: "Employee salary: $50,000"
+Output: "Employee <SALARY>"
+```
+
+### Using Context Words
+
+Context words improve accuracy by increasing confidence when specific terms appear near the matched pattern:
+
+```
+Context Words: "project", "code", "internal"
+Entity Type: PROJECT_CODE
+Pattern: PRJ-\d{4}
+```
+
+When "project" or "code" appears near "PRJ-1234", the recognizer has higher confidence it's a true match, reducing false positives.
+
+
+## Viewing Redacted Traces
+
+Once PII redaction is enabled, your traces will show redacted values in place of sensitive data:
+
+```
+Task Output: "Customer <PERSON> placed order #12345.
+Contact email: <EMAIL_ADDRESS>, phone: <PHONE_NUMBER>.
+Payment processed for card ending in <CREDIT_CARD>."
+```
+
+Redacted values are clearly marked with angle brackets and the entity type label (e.g., `<EMAIL_ADDRESS>`), making it easy to understand what data was protected while still allowing you to debug and monitor crew behavior.
+
+
+
+## Best Practices
+
+### Performance Considerations
+
+<Steps>
+  <Step title="Enable Only Needed Entities">
+    Each enabled entity adds processing overhead. Only enable entities relevant to your data.
+  </Step>
+
+  <Step title="Use Specific Patterns">
+    For custom recognizers, use specific patterns to reduce false positives and improve performance. Regex patterns are best when identifying specific patterns in the traces such as salary, employee id, project code, etc. Deny-list recognizers are best when identifying exact strings in the traces such as company names, internal codenames, etc.
+  </Step>
+
+  <Step title="Leverage Context Words">
+    Context words improve accuracy by only triggering detection when surrounding text matches.
+  </Step>
+</Steps>
+
+## Troubleshooting
+
+<Accordion title="PII Not Being Redacted">
+  **Possible Causes:**
+  - Entity type not enabled in configuration
+  - Pattern doesn't match the data format
+  - Custom recognizer has syntax errors
+
+  **Solutions:**
+  - Verify entity is enabled in Settings → Security
+  - Test regex patterns with sample data
+  - Check logs for configuration errors
+</Accordion>
+
+<Accordion title="Too Much Data Being Redacted">
+  **Possible Causes:**
+  - Overly broad entity types enabled (e.g., `DATE_TIME` catches dates everywhere)
+  - Custom recognizer patterns are too general
+
+  **Solutions:**
+  - Disable entities that cause false positives
+  - Make custom patterns more specific
+  - Add context words to improve accuracy
+</Accordion>
+
+<Accordion title="Performance Issues">
+  **Possible Causes:**
+  - Too many entities enabled
+  - NLP-based entities (`PERSON`, `LOCATION`, `NRP`) are computationally expensive as they use machine learning models
+
+  **Solutions:**
+  - Only enable entities you actually need
+  - Consider using pattern-based alternatives where possible
+  - Monitor trace processing times in the dashboard
+</Accordion>
+
+---
+
+## Practical Example: Salary Pattern Matching
+
+This example demonstrates how to create a custom recognizer to detect and mask salary information in your traces.
+
+### Use Case
+
+Your crew processes employee or financial data that includes salary information in formats like:
+- `salary: $50,000`
+- `salary: $125,000.00`
+- `salary:$1,500.50`
+
+You want to automatically mask these values to protect sensitive compensation data.
+
+### Configuration
+
+<Frame>
+  ![Salary Recognizer Configuration](/images/enterprise/pii_mask_custom_recognizer_salary.png)
+</Frame>
+
+| Field | Value |
+|-------|-------|
+| **Name** | `SALARY` |
+| **Entity Type** | `SALARY` |
+| **Type** | Regex Pattern |
+| **Regex Pattern** | `salary:\s*\$\s*\d{1,3}(,\d{3})*(\.\d{2})?` |
+| **Action** | Mask |
+| **Confidence Threshold** | `0.8` |
+| **Context Words** | `salary, compensation, pay, wage, income` |
+
+### Regex Pattern Breakdown
+
+| Pattern Component | Meaning |
+|-------------------|---------|
+| `salary:` | Matches the literal text "salary:" |
+| `\s*` | Matches zero or more whitespace characters |
+| `\$` | Matches the dollar sign (escaped) |
+| `\s*` | Matches zero or more whitespace characters after $ |
+| `\d{1,3}` | Matches 1-3 digits (e.g., "1", "50", "125") |
+| `(,\d{3})*` | Matches comma-separated thousands (e.g., ",000", ",500,000") |
+| `(\.\d{2})?` | Optionally matches cents (e.g., ".00", ".50") |
+
+### Example Results
+
+```
+Original: "Employee record shows salary: $125,000.00 annually"
+Redacted: "Employee record shows <SALARY> annually"
+
+Original: "Base salary:$50,000 with bonus potential"
+Redacted: "Base <SALARY> with bonus potential"
+```
+
+<Tip>
+  Adding context words like "salary", "compensation", "pay", "wage", and "income" helps increase detection confidence when these terms appear near the matched pattern, reducing false positives.
+</Tip>
+
+### Enable the Recognizer for Your Deployments
+
+<Warning>
+  Creating a custom recognizer at the organization level does not automatically enable it for your deployments. You must manually enable each recognizer for every deployment where you want it applied.
+</Warning>
+
+After creating your custom recognizer, enable it for each deployment:
+
+<Steps>
+  <Step title="Navigate to Your Deployment">
+    Go to your deployment/automation and open **Settings** → **PII Protection**.
+  </Step>
+
+  <Step title="Select Custom Recognizers">
+    Under **Mask Recognizers**, you'll see your organization-defined recognizers. Check the box next to the recognizers you want to enable.
+
+    <Frame>
+      ![Enable Custom Recognizer](/images/enterprise/pii_mask_recognizers_options.png)
+    </Frame>
+  </Step>
+
+  <Step title="Save Configuration">
+    Save your changes. The recognizer will be active on all subsequent executions for this deployment.
+  </Step>
+</Steps>
+
+<Info>
+  Repeat this process for each deployment where you need the custom recognizer. This gives you granular control over which recognizers are active in different environments (e.g., development vs. production).
+</Info>
--- a/docs/en/learn/a2a-agent-delegation.mdx
+++ b/docs/en/learn/a2a-agent-delegation.mdx
@@ -91,6 +91,10 @@ The `A2AConfig` class accepts the following parameters:
  Update mechanism for receiving task status. Options: `StreamingConfig`, `PollingConfig`, or `PushNotificationConfig`.
 </ParamField>

+<ParamField path="transport_protocol" type="Literal['JSONRPC', 'GRPC', 'HTTP+JSON']" default="JSONRPC">
+  Transport protocol for A2A communication. Options: `JSONRPC` (default), `GRPC`, or `HTTP+JSON`.
+</ParamField>
+
 ## Authentication

 For A2A agents that require authentication, use one of the provided auth schemes:
--- a/docs/en/learn/human-feedback-in-flows.mdx
+++ b/docs/en/learn/human-feedback-in-flows.mdx
@@ -7,6 +7,10 @@ mode: "wide"

 ## Overview

+<Note>
+The `@human_feedback` decorator requires **CrewAI version 1.8.0 or higher**. Make sure to update your installation before using this feature.
+</Note>
+
 The `@human_feedback` decorator enables human-in-the-loop (HITL) workflows directly within CrewAI Flows. It allows you to pause flow execution, present output to a human for review, collect their feedback, and optionally route to different listeners based on the feedback outcome.

 This is particularly valuable for:
--- a/docs/en/learn/human-in-the-loop.mdx
+++ b/docs/en/learn/human-in-the-loop.mdx
@@ -11,10 +11,10 @@ Human-in-the-Loop (HITL) is a powerful approach that combines artificial intelli

 CrewAI offers two main approaches for implementing human-in-the-loop workflows:

-| Approach | Best For | Integration |
-|----------|----------|-------------|
-| **Flow-based** (`@human_feedback` decorator) | Local development, console-based review, synchronous workflows | [Human Feedback in Flows](/en/learn/human-feedback-in-flows) |
-| **Webhook-based** (Enterprise) | Production deployments, async workflows, external integrations (Slack, Teams, etc.) | This guide |
+| Approach | Best For | Integration | Version |
+|----------|----------|-------------|---------|
+| **Flow-based** (`@human_feedback` decorator) | Local development, console-based review, synchronous workflows | [Human Feedback in Flows](/en/learn/human-feedback-in-flows) | **1.8.0+** |
+| **Webhook-based** (Enterprise) | Production deployments, async workflows, external integrations (Slack, Teams, etc.) | This guide | - |

 <Tip>
 If you're building flows and want to add human review steps with routing based on feedback, check out the [Human Feedback in Flows](/en/learn/human-feedback-in-flows) guide for the `@human_feedback` decorator.
--- a/docs/en/observability/galileo.mdx
+++ b/docs/en/observability/galileo.mdx
@@ -0,0 +1,115 @@
+---
+title: Galileo
+description: Galileo integration for CrewAI tracing and evaluation
+icon: telescope
+mode: "wide"
+---
+
+## Overview
+
+This guide demonstrates how to integrate **Galileo** with **CrewAI**
+for comprehensive tracing and Evaluation Engineering.
+By the end of this guide, you will be able to trace your CrewAI agents,
+monitor their performance, and evaluate their behaviour with
+Galileo's powerful observability platform.
+
+> **What is Galileo?** [Galileo](https://galileo.ai) is AI evaluation and observability
+platform that delivers end-to-end tracing, evaluation,
+and monitoring for AI applications. It enables teams to capture ground truth,
+create robust guardrails, and run systematic experiments with
+built-in experiment tracking and performance analytics—ensuring reliability,
+transparency, and continuous improvement across the AI lifecycle.
+
+## Getting started
+
+This tutorial follows the [CrewAI quickstart](/en/quickstart) and shows how to add
+Galileo's [CrewAIEventListener](https://v2docs.galileo.ai/sdk-api/python/reference/handlers/crewai/handler),
+an event handler.
+For more information, see Galileo’s
+[Add Galileo to a CrewAI Application](https://v2docs.galileo.ai/how-to-guides/third-party-integrations/add-galileo-to-crewai/add-galileo-to-crewai)
+how-to guide.
+
+> **Note** This tutorial assumes you have completed the [CrewAI quickstart](/en/quickstart).
+If you want a completed comprehensive example, see the Galileo
+[CrewAI sdk-example repo](https://github.com/rungalileo/sdk-examples/tree/main/python/agent/crew-ai).
+
+### Step 1: Install dependencies
+
+Install the required dependencies for your app.
+Create a virtual environment using your preferred method,
+then install dependencies inside that environment using your
+preferred tool:
+
+```bash
+uv add galileo 
+```
+
+### Step 2: Add to the .env file from the [CrewAI quickstart](/en/quickstart)
+
+```bash
+# Your Galileo API key
+GALILEO_API_KEY="your-galileo-api-key"
+
+# Your Galileo project name
+GALILEO_PROJECT="your-galileo-project-name"
+
+# The name of the Log stream you want to use for logging
+GALILEO_LOG_STREAM="your-galileo-log-stream "
+```
+
+### Step 3: Add the Galileo event listener
+
+To enable logging with Galileo, you need to create an instance of the `CrewAIEventListener`.
+Import the Galileo CrewAI handler package by
+adding the following code at the top of your main.py file:
+
+```python
+from galileo.handlers.crewai.handler import CrewAIEventListener
+```
+
+At the start of your run function, create the event listener:
+
+```python
+def run():
+    # Create the event listener
+    CrewAIEventListener()
+    # The rest of your existing code goes here
+```
+
+When you create the listener instance, it is automatically
+registered with CrewAI.
+
+### Step 4: Run your crew
+
+Run your crew with the CrewAI CLI:
+
+```bash
+crewai run
+```
+
+### Step 5: View the traces in Galileo
+
+Once your crew has finished, the traces will be flushed and appear in Galileo.
+
+![Galileo trace view](/images/galileo-trace-veiw.png)
+  
+## Understanding the Galileo Integration
+
+Galileo integrates with CrewAI by registering an event listener
+that captures Crew execution events (e.g., agent actions, tool calls, model responses)
+and forwards them to Galileo for observability and evaluation.
+
+### Understanding the event listener
+
+Creating a `CrewAIEventListener()` instance is all that’s
+required to enable Galileo for a CrewAI run. When instantiated, the listener:
+
+- Automatically registers itself with CrewAI
+- Reads Galileo configuration from environment variables
+- Logs all run data to the Galileo project and log stream specified by
+  `GALILEO_PROJECT` and `GALILEO_LOG_STREAM`
+
+No additional configuration or code changes are required.
+All data from this run is logged to the Galileo project and
+log stream specified by your environment configuration
+(for example, GALILEO_PROJECT and GALILEO_LOG_STREAM).