fix: OpenTelemetry logs and traces showing proper crew names

[renatonitta]

Summary

This PR fixes OpenTelemetry logs and traces showing crew_name: "crew" for every unnamed automation, making it impossible to tell which automation ran. Root cause: Crew.name defaulted to the literal string "crew", which propagated to every downstream event.

The default is now None, resolved at construction time via a model_validator that falls back to the class name, matching Flow's existing pattern.

Changes

• Crew.name defaults to None instead of the literal "crew".
• _resolve_name model validator (mode="after") fills in the class name when no explicit name is provided.
• @crew decorator propagates the @CrewBase class name to the returned Crew instance, preserving any explicit Crew(name=...) set inside the factory method.

Behavior

Construction	Before	After
Crew(name="My Automation", ...)	crew	My Automation
class MyCrew(Crew) → MyCrew(...)	crew	MyCrew
@CrewBase class ResearchCrew: @crew def crew(self):	crew	ResearchCrew
Crew(...) (bare, no name)	crew	Crew

---

Note

Medium Risk
Changes Crew.name defaulting and propagation logic, which affects event payloads, memory scoping namespaces, and OpenTelemetry trace metadata for all crews. Risk is moderate due to behavior changes in identifiers that may impact downstream logging/metrics expectations.

Overview
Unnamed Crew instances no longer default to the literal string "crew"; Crew.name now defaults to None and is resolved post-init to the concrete class name via a new _resolve_name model validator while tracking whether the user explicitly set name.

Telemetry and UI surfaces now use this resolved name: kickoff/training/testing events emit the resolved crew_name, checkpoint resume panels cast crew.name as non-null, and the tracing listener treats missing/empty crew names as "Unknown Crew" instead of accepting falsy values.

The @crew factory decorator now propagates the @CrewBase class name onto the returned Crew instance only when name was not explicitly provided, and tests were updated/added to lock in these naming semantics (plus a small uv.lock timestamp change).

^{Reviewed by Cursor Bugbot for commit 6a41e6f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[linear]

CON-109 OpenTelemety Logs and Traces are not providing correct crew/automation name

[greysonlalonde]

Rather than adding new property logic, can we stick this in a @model_validator to keep from adding new attrs? Something like:

@model_validator(mode="after")                                                                                                                       
def _resolve_name(self) -> Self:                                                                                                                     
    if self.name is None:                                                                                                                            
        self.name = type(self).__name__
    return self  

Then we can keep the same .name accessor throughout files.

The decorator would need to unconditionally assign the name like so:

crew_instance.name = getattr(self, "_crew_name", None) or crew_instance.name

[renatonitta]

done

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 6a41e6f. Configure here.}

[cursor]

Validator doesn't fallback when name is explicitly None

Low Severity

The _resolve_name validator uses "name" in self.model_fields_set to decide whether to apply the class-name fallback. When a user explicitly passes Crew(name=None), Pydantic includes "name" in model_fields_set, so _name_was_explicit becomes True and the fallback is skipped—leaving name as None. This breaks the "guaranteed non-None" invariant that downstream cast(str, self.name) calls rely on. The fallback condition needs to check self.name is None rather than not self._name_was_explicit, while keeping _name_was_explicit based on model_fields_set for the decorator's separate concern.

Additional Locations (2)

• lib/crewai/src/crewai/crew.py#L594-L596
• lib/crewai/src/crewai/crews/utils.py#L311-L315

 

^{Reviewed by Cursor Bugbot for commit 6a41e6f. Configure here.}

[renatonitta]

Closing this in favor of #5574