Fetching from the wire…
01
02
03
04
05
06
07
08
Agents2026-08-12 · source-backed
Ships flow outcome, duration and human-in-the-loop signals as first-class telemetry rather than something you reconstruct from spans, and fixes a real gap where FlowStartedEvent wasn't emitted when a boundary hook aborted the flow, meaning aborted runs were invisible to listeners (GitHub). It now scopes span export to CrewAI's own tracer provider instead of the global one. Security bumps to torch 2.13.0 and gitpython 3.1.58. CLI flags moved to kebab-case, which is a breaking change if you script it.
Each link below shares sources, entities, or timing with this story.
LangGraph benchmarked against CrewAI / Shared entity: CrewAI / Same source domain / Earlier coverage
Linked by a graph relationship (LangGraph benchmarked against CrewAI); both cover CrewAI; reported by the same outlet (github.com).
CrewAI supports MCP / Shared entity: OpenTelemetry / Same source domain / Earlier coverage
Linked by a graph relationship (CrewAI supports MCP); both cover OpenTelemetry; reported by the same outlet (github.com).
CrewAI supports MCP / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (CrewAI supports MCP); both cover CLI, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (CrewAI supports MCP); both cover CLI, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (CrewAI supports MCP); both cover CLI, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (CrewAI supports MCP); both cover GitHub, Ships; reported by the same outlet (github.com).
Linked by a graph relationship (CrewAI supports MCP); both cover CLI, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (CrewAI supports MCP); both cover GitHub, Ships; reported by the same outlet (github.com).