Agent Atlas / Agent frameworks

crewAIInc/crewAI

A framework centered on orchestrating role-based agents, crews, tasks, and flows for collaborative multi-agent applications.

Agent framework Scope profile Project documented Reviewed August 26, 2026
Intended operator

Python developers composing multi-agent applications and workflows.

Primary surfaces

Python framework / crew and task abstractions / workflow flows

Tracked repository

crewAIInc/crewAI

Teaching mechanism

A role name is not yet a delegation contract

Crew and task abstractions make responsibilities explicit, but dependable delegation also requires lifecycle, authority, result, cancellation, and evidence semantics.

Evidence limitTheGitReporter has not yet inspected how those semantics behave across current execution and persistence paths.
Inspect the source
System map status

Reporting is still in progress.

This scope profile names the project's place in the field and one useful mechanism. It does not claim that every runtime boundary has been inspected.

Learn Through This Project

8 lessons
Chapter 1 Before the First Model Request Chapter 3 Tool Calls: Contract, Authorization, Execution Chapter 4 Loops, Workflows, and Recovery Chapter 5 Delegation Is a Distributed System Chapter 6 Memory Is a Typed Storage Contract Chapter 7 The Approval Trap Chapter 9 Trust Must Make Its Case Chapter 10 The Future Has Three Branches

Compare Its Boundaries

7 labs
Comparison labTool ContractsComparison labGoverned MemoryComparison labDelegation ReceiptsComparison labApproval BoundariesComparison labSessions And RecoveryComparison labEvidence And EvaluationComparison labMaturity Signals

Latest Reporting

4 articles
CrewAI teaches telemetry to separate the agent from the room

August 9, 2026 — CrewAI’s agent-assisted telemetry change makes one reusable move: record who drove a process separately from where the process ran. crewAIInc/crewAI

 QM is trying to turn the personal agent into company infrastructure

August 1, 2026 — Y Combinator's new open-source harness does not win its case by running Codex or Claude in Slack. Its more consequential bet is that every person and room needs a clearly owned memory, workspace, permission set, schedule, and durable computer. yc-software/qm, block/buzz, egregore-labs/egregore, openclaw/openclaw, NousResearch/hermes-agent, crewAIInc/crewAI, microsoft/agent-framework

 CrewAI: role-based multi-agent orchestration after the demo

August 1, 2026 — CrewAI's current source makes a useful correction to the role-playing pitch: a multi-agent crew becomes an operable system only where it carries state, records its progress, and proves what happens after a stop. crewAIInc/crewAI

 API Discovery: Tell an Agent When Waiting Is the Work

July 28, 2026 — CrewAI’s new WaitTool gives an agent one narrow capability: let a real external job make progress before checking it again—without pretending that a pause is a status update. crewAIInc/crewAI

Primary Sources

CrewAI repository

Primary public framework source.

Open Questions

  • Which crew abstractions carry enforceable authority and lineage, rather than only prompt-level roles?

Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.