crewAIInc · Vidit-Ostwal · Sep 7, 2026 · coderabbitai · Sep 7, 2026 · coderabbitai
diff --git a/docs/edge/ar/concepts/cli.mdx b/docs/edge/ar/concepts/cli.mdx
@@ -286,6 +286,7 @@ crewai traces [COMMAND]
    ```shell Terminal
    crewai traces enable
    ```
+   - يحدّث موجه التشغيل الأول (`Would you like to view your execution traces?`) هذا التفضيل أيضاً
 
 <Note>
 **لتفعيل التتبع**، استخدم أيًا من هذه الطرق:

diff --git a/docs/edge/ar/observability/tracing.mdx b/docs/edge/ar/observability/tracing.mdx
@@ -9,7 +9,7 @@ mode: "wide"
 
 يوفر CrewAI إمكانيات تتبع مدمجة تتيح لك مراقبة وتصحيح أخطاء الطواقم والتدفقات في الوقت الفعلي. يوضح هذا الدليل كيفية تفعيل التتبع لكل من **الطواقم** و**التدفقات** باستخدام منصة المراقبة المتكاملة في CrewAI.
 
-> **ما هو تتبع CrewAI؟** يوفر التتبع المدمج في CrewAI مراقبة شاملة لوكلاء الذكاء الاصطناعي، بما في ذلك قرارات الوكلاء وجداول تنفيذ المهام واستخدام الأدوات واستدعاءات LLM - كل ذلك متاح عبر [منصة CrewAI AMP](https://app.crewai.com).
+> **ما هو تتبع CrewAI؟** يوفر التتبع المدمج في CrewAI مراقبة شاملة لوكلاء الذكاء الاصطناعي، بما في ذلك قرارات الوكلاء وجداول تنفيذ المهام واستخدام الأدوات واستدعاءات LLM - كل ذلك متاح عبر [منصة CrewAI AMP](https://app.crewai.com). يتم إدارة التتبع بشكل مستقل عن [القياس عن بُعد](/ar/telemetry).
 
 ![واجهة تتبع CrewAI](/images/crewai-tracing.png)
 
@@ -170,6 +170,18 @@ CREWAI_TRACING_ENABLED=true
 
 عند تعيين متغير البيئة هذا، ستُفعّل جميع الطواقم والتدفقات التتبع تلقائياً، حتى بدون تعيين `tracing=True` صراحةً.
 
+## عرض التتبعات بعد أول تشغيل
+
+في المرة الأولى التي تشغّل فيها طاقماً أو تدفقاً، قد يسألك طرف تفاعلي:
+
+```text
+Would you like to view your execution traces? [y/N]
+```
+
+اختر **yes** لفتح رابط العرض. يمكنك تغيير ذلك لاحقاً باستخدام
+`crewai traces enable` أو `crewai traces disable`، أو بتعيين `tracing`
+على الطاقم أو التدفق.
+
 ## عرض التتبعات
 
 ### الوصول إلى لوحة تحكم CrewAI AMP

diff --git a/docs/edge/ar/telemetry.mdx b/docs/edge/ar/telemetry.mdx
@@ -24,6 +24,7 @@ mode: "wide"
 لتوفير رؤى أعمق. قد يتضمن جمع البيانات الموسع هذا معلومات شخصية إذا دمجها المستخدمون في طواقمهم أو مهامهم.
 يجب على المستخدمين النظر بعناية في محتوى طواقمهم ومهامهم قبل تفعيل `share_crew`.
 يمكن للمستخدمين تعطيل القياس عن بُعد في CrewAI عبر تعيين `CREWAI_DISABLE_TELEMETRY` إلى `true` أو `1` أو `yes` أو `on` (بغض النظر عن حالة الأحرف). `OTEL_SDK_DISABLED` بنفس القيم يعطّل أيضاً مُصدِّر CrewAI. مجموعة أدوات OpenTelemetry نفسها ما تزال تقبل `true` فقط لتعطيل بقية أدوات القياس في العملية.
+تتبع AMP مشمول بشكل منفصل في [التتبع](/ar/observability/tracing).
 
 ### أمثلة:
 ```python

diff --git a/docs/edge/en/concepts/cli.mdx b/docs/edge/en/concepts/cli.mdx
@@ -578,6 +578,7 @@ Trace collection is controlled by checking three settings in priority order:
    ```
    - Checked only if `tracing` is not set in code and `CREWAI_TRACING_ENABLED` is not set to `true`
    - Running `crewai traces enable` is sufficient to enable tracing by itself
+   - The first-run prompt (`Would you like to view your execution traces?`) also updates this preference
 
 <Note>
 **To enable tracing**, use any one of these methods:

diff --git a/docs/edge/en/concepts/crews.mdx b/docs/edge/en/concepts/crews.mdx
@@ -37,7 +37,7 @@ A crew in crewAI represents a collaborative group of agents working together to
 | **Chat LLM** _(optional)_                      | `chat_llm`                    | The language model used to orchestrate `crewai chat` CLI interactions with the crew. Accepts a model name string or `LLM` instance. Defaults to `None`.                                                                                                    |
 | **Before Kickoff Callbacks** _(optional)_      | `before_kickoff_callbacks`    | A list of callable functions executed **before** the crew starts. Each callback receives and can modify the inputs dict. Distinct from the `@before_kickoff` decorator. Defaults to `[]`.                                                                   |
 | **After Kickoff Callbacks** _(optional)_       | `after_kickoff_callbacks`     | A list of callable functions executed **after** the crew finishes. Each callback receives and can modify the `CrewOutput`. Distinct from the `@after_kickoff` decorator. Defaults to `[]`.                                                                  |
-| **Tracing** _(optional)_                       | `tracing`                     | Controls OpenTelemetry tracing for the crew. `True` = always enable, `False` = always disable, `None` = inherit from environment / user settings. Defaults to `None`.                                                                                      |
+| **Tracing** _(optional)_                       | `tracing`                     | Controls tracing for the crew. `True` = always enable, `False` = always disable, `None` = inherit from environment / user settings. Defaults to `None`.                                                                                      |
 | **Skills** _(optional)_                        | `skills`                      | A list of `Path` objects (skill search directories) or pre-loaded `Skill` objects applied to all agents in the crew. Defaults to `None`.                                                                                                                    |
 | **Security Config** _(optional)_               | `security_config`              | A `SecurityConfig` instance managing crew fingerprinting and identity. Defaults to `SecurityConfig()`.                                                                                                                                                      |
 | **Checkpoint** _(optional)_                    | `checkpoint`                  | Enables automatic checkpointing. Pass `True` for sensible defaults, a `CheckpointConfig` for full control, `False` to opt out, or `None` to inherit. See the [Checkpointing](#checkpointing) section below. Defaults to `None`.                             |

diff --git a/docs/edge/en/observability/tracing.mdx b/docs/edge/en/observability/tracing.mdx
@@ -9,7 +9,7 @@ mode: "wide"
 
 CrewAI provides built-in tracing capabilities that allow you to monitor and debug your Crews and Flows in real-time. This guide demonstrates how to enable tracing for both **Crews** and **Flows** using CrewAI's integrated observability platform.
 
-> **What is CrewAI Tracing?** CrewAI's built-in tracing provides comprehensive observability for your AI agents, including agent decisions, task execution timelines, tool usage, and LLM calls - all accessible through the [CrewAI AMP platform](https://app.crewai.com).
+> **What is CrewAI Tracing?** CrewAI's built-in tracing provides comprehensive observability for your AI agents, including agent decisions, task execution timelines, tool usage, and LLM calls - all accessible through the [CrewAI AMP platform](https://app.crewai.com). Tracing is managed independently from [telemetry](/en/telemetry).
 
 ![CrewAI Tracing Interface](/images/crewai-tracing.png)
 
@@ -170,6 +170,18 @@ CREWAI_TRACING_ENABLED=true
 
 When this environment variable is set, all Crews and Flows will automatically have tracing enabled, even without explicitly setting `tracing=True`.
 
+## Viewing traces after your first run
+
+The first time you run a Crew or Flow, an interactive terminal may ask:
+
+```text
+Would you like to view your execution traces? [y/N]
+```
+
+Choose **yes** to open a view link. You can change this later with
+`crewai traces enable` or `crewai traces disable`, or by setting `tracing`
+on the Crew or Flow.
+
 ## Viewing Your Traces
 
 ### Access the CrewAI AMP Dashboard

diff --git a/docs/edge/en/telemetry.mdx b/docs/edge/en/telemetry.mdx
@@ -24,6 +24,7 @@ When the `share_crew` feature is enabled, detailed data including task descripti
 to provide deeper insights. This expanded data collection may include personal information if users have incorporated it into their crews or tasks. 
 Users should carefully consider the content of their crews and tasks before enabling `share_crew`. 
 Users can disable CrewAI telemetry by setting `CREWAI_DISABLE_TELEMETRY` to `true`, `1`, `yes`, or `on` (any case). `OTEL_SDK_DISABLED` with the same values also disables CrewAI's exporter. The OpenTelemetry SDK itself still only honors `true` for disabling other instrumentation in the process.
+AMP tracing is covered separately in [Tracing](/en/observability/tracing).
 
 ### Examples:
 ```python

diff --git a/docs/edge/ko/observability/tracing.mdx b/docs/edge/ko/observability/tracing.mdx
@@ -9,7 +9,7 @@ mode: "wide"
 
 CrewAI는 Crews와 Flows를 실시간으로 모니터링하고 디버깅할 수 있는 내장 추적 기능을 제공합니다. 이 가이드는 CrewAI의 통합 관측 가능성 플랫폼을 사용하여 **Crews**와 **Flows** 모두에 대한 추적을 활성화하는 방법을 보여줍니다.
 
-> **CrewAI Tracing이란?** CrewAI의 내장 추적은 agent 결정, 작업 실행 타임라인, 도구 사용, LLM 호출을 포함한 AI agent에 대한 포괄적인 관측 가능성을 제공하며, 모두 [CrewAI AMP 플랫폼](https://app.crewai.com)을 통해 액세스할 수 있습니다.
+> **CrewAI Tracing이란?** CrewAI의 내장 추적은 agent 결정, 작업 실행 타임라인, 도구 사용, LLM 호출을 포함한 AI agent에 대한 포괄적인 관측 가능성을 제공하며, 모두 [CrewAI AMP 플랫폼](https://app.crewai.com)을 통해 액세스할 수 있습니다. 추적은 [텔레메트리](/ko/telemetry)와 별도로 관리됩니다.
 
 ![CrewAI Tracing Interface](/images/crewai-tracing.png)
 
@@ -170,6 +170,17 @@ CREWAI_TRACING_ENABLED=true
 
 이 환경 변수가 설정되면 `tracing=True`를 명시적으로 설정하지 않아도 모든 Crews와 Flows에 자동으로 추적이 활성화됩니다.
 
+## 첫 실행 후 추적 보기
+
+Crew 또는 Flow를 처음 실행하면 대화형 터미널에서 다음을 물을 수 있습니다:
+
+```text
+Would you like to view your execution traces? [y/N]
+```
+
+보기 링크를 열려면 **yes**를 선택하세요. 나중에 `crewai traces enable` 또는
+`crewai traces disable`로 바꾸거나, Crew 또는 Flow에서 `tracing`을 설정할 수 있습니다.
+
 ## 추적 보기
 
 ### CrewAI AMP 대시보드 액세스

diff --git a/docs/edge/ko/telemetry.mdx b/docs/edge/ko/telemetry.mdx
@@ -23,6 +23,7 @@ CrewAI는 익명 텔레메트리를 활용하여 사용 통계를 수집하며,
 이 확대된 데이터 수집에는 사용자가 crew나 작업에 개인정보를 포함한 경우, 개인정보가 포함될 수 있습니다.
 사용자는 `share_crew`를 활성화하기 전에 crew와 작업의 내용을 신중하게 검토해야 합니다.
 사용자는 `CREWAI_DISABLE_TELEMETRY`를 `true`, `1`, `yes`, `on` 중 하나로 설정하여 CrewAI 텔레메트리를 비활성화할 수 있습니다(대소문자 무관). 같은 값의 `OTEL_SDK_DISABLED`도 CrewAI exporter를 끕니다. 프로세스 내 다른 OpenTelemetry 계측을 끄려면 OpenTelemetry SDK는 여전히 `true`만 인식합니다.
+AMP 추적은 [Tracing](/ko/observability/tracing)에서 별도로 다룹니다.
 
 ### 예시:
 ```python

diff --git a/docs/edge/pt-BR/observability/tracing.mdx b/docs/edge/pt-BR/observability/tracing.mdx
@@ -9,7 +9,7 @@ mode: "wide"
 
 O CrewAI fornece recursos de rastreamento integrados que permitem monitorar e depurar seus Crews e Flows em tempo real. Este guia demonstra como habilitar o rastreamento para **Crews** e **Flows** usando a plataforma de observabilidade integrada do CrewAI.
 
-> **O que é o CrewAI Tracing?** O rastreamento integrado do CrewAI fornece observabilidade abrangente para seus agentes de IA, incluindo decisões de agentes, cronogramas de execução de tarefas, uso de ferramentas e chamadas de LLM - tudo acessível através da [plataforma CrewAI AMP](https://app.crewai.com).
+> **O que é o CrewAI Tracing?** O rastreamento integrado do CrewAI fornece observabilidade abrangente para seus agentes de IA, incluindo decisões de agentes, cronogramas de execução de tarefas, uso de ferramentas e chamadas de LLM - tudo acessível através da [plataforma CrewAI AMP](https://app.crewai.com). O rastreamento é gerenciado de forma independente da [telemetria](/pt-BR/telemetry).
 
 ![CrewAI Tracing Interface](/images/crewai-tracing.png)
 
@@ -170,6 +170,18 @@ CREWAI_TRACING_ENABLED=true
 
 Quando esta variável de ambiente estiver definida, todos os Crews e Flows terão automaticamente o rastreamento habilitado, mesmo sem definir explicitamente `tracing=True`.
 
+## Visualizando rastreamentos após a primeira execução
+
+Na primeira vez que você executa um Crew ou Flow, um terminal interativo pode perguntar:
+
+```text
+Would you like to view your execution traces? [y/N]
+```
+
+Escolha **yes** para abrir um link de visualização. Você pode alterar isso depois com
+`crewai traces enable` ou `crewai traces disable`, ou definindo `tracing`
+no Crew ou Flow.
+
 ## Visualizando seus Rastreamentos
 
 ### Acesse o Painel CrewAI AMP

diff --git a/docs/edge/pt-BR/telemetry.mdx b/docs/edge/pt-BR/telemetry.mdx
@@ -24,6 +24,7 @@ Quando o recurso `share_crew` está ativado, dados detalhados, incluindo descri
 para fornecer insights mais detalhados. Essa coleta expandida pode incluir informações pessoais caso o usuário as tenha inserido em seus crews ou tarefas.
 Usuários devem considerar cuidadosamente o conteúdo de seus crews e tarefas antes de habilitar o `share_crew`.
 A telemetria do CrewAI pode ser desabilitada ao definir `CREWAI_DISABLE_TELEMETRY` como `true`, `1`, `yes` ou `on` (qualquer capitalização). `OTEL_SDK_DISABLED` com os mesmos valores também desabilita o exportador do CrewAI. O SDK do OpenTelemetry em si ainda só reconhece `true` para desabilitar as demais instrumentações do processo.
+O rastreamento AMP é tratado em [Tracing](/pt-BR/observability/tracing).
 
 ### Exemplos:
 ```python