[BUG] the verbose information of flow could not be disabled

[w6m6]

Description

How could i disable the verbose information of flow? it seed that there is no verbose para for flow.

╭───────────────────────────────────── Flow Execution ─────────────────────────────────────╮
│ │
│ Starting Flow Execution │
│ Name: GuideCreatorFlow │
│ ID: 27cfce60-1762-4fdd-bd0f-9e66d0f3f259 │
│ Tool Args: │
│ │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────╯

Steps to Reproduce

when using flow.

Expected behavior

the verbose of flow could be disabled.

Screenshots/Code snippets

def print_panel(
self, content: Text, title: str, style: str = "blue", is_flow: bool = False
) -> None:
"""Print a panel with consistent formatting if verbose is enabled."""
panel = self.create_panel(content, title, style)
if is_flow:
self.print(panel)
self.print()
else:
if self.verbose:
self.print(panel)

Operating System

Ubuntu 24.04

Python Version

3.10

crewAI Version

1.20.1

crewAI Tools Version

1.20.1

Virtual Environment

Venv

Evidence

N/A

Possible Solution

set up a env variable.

Additional context

crewai/events/utils/console_formatter.py

def print_panel(
self, content: Text, title: str, style: str = "blue", is_flow: bool = False
) -> None:
"""Print a panel with consistent formatting if verbose is enabled."""
panel = self.create_panel(content, title, style)
if is_flow:
self.print(panel)
self.print()
else:
if self.verbose:
self.print(panel)

[Goldokpa]

Hi maintainers , I’d like to take this bug.

Summary

Flow output shows verbose panels/logs even when users expect it to be fully silent. This stems from flow‑level printing/logging not being gated by a Flow‑scoped verbosity flag, and certain printing paths bypassing any verbosity guard.

Root cause (from code)

• crewai/flow/flow.py::_log_flow_event prints and logs unconditionally (prints via self._printer.print(...) and logs info + warning regardless), so disabling verbosity isn’t possible at Flow level.
• The console panel path referenced by the reporter (crewai/events/utils/console_formatter.py::print_panel) treats is_flow=True as always-print, effectively bypassing a verbosity check.

Proposed fix

• Add verbose: bool = False to Flow and accept it via __init__. This mirrors how Agent wires verbosity into its logger.
• Gate _log_flow_event so both console prints and log lines occur only when self.verbose is True. Remove the unconditional warning to avoid duplicate/noisy logs.
• Ensure any flow-specific console panel printing respects Flow.verbose even when is_flow=True. Panels print only if self.verbose is True.
• Keep persistence decorator behavior unchanged: @persist(..., verbose=True) should still produce its own logs, independent of flow verbosity (as tested in the repo). Document the interplay so users can choose granularly.

Test plan

• Add tests asserting:
  • No flow logs/panels when Flow(verbose=False).
  • Logs/panels appear when Flow(verbose=True).
  • Persistence decorator logs only when @persist(..., verbose=True) is used, independent of flow verbosity.
• Use caplog and capture console output where applicable. Extend lib/crewai/tests/test_flow_persistence.py (there’s already coverage of persist(verbose=...)) and/or add a focused tests/flow/test_flow_verbose.py.

Docs

• Update docs/en/guides/flows/mastering-flow-state.mdx to document:
  • Flow(verbose=...) behavior
  • Interaction with @persist(..., verbose=...)
  • Distinction from tracing=True (which should remain orthogonal to console verbosity)

Backwards compatibility

• Default remains non-verbose. Users depending on current prints can set verbose=True explicitly. Persistence decorator logging is unchanged and opt-in via its own flag.

Logistics

• Branch: fix/flow-verbosity-control
• ETA: 2–3 days for code + tests + docs

Optional for future implementation

• Consider an env var like CREWAI_FLOW_VERBOSE=true/false to set a default verbosity globally, but I’ll keep scope minimal in this PR unless requested.

Please let me know if you have a preferred flag name or want the env var included in this fix. thank you

[lorenzejay]

that would be a good issue to pick up! go for it @Goldokpa thanks for taking this one and slooks like a solid plan

[Goldokpa]

thank you mate @lorenzejay i'm glad to work on this, cheers!!

[Goldokpa]

I'll provide a PR in 2-3 days and I'll keep it mostly focused on the core verbosity control and skip the env var for now unless you'd like me to include it.