adjust aop to amp docs lang (#4179)

* adjust aop to amp docs lang * whoop no print
2026-01-11 00:58:30 +00:00 · 2026-01-05 15:30:21 -08:00
parent f8deb0fd18
commit 25c0c030ce
203 changed files with 5176 additions and 2715 deletions
--- a/docs/en/enterprise/features/rbac.mdx
+++ b/docs/en/enterprise/features/rbac.mdx
@@ -7,10 +7,10 @@ mode: "wide"

 ## Overview

-RBAC in CrewAI AOP enables secure, scalable access management through a combination of organization‑level roles and automation‑level visibility controls.
+RBAC in CrewAI AMP enables secure, scalable access management through a combination of organization‑level roles and automation‑level visibility controls.

 <Frame>
-  <img src="/images/enterprise/users_and_roles.png" alt="RBAC overview in CrewAI AOP" />
+  <img src="/images/enterprise/users_and_roles.png" alt="RBAC overview in CrewAI AMP" />

 </Frame>

@@ -28,10 +28,11 @@ You can configure users and roles in Settings → Roles.

 <Steps>
  <Step title="Open Roles settings">
-    Go to <b>Settings → Roles</b> in CrewAI AOP.
+    Go to <b>Settings → Roles</b> in CrewAI AMP.
  </Step>
  <Step title="Choose a role type">
-    Use a predefined role (<b>Owner</b>, <b>Member</b>) or click <b>Create role</b> to define a custom one.
+    Use a predefined role (<b>Owner</b>, <b>Member</b>) or click{" "}
+    <b>Create role</b> to define a custom one.
  </Step>
  <Step title="Assign to members">
    Select users and assign the role. You can change this anytime.
@@ -40,10 +41,10 @@ You can configure users and roles in Settings → Roles.

 ### Configuration summary

-| Area | Where to configure | Options |
-|:---|:---|:---|
-| Users & Roles | Settings → Roles | Predefined: Owner, Member; Custom roles |
-| Automation visibility | Automation → Settings → Visibility | Private; Whitelist users/roles |
+| Area                  | Where to configure                 | Options                                 |
+| :-------------------- | :--------------------------------- | :-------------------------------------- |
+| Users & Roles         | Settings → Roles                   | Predefined: Owner, Member; Custom roles |
+| Automation visibility | Automation → Settings → Visibility | Private; Whitelist users/roles          |

 ## Automation‑level Access Control

@@ -70,30 +71,34 @@ You can configure automation‑level access control in Automation → Settings
    Navigate to <b>Automation → Settings → Visibility</b>.
  </Step>
  <Step title="Set visibility">
-    Choose <b>Private</b> to restrict access. The organization owner always retains access.
+    Choose <b>Private</b> to restrict access. The organization owner always
+    retains access.
  </Step>
  <Step title="Whitelist access">
-    Add specific users and roles allowed to view, run, and access logs/metrics/settings.
+    Add specific users and roles allowed to view, run, and access
+    logs/metrics/settings.
  </Step>
  <Step title="Save and verify">
-    Save changes, then confirm that non‑whitelisted users cannot view or run the automation.
+    Save changes, then confirm that non‑whitelisted users cannot view or run the
+    automation.
  </Step>
 </Steps>

 ### Private visibility: access outcomes

-| Action | Owner | Whitelisted user/role | Not whitelisted |
-|:---|:---|:---|:---|
-| View automation | ✓ | ✓ | ✗ |
-| Run automation/API | ✓ | ✓ | ✗ |
-| Access logs/metrics/settings | ✓ | ✓ | ✗ |
+| Action                       | Owner | Whitelisted user/role | Not whitelisted |
+| :--------------------------- | :---- | :-------------------- | :-------------- |
+| View automation              | ✓     | ✓                     | ✗               |
+| Run automation/API           | ✓     | ✓                     | ✗               |
+| Access logs/metrics/settings | ✓     | ✓                     | ✗               |

 <Tip>
-The organization owner always has access. In private mode, only whitelisted users and roles can view, run, and access logs/metrics/settings.
+  The organization owner always has access. In private mode, only whitelisted
+  users and roles can view, run, and access logs/metrics/settings.
 </Tip>

 <Frame>
-  <img src="/images/enterprise/visibility.png" alt="Automation Visibility settings in CrewAI AOP" />
+  <img src="/images/enterprise/visibility.png" alt="Automation Visibility settings in CrewAI AMP" />

 </Frame>

--- a/docs/en/enterprise/features/tools-and-integrations.mdx
+++ b/docs/en/enterprise/features/tools-and-integrations.mdx
@@ -18,222 +18,226 @@ Tools & Integrations is the central hub for connecting third‑party apps and ma
 <Tabs>
  <Tab title="Integrations" icon="plug">

-  ## Agent Apps (Integrations)
+## Agent Apps (Integrations)

-  Connect enterprise‑grade applications (e.g., Gmail, Google Drive, HubSpot, Slack) via OAuth to enable agent actions.
+Connect enterprise‑grade applications (e.g., Gmail, Google Drive, HubSpot, Slack) via OAuth to enable agent actions.

-  <Steps>
-    <Step title="Connect">
-      Click <b>Connect</b> on an app and complete OAuth.
-    </Step>
-    <Step title="Configure">
-      Optionally adjust scopes, triggers, and action availability.
-    </Step>
-    <Step title="Use in Agents">
-      Connected services become available as tools for your agents.
-    </Step>
-  </Steps>
+{" "}
+<Steps>
+  <Step title="Connect">
+    Click <b>Connect</b> on an app and complete OAuth.
+  </Step>
+  <Step title="Configure">
+    Optionally adjust scopes, triggers, and action availability.
+  </Step>
+  <Step title="Use in Agents">
+    Connected services become available as tools for your agents.
+  </Step>
+</Steps>

-  <Frame>
-    ![Integrations Grid](/images/enterprise/agent-apps.png)
-  </Frame>
+{" "}
+<Frame>![Integrations Grid](/images/enterprise/agent-apps.png)</Frame>

-  ### Connect your Account
+### Connect your Account

-  1. Go to <Link href="https://app.crewai.com/crewai_plus/connectors">Integrations</Link>
-  2. Click <b>Connect</b> on the desired service
-  3. Complete the OAuth flow and grant scopes
-  4. Copy your Enterprise Token from <Link href="https://app.crewai.com/crewai_plus/settings/integrations">Integration Settings</Link>
+1. Go to <Link href="https://app.crewai.com/crewai_plus/connectors">Integrations</Link>
+2. Click <b>Connect</b> on the desired service
+3. Complete the OAuth flow and grant scopes
+4. Copy your Enterprise Token from <Link href="https://app.crewai.com/crewai_plus/settings/integrations">Integration Settings</Link>

-  <Frame>
-    ![Enterprise Token](/images/enterprise/enterprise_action_auth_token.png)
-  </Frame>
+{" "}
+<Frame>
+  ![Enterprise Token](/images/enterprise/enterprise_action_auth_token.png)
+</Frame>

-  ### Install Integration Tools
+### Install Integration Tools

-  To use the integrations locally, you need to install the latest `crewai-tools` package.
+To use the integrations locally, you need to install the latest `crewai-tools` package.

-  ```bash
-  uv add crewai-tools
-  ```
+```bash
+uv add crewai-tools
+```

-  ### Environment Variable Setup
+### Environment Variable Setup

-  <Note>
-    To use integrations with `Agent(apps=[])`, you must set the `CREWAI_PLATFORM_INTEGRATION_TOKEN` environment variable with your Enterprise Token.
-  </Note>
+{" "}
+<Note>
+  To use integrations with `Agent(apps=[])`, you must set the
+  `CREWAI_PLATFORM_INTEGRATION_TOKEN` environment variable with your Enterprise
+  Token.
+</Note>

-  ```bash
-  export CREWAI_PLATFORM_INTEGRATION_TOKEN="your_enterprise_token"
-  ```
+```bash
+export CREWAI_PLATFORM_INTEGRATION_TOKEN="your_enterprise_token"
+```

-  Or add it to your `.env` file:
+Or add it to your `.env` file:

-  ```
-  CREWAI_PLATFORM_INTEGRATION_TOKEN=your_enterprise_token
-  ```
+```
+CREWAI_PLATFORM_INTEGRATION_TOKEN=your_enterprise_token
+```

-  ### Usage Example
+### Usage Example

-  <Tip>
-    Use the new streamlined approach to integrate enterprise apps. Simply specify the app and its actions directly in the Agent configuration.
-  </Tip>
+{" "}
+<Tip>
+  Use the new streamlined approach to integrate enterprise apps. Simply specify
+  the app and its actions directly in the Agent configuration.
+</Tip>

-  ```python
-  from crewai import Agent, Task, Crew
+```python
+from crewai import Agent, Task, Crew

-  # Create an agent with Gmail capabilities
-  email_agent = Agent(
-      role="Email Manager",
-      goal="Manage and organize email communications",
-      backstory="An AI assistant specialized in email management and communication.",
-      apps=['gmail', 'gmail/send_email']  # Using canonical name 'gmail'
-  )
+# Create an agent with Gmail capabilities
+email_agent = Agent(
+    role="Email Manager",
+    goal="Manage and organize email communications",
+    backstory="An AI assistant specialized in email management and communication.",
+    apps=['gmail', 'gmail/send_email']  # Using canonical name 'gmail'
+)

-  # Task to send an email
-  email_task = Task(
-      description="Draft and send a follow-up email to john@example.com about the project update",
-      agent=email_agent,
-      expected_output="Confirmation that email was sent successfully"
-  )
+# Task to send an email
+email_task = Task(
+    description="Draft and send a follow-up email to john@example.com about the project update",
+    agent=email_agent,
+    expected_output="Confirmation that email was sent successfully"
+)

-  # Run the task
-  crew = Crew(
-      agents=[email_agent],
-      tasks=[email_task]
-  )
+# Run the task
+crew = Crew(
+    agents=[email_agent],
+    tasks=[email_task]
+)

-  # Run the crew
-  crew.kickoff()
-  ```
+# Run the crew
+crew.kickoff()
+```

-  ### Filtering Tools
+### Filtering Tools

-  ```python
-  from crewai import Agent, Task, Crew
+```python
+from crewai import Agent, Task, Crew

-  # Create agent with specific Gmail actions only
-  gmail_agent = Agent(
-      role="Gmail Manager",
-      goal="Manage gmail communications and notifications",
-      backstory="An AI assistant that helps coordinate gmail communications.",
-      apps=['gmail/fetch_emails']  # Using canonical name with specific action
-  )
+# Create agent with specific Gmail actions only
+gmail_agent = Agent(
+    role="Gmail Manager",
+    goal="Manage gmail communications and notifications",
+    backstory="An AI assistant that helps coordinate gmail communications.",
+    apps=['gmail/fetch_emails']  # Using canonical name with specific action
+)

-  notification_task = Task(
-      description="Find the email from john@example.com",
-      agent=gmail_agent,
-      expected_output="Email found from john@example.com"
-  )
+notification_task = Task(
+    description="Find the email from john@example.com",
+    agent=gmail_agent,
+    expected_output="Email found from john@example.com"
+)

-  crew = Crew(
-      agents=[gmail_agent],
-      tasks=[notification_task]
-  )
-  ```
+crew = Crew(
+    agents=[gmail_agent],
+    tasks=[notification_task]
+)
+```

-  On a deployed crew, you can specify which actions are available for each integration from the service settings page.
+On a deployed crew, you can specify which actions are available for each integration from the service settings page.

-  <Frame>
-    ![Filter Actions](/images/enterprise/filtering_enterprise_action_tools.png)
-  </Frame>
+{" "}
+<Frame>
+  ![Filter Actions](/images/enterprise/filtering_enterprise_action_tools.png)
+</Frame>

-  ### Scoped Deployments (multi‑user orgs)
+### Scoped Deployments (multi‑user orgs)

-  You can scope each integration to a specific user. For example, a crew that connects to Google can use a specific user’s Gmail account.
+You can scope each integration to a specific user. For example, a crew that connects to Google can use a specific user’s Gmail account.

-  <Tip>
-    Useful when different teams/users must keep data access separated.
-  </Tip>
+{" "}
+<Tip>Useful when different teams/users must keep data access separated.</Tip>

-  Use the `user_bearer_token` to scope authentication to the requesting user. If the user isn’t logged in, the crew won’t use connected integrations. Otherwise it falls back to the default bearer token configured for the deployment.
+Use the `user_bearer_token` to scope authentication to the requesting user. If the user isn’t logged in, the crew won’t use connected integrations. Otherwise it falls back to the default bearer token configured for the deployment.

-  <Frame>
-    ![User Bearer Token](/images/enterprise/user_bearer_token.png)
-  </Frame>
+{" "}
+<Frame>![User Bearer Token](/images/enterprise/user_bearer_token.png)</Frame>

-  <div id="catalog"></div>
-  ### Catalog
+{" "}
+<div id="catalog"></div>
+### Catalog

-  #### Communication & Collaboration
-  - Gmail — Manage emails and drafts
-  - Slack — Workspace notifications and alerts
-  - Microsoft — Office 365 and Teams integration
+#### Communication & Collaboration

-  #### Project Management
-  - Jira — Issue tracking and project management
-  - ClickUp — Task and productivity management
-  - Asana — Team task and project coordination
-  - Notion — Page and database management
-  - Linear — Software project and bug tracking
-  - GitHub — Repository and issue management
+- Gmail — Manage emails and drafts
+- Slack — Workspace notifications and alerts
+- Microsoft — Office 365 and Teams integration

-  #### Customer Relationship Management
-  - Salesforce — CRM account and opportunity management
-  - HubSpot — Sales pipeline and contact management
-  - Zendesk — Customer support ticket management
+#### Project Management

-  #### Business & Finance
-  - Stripe — Payment processing and customer management
-  - Shopify — E‑commerce store and product management
+- Jira — Issue tracking and project management
+- ClickUp — Task and productivity management
+- Asana — Team task and project coordination
+- Notion — Page and database management
+- Linear — Software project and bug tracking
+- GitHub — Repository and issue management

-  #### Productivity & Storage
-  - Google Sheets — Spreadsheet data synchronization
-  - Google Calendar — Event and schedule management
-  - Box — File storage and document management
+#### Customer Relationship Management

-  …and more to come!
+- Salesforce — CRM account and opportunity management
+- HubSpot — Sales pipeline and contact management
+- Zendesk — Customer support ticket management
+
+#### Business & Finance
+
+- Stripe — Payment processing and customer management
+- Shopify — E‑commerce store and product management
+
+#### Productivity & Storage
+
+- Google Sheets — Spreadsheet data synchronization
+- Google Calendar — Event and schedule management
+- Box — File storage and document management
+
+…and more to come!

  </Tab>
  <Tab title="Internal Tools" icon="toolbox">

-  ## Internal Tools
+## Internal Tools

-  Create custom tools locally, publish them on CrewAI AOP Tool Repository and use them in your agents.
+Create custom tools locally, publish them on CrewAI AMP Tool Repository and use them in your agents.

-  <Tip>
-  Before running the commands below, make sure you log in to your CrewAI AOP account by running this command:
-    ```bash
-    crewai login
-    ```
-  </Tip>
+{" "}
+<Tip>
+  Before running the commands below, make sure you log in to your CrewAI AMP
+  account by running this command: ```bash crewai login ```
+</Tip>

-  <Frame>
-    ![Internal Tool Detail](/images/enterprise/tools-integrations-internal.png)
-  </Frame>
+{" "}
+<Frame>
+  ![Internal Tool Detail](/images/enterprise/tools-integrations-internal.png)
+</Frame>

-  <Steps>
-    <Step title="Create">
-      Create a new tool locally.
-      ```bash
-      crewai tool create your-tool
-      ```
-    </Step>
-    <Step title="Publish">
-      Publish the tool to the CrewAI AOP Tool Repository.
-      ```bash
-      crewai tool publish
-      ```
-    </Step>
-    <Step title="Install">
-      Install the tool from the CrewAI AOP Tool Repository.
-      ```bash
-      crewai tool install your-tool
-      ```
-    </Step>
-  </Steps>
+{" "}
+<Steps>
+  <Step title="Create">
+    Create a new tool locally. ```bash crewai tool create your-tool ```
+  </Step>
+  <Step title="Publish">
+    Publish the tool to the CrewAI AMP Tool Repository. ```bash crewai tool
+    publish ```
+  </Step>
+  <Step title="Install">
+    Install the tool from the CrewAI AMP Tool Repository. ```bash crewai tool
+    install your-tool ```
+  </Step>
+</Steps>

-  Manage:
+Manage:

-  - Name and description
-  - Visibility (Private / Public)
-  - Required environment variables
-  - Version history and downloads
-  - Team and role access
+- Name and description
+- Visibility (Private / Public)
+- Required environment variables
+- Version history and downloads
+- Team and role access

-  <Frame>
-    ![Internal Tool Detail](/images/enterprise/tool-configs.png)
-  </Frame>
+{" "}
+<Frame>![Internal Tool Detail](/images/enterprise/tool-configs.png)</Frame>

  </Tab>
 </Tabs>
@@ -241,10 +245,18 @@ Tools & Integrations is the central hub for connecting third‑party apps and ma
 ## Related

 <CardGroup cols={2}>
-  <Card title="Tool Repository" href="/en/enterprise/guides/tool-repository#tool-repository" icon="toolbox">
+  <Card
+    title="Tool Repository"
+    href="/en/enterprise/guides/tool-repository#tool-repository"
+    icon="toolbox"
+  >
    Create, publish, and version custom tools for your organization.
  </Card>
-  <Card title="Webhook Automation" href="/en/enterprise/guides/webhook-automation" icon="bolt">
+  <Card
+    title="Webhook Automation"
+    href="/en/enterprise/guides/webhook-automation"
+    icon="bolt"
+  >
    Automate workflows and integrate with external platforms and services.
  </Card>
 </CardGroup>
--- a/docs/en/enterprise/features/traces.mdx
+++ b/docs/en/enterprise/features/traces.mdx
@@ -11,7 +11,7 @@ Traces provide comprehensive visibility into your crew executions, helping you m

 ## What are Traces?

-Traces in CrewAI AOP are detailed execution records that capture every aspect of your crew's operation, from initial inputs to final outputs. They record:
+Traces in CrewAI AMP are detailed execution records that capture every aspect of your crew's operation, from initial inputs to final outputs. They record:

 - Agent thoughts and reasoning
 - Task execution details
@@ -20,15 +20,13 @@ Traces in CrewAI AOP are detailed execution records that capture every aspect of
 - Execution times
 - Cost estimates

-<Frame>
-  ![Traces Overview](/images/enterprise/traces-overview.png)
-</Frame>
+<Frame>![Traces Overview](/images/enterprise/traces-overview.png)</Frame>

 ## Accessing Traces

 <Steps>
  <Step title="Navigate to the Traces Tab">
-    Once in your CrewAI AOP dashboard, click on the **Traces** to view all execution records.
+    Once in your CrewAI AMP dashboard, click on the **Traces** to view all execution records.
  </Step>

  <Step title="Select an Execution">
@@ -51,9 +49,7 @@ The top section displays high-level metrics about the execution:
 - **Execution Time**: Total duration of the crew run
 - **Estimated Cost**: Approximate cost based on token usage

-<Frame>
-  ![Execution Summary](/images/enterprise/trace-summary.png)
-</Frame>
+<Frame>![Execution Summary](/images/enterprise/trace-summary.png)</Frame>

 ### 2. Tasks & Agents

@@ -64,33 +60,25 @@ This section shows all tasks and agents that were part of the crew execution:
 - Status (completed/failed)
 - Individual execution time of the task

-<Frame>
-  ![Task List](/images/enterprise/trace-tasks.png)
-</Frame>
+<Frame>![Task List](/images/enterprise/trace-tasks.png)</Frame>

 ### 3. Final Output

 Displays the final result produced by the crew after all tasks are completed.

-<Frame>
-  ![Final Output](/images/enterprise/final-output.png)
-</Frame>
+<Frame>![Final Output](/images/enterprise/final-output.png)</Frame>

 ### 4. Execution Timeline

 A visual representation of when each task started and ended, helping you identify bottlenecks or parallel execution patterns.

-<Frame>
-  ![Execution Timeline](/images/enterprise/trace-timeline.png)
-</Frame>
+<Frame>![Execution Timeline](/images/enterprise/trace-timeline.png)</Frame>

 ### 5. Detailed Task View

 When you click on a specific task in the timeline or task list, you'll see:

-<Frame>
-  ![Detailed Task View](/images/enterprise/trace-detailed-task.png)
-</Frame>
+<Frame>![Detailed Task View](/images/enterprise/trace-detailed-task.png)</Frame>

 - **Task Key**: Unique identifier for the task
 - **Task ID**: Technical identifier in the system
@@ -104,7 +92,6 @@ When you click on a specific task in the timeline or task list, you'll see:
 - **Input**: Any input provided to this task from previous tasks
 - **Output**: The actual result produced by the agent

-
 ## Using Traces for Debugging

 Traces are invaluable for troubleshooting issues with your crews:
@@ -121,6 +108,7 @@ Traces are invaluable for troubleshooting issues with your crews:
    <Frame>
      ![Failure Points](/images/enterprise/failure.png)
    </Frame>
+
  </Step>

  <Step title="Optimize Performance">
@@ -130,6 +118,7 @@ Traces are invaluable for troubleshooting issues with your crews:
    - Excessive token usage
    - Redundant tool operations
    - Unnecessary API calls
+
  </Step>

  <Step title="Improve Cost Efficiency">
@@ -139,6 +128,7 @@ Traces are invaluable for troubleshooting issues with your crews:
    - Refine prompts to be more concise
    - Cache frequently accessed information
    - Structure tasks to minimize redundant operations
+
  </Step>
 </Steps>

@@ -153,5 +143,6 @@ CrewAI batches trace uploads to reduce overhead on high-volume runs:
 This yields more stable tracing under load while preserving detailed task/agent telemetry.

 <Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
-  Contact our support team for assistance with trace analysis or any other CrewAI AOP features.
+  Contact our support team for assistance with trace analysis or any other
+  CrewAI AMP features.
 </Card>
--- a/docs/en/enterprise/features/webhook-streaming.mdx
+++ b/docs/en/enterprise/features/webhook-streaming.mdx
@@ -8,7 +8,7 @@ mode: "wide"
 ## Overview

 Enterprise Event Streaming lets you receive real-time webhook updates about your crews and flows deployed to
-CrewAI AOP, such as model calls, tool usage, and flow steps.
+CrewAI AMP, such as model calls, tool usage, and flow steps.

 ## Usage

@@ -16,7 +16,7 @@ When using the Kickoff API, include a `webhooks` object to your request, for exa

 ```json
 {
-  "inputs": {"foo": "bar"},
+  "inputs": { "foo": "bar" },
  "webhooks": {
    "events": ["crew_kickoff_started", "llm_call_started"],
    "url": "https://your.endpoint/webhook",
@@ -46,8 +46,8 @@ Each webhook sends a list of events:
      "data": {
        "model": "gpt-4",
        "messages": [
-          {"role": "system", "content": "You are an assistant."},
-          {"role": "user", "content": "Summarize this article."}
+          { "role": "system", "content": "You are an assistant." },
+          { "role": "user", "content": "Summarize this article." }
        ]
      }
    }
@@ -65,104 +65,109 @@ CrewAI supports both system events and custom events in Enterprise Event Streami

 ### Flow Events:

-  - `flow_created`
-  - `flow_started`
-  - `flow_finished`
-  - `flow_plot`
-  - `method_execution_started`
-  - `method_execution_finished`
-  - `method_execution_failed`
+- `flow_created`
+- `flow_started`
+- `flow_finished`
+- `flow_plot`
+- `method_execution_started`
+- `method_execution_finished`
+- `method_execution_failed`

 ### Agent Events:

-  - `agent_execution_started`
-  - `agent_execution_completed`
-  - `agent_execution_error`
-  - `lite_agent_execution_started`
-  - `lite_agent_execution_completed`
-  - `lite_agent_execution_error`
-  - `agent_logs_started`
-  - `agent_logs_execution`
-  - `agent_evaluation_started`
-  - `agent_evaluation_completed`
-  - `agent_evaluation_failed`
+- `agent_execution_started`
+- `agent_execution_completed`
+- `agent_execution_error`
+- `lite_agent_execution_started`
+- `lite_agent_execution_completed`
+- `lite_agent_execution_error`
+- `agent_logs_started`
+- `agent_logs_execution`
+- `agent_evaluation_started`
+- `agent_evaluation_completed`
+- `agent_evaluation_failed`

 ### Crew Events:

-  - `crew_kickoff_started`
-  - `crew_kickoff_completed`
-  - `crew_kickoff_failed`
-  - `crew_train_started`
-  - `crew_train_completed`
-  - `crew_train_failed`
-  - `crew_test_started`
-  - `crew_test_completed`
-  - `crew_test_failed`
-  - `crew_test_result`
+- `crew_kickoff_started`
+- `crew_kickoff_completed`
+- `crew_kickoff_failed`
+- `crew_train_started`
+- `crew_train_completed`
+- `crew_train_failed`
+- `crew_test_started`
+- `crew_test_completed`
+- `crew_test_failed`
+- `crew_test_result`

 ### Task Events:

-  - `task_started`
-  - `task_completed`
-  - `task_failed`
-  - `task_evaluation`
+- `task_started`
+- `task_completed`
+- `task_failed`
+- `task_evaluation`

 ### Tool Usage Events:

-  - `tool_usage_started`
-  - `tool_usage_finished`
-  - `tool_usage_error`
-  - `tool_validate_input_error`
-  - `tool_selection_error`
-  - `tool_execution_error`
+- `tool_usage_started`
+- `tool_usage_finished`
+- `tool_usage_error`
+- `tool_validate_input_error`
+- `tool_selection_error`
+- `tool_execution_error`

 ### LLM Events:

-  - `llm_call_started`
-  - `llm_call_completed`
-  - `llm_call_failed`
-  - `llm_stream_chunk`
+- `llm_call_started`
+- `llm_call_completed`
+- `llm_call_failed`
+- `llm_stream_chunk`

 ### LLM Guardrail Events:

-  - `llm_guardrail_started`
-  - `llm_guardrail_completed`
+- `llm_guardrail_started`
+- `llm_guardrail_completed`

 ### Memory Events:

-  - `memory_query_started`
-  - `memory_query_completed`
-  - `memory_query_failed`
-  - `memory_save_started`
-  - `memory_save_completed`
-  - `memory_save_failed`
-  - `memory_retrieval_started`
-  - `memory_retrieval_completed`
+- `memory_query_started`
+- `memory_query_completed`
+- `memory_query_failed`
+- `memory_save_started`
+- `memory_save_completed`
+- `memory_save_failed`
+- `memory_retrieval_started`
+- `memory_retrieval_completed`

 ### Knowledge Events:

-  - `knowledge_search_query_started`
-  - `knowledge_search_query_completed`
-  - `knowledge_search_query_failed`
-  - `knowledge_query_started`
-  - `knowledge_query_completed`
-  - `knowledge_query_failed`
+- `knowledge_search_query_started`
+- `knowledge_search_query_completed`
+- `knowledge_search_query_failed`
+- `knowledge_query_started`
+- `knowledge_query_completed`
+- `knowledge_query_failed`

 ### Reasoning Events:

-  - `agent_reasoning_started`
-  - `agent_reasoning_completed`
-  - `agent_reasoning_failed`
+- `agent_reasoning_started`
+- `agent_reasoning_completed`
+- `agent_reasoning_failed`

 Event names match the internal event bus. See GitHub for the full list of events.

 You can emit your own custom events, and they will be delivered through the webhook stream alongside system events.

 <CardGroup>
- <Card title="GitHub" icon="github" href="https://github.com/crewAIInc/crewAI/tree/main/src/crewai/utilities/events">
-  Full list of events
- </Card>
-<Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
-  Contact our support team for assistance with webhook integration or troubleshooting.
-</Card>
+  <Card
+    title="GitHub"
+    icon="github"
+    href="https://github.com/crewAIInc/crewAI/tree/main/src/crewai/utilities/events"
+  >
+    Full list of events
+  </Card>
+  <Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
+    Contact our support team for assistance with webhook integration or
+    troubleshooting.
+  </Card>
 </CardGroup>