CrewAI 多智能体框架

WHENWhen constructing a Crew with 5 or more sequential tasks and verbose intermediate outputs

ACTIONAlways set task.context = [task1, task2, ...] explicitly to declare which prior outputs are needed, OR install a task callback that summarizes raw output before the next task consumes it. Do not rely on the default aggregation path for chains beyond ~4 tasks. Verify by inspecting agent prompt token counts at the boundary task.

CONSEQUENCEundefined behavior

WHENWhen configuring an Agent with 2 or more tools where the model could plausibly toggle between them

ACTIONOn every tool instance reachable by an agent with >=2 tools, set max_usage_count to a budget you can afford (e.g. 5-10 per kickoff). Additionally hook step_callback to maintain a per-tool counter and abort the loop when an A→B→A pattern persists for >=2 cycles. Do NOT rely on _check_tool_repeated_usage to catch oscillation.

CONSEQUENCEundefined behavior

WHENWhen deploying any application that imports crewai in an environment with privacy / compliance / GDPR / SOC2 / data-residency requirements

ACTIONSet CREWAI_DISABLE_TELEMETRY=true (or one of the equivalents) BEFORE any process imports crewai — set it in .env, docker-compose, Kubernetes manifests, CI workflows, and developer onboarding scripts. Do NOT rely on assuming SDK frameworks are silent. Audit by running with logging enabled and confirming no OTLP exporter init log appears.

CONSEQUENCEundefined behavior