Joao MouraandClaude Opus 5.5 9226eee072 fix(cli): say where the trace goes only when the yes is inferred from crewai eval ...

The note, in the run app ("This run will be evaluated: its trace is sent to
CrewAI AMP, which grades it.") and in `crewai eval`'s line, is for the case
where nobody turned tracing on: not `tracing=True` on the crew or flow, not
`CREWAI_TRACING_ENABLED=true`, not a consent a person gave once
(`crewai_core.user_data.is_tracing_enabled`), and not the yes they just gave to
turn it on. A project or a person who opted in is told nothing new.

The run `crewai eval` starts no longer sets `CREWAI_TRACING_ENABLED=true`:
the handshake alone turns tracing on for it, so the setting a run reads is the
project's own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-18 23:07:51 -07:00

..

cli

fix(cli): say where the trace goes only when the yes is inferred from crewai eval

2026-10-18 23:07:51 -07:00

crewai

fix(tracing): the telemetry opt-out no longer turns tracing off; an evaluated run says where its trace goes

2026-10-18 23:07:51 -07:00

crewai-core

feat(cli): crewai eval runs the crew itself, so a coding agent gets a verdict from one command

2026-10-18 23:07:50 -07:00

crewai-files

fix: resolve pip-audit dependency findings (#8221)

2026-10-16 09:14:52 +00:00

crewai-tools

fix: resolve pip-audit dependency findings (#8221)

2026-10-16 09:14:52 +00:00

devtools

feat: bump versions to 1.15.28 (#8146)

2026-10-14 01:42:13 -03:00