Issue Station
Sign In
Tools hereToolbox

crewai - ✅(Solved) Fix [BUG] I can not stop the "Info: Tracing is disabled." nagging. [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
crewAIInc/crewAI#5665•Fetched 2026-05-01 05:41:52
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
TByte007TByte007
Participants
TByte007TByte007
Timeline (top)
cross-referenced ×1labeled ×1

There is no stopping of this. Is this spam on purpose or a bug?

Info: Tracing is disabled.

To enable tracing, do any one of these: • Set tracing=True in your Crew code • Set CREWAI_TRACING_ENABLED=true in your project's .env file • Run: crewai traces enable

What is the point of this ? https://github.com/crewAIInc/crewAI/blob/c7f01048b77b2600298ab2f776334034736c4d81/lib/crewai/src/crewai/crew.py#L2277

What if I don't want to even see the message?

if has_user_declined_tracing():
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""
        else:
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""

Both print the same message ? Why ? Am I missing something ?

Root Cause

There is no stopping of this. Is this spam on purpose or a bug?

Info: Tracing is disabled.

To enable tracing, do any one of these: • Set tracing=True in your Crew code • Set CREWAI_TRACING_ENABLED=true in your project's .env file • Run: crewai traces enable

What is the point of this ? https://github.com/crewAIInc/crewAI/blob/c7f01048b77b2600298ab2f776334034736c4d81/lib/crewai/src/crewai/crew.py#L2277

What if I don't want to even see the message?

if has_user_declined_tracing():
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""
        else:
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""

Both print the same message ? Why ? Am I missing something ?

Fix Action

Fixed

PR fix notes

PR #5666: Fix #5665: Stop nagging users who declined tracing with repeated messages

Description (problem / solution / changelog)

Summary

Fixes #5665 — Users who have explicitly declined tracing are still shown the "Info: Tracing is disabled" panel on every crew/flow execution, with no way to suppress it.

Root causes fixed:

  1. All four _show_tracing_disabled_message implementations had identical if has_user_declined_tracing() / else branches — both showed the exact same message, making the conditional pointless.
  2. Users who explicitly declined tracing were still nagged every time.
  3. There was no environment variable to suppress the message.

Changes:

  • When has_user_declined_tracing() returns True, the message is now skipped entirely (in crew.py, flow.py, trace_listener.py, and console_formatter.py).
  • should_suppress_tracing_messages() now also checks the CREWAI_SUPPRESS_TRACING_MESSAGES environment variable (true/1/yes), giving users an additional way to silence the message.
  • Removed the duplicate identical if/else branches, keeping only the single message for the case when the user hasn't decided yet.

Review & Testing Checklist for Human

  • Verify that running a Crew with tracing declined (trace_consent: false in user data) no longer prints the tracing panel
  • Verify that setting CREWAI_SUPPRESS_TRACING_MESSAGES=true suppresses the message even for new users
  • Verify that the message still appears for users who haven't explicitly declined (default behavior preserved)

Notes

  • The uv.lock diff is from regenerating the lockfile (the existing one had a parse error); the actual code changes are minimal and scoped to the tracing message logic.

Link to Devin session: https://app.devin.ai/sessions/6e8d08df06184175acc80d251b4915d4

Changed files

  • lib/crewai/src/crewai/crew.py (modified, +5/-9)
  • lib/crewai/src/crewai/events/listeners/tracing/trace_listener.py (modified, +5/-9)
  • lib/crewai/src/crewai/events/listeners/tracing/utils.py (modified, +10/-1)
  • lib/crewai/src/crewai/events/utils/console_formatter.py (modified, +5/-9)
  • lib/crewai/src/crewai/flow/flow.py (modified, +5/-9)
  • lib/crewai/tests/tracing/test_tracing_message_suppression.py (added, +259/-0)

Code Example

if has_user_declined_tracing():
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""
        else:
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""
RAW_BUFFERClick to expand / collapse

Description

There is no stopping of this. Is this spam on purpose or a bug?

Info: Tracing is disabled.

To enable tracing, do any one of these: • Set tracing=True in your Crew code • Set CREWAI_TRACING_ENABLED=true in your project's .env file • Run: crewai traces enable

What is the point of this ? https://github.com/crewAIInc/crewAI/blob/c7f01048b77b2600298ab2f776334034736c4d81/lib/crewai/src/crewai/crew.py#L2277

What if I don't want to even see the message?

if has_user_declined_tracing():
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""
        else:
            message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""

Both print the same message ? Why ? Am I missing something ?

Steps to Reproduce

Just run CrewAI with tracing disabled.

Expected behavior

Not to be nagged about it 100 times.

Screenshots/Code snippets

if has_user_declined_tracing(): message = """Info: Tracing is disabled.

To enable tracing, do any one of these: • Set tracing=True in your Crew code • Set CREWAI_TRACING_ENABLED=true in your project's .env file • Run: crewai traces enable""" else: message = """Info: Tracing is disabled.

To enable tracing, do any one of these: • Set tracing=True in your Crew code • Set CREWAI_TRACING_ENABLED=true in your project's .env file • Run: crewai traces enable"""

Operating System

Ubuntu 24.04

Python Version

3.12

crewAI Version

1.14.3

crewAI Tools Version

1.14.3

Virtual Environment

Venv

Evidence

100 times <img width="550" height="170" alt="Image" src="https://github.com/user-attachments/assets/9231f138-51db-4488-a45f-85ef1ea736bf" />

Possible Solution

Make it stop printing it with some env variable .

Additional context

No

extent analysis

TL;DR

Disable the tracing message by setting an environment variable or modifying the code to handle the has_user_declined_tracing() condition differently.

Guidance

  • Review the code snippet provided and notice that both conditions (if has_user_declined_tracing() and else) print the same message, which might be the cause of the repetitive tracing message.
  • Consider setting an environment variable, such as CREWAI_SUPPRESS_TRACING_MESSAGE, to control the printing of the tracing message.
  • Modify the code to handle the has_user_declined_tracing() condition differently, for example, by printing a different message or no message at all.
  • Investigate the has_user_declined_tracing() function to understand its logic and how it affects the printing of the tracing message.

Example

if has_user_declined_tracing():
    # Print a different message or no message at all
    message = "Tracing is disabled by user."
else:
    message = """Info: Tracing is disabled.

To enable tracing, do any one of these:
• Set tracing=True in your Crew code
• Set CREWAI_TRACING_ENABLED=true in your project's .env file
• Run: crewai traces enable"""

Notes

The provided code snippet and issue description suggest that the repetitive tracing message is caused by the identical messages printed in both conditions. However, without more context or information about the has_user_declined_tracing() function, it is difficult to provide a definitive solution.

Recommendation

Apply a workaround by modifying the code to handle the has_user_declined_tracing() condition differently, as this seems to be the most straightforward approach to disable the repetitive tracing message.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Not to be nagged about it 100 times.

#GPU setup#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING