/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

crewAIInc/crewAI

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:00:07.859Z

3mo ago

crewAIInc/crewAI

crewAIInc/crewAI is a popular, actively maintained Python framework for orchestrating autonomous, role-playing AI agents. It is positioned as a fast, flexible multi-agent automation framework, with both open-source core and enterprise-oriented offerings around CrewAI Flows and the AMP Suite. The repo is large and active, with 47,573 stars, 6,444 forks, and a recent push on 2026-03-30.

Loading tags...

Stars47,573

Forks6,444

Default branchmain

Last pushed2026-03-30T11:00:45Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you specifically need its older behavior or the handful of added core features; otherwise upstream is the better default because it is far more current, actively maintained, and materially ahead on release, docs, and enterprise workflows.

Prefer this fork only if you need its specific older/customized behavior and are willing to own the maintenance burden. If you want current CrewAI capabilities, documentation, and lower integration risk, upstream is the better choice.

Prefer this fork only if you need its specific executor/provider/release customizations and are prepared to maintain a long-lived divergence. If you want the current upstream CrewAI feature set, docs, and lower upgrade risk, upstream is the safer choice.

Choose this fork only if you specifically need its AgentOps-oriented customization or legacy behavior. For most adopters, upstream CrewAI is the better default because this fork is stale and far behind current framework, docs, and enterprise workflow changes.

Prefer this fork only if you need its specific tracing, enterprise-doc, or release-process customizations and are prepared to maintain a large divergence. For most adopters, upstream is the safer choice because this fork is materially behind and appears to have removed or rewritten substantial areas.

Choose this fork only if its local customizations matter more than staying current with upstream. For most adopters, upstream CrewAI is the safer default; this fork is mainly for teams that need a pre-diverged, customized codebase and are prepared to maintain it themselves.

Prefer this fork only if you want its older autonomous-agent experiments and are willing to own the maintenance burden. For most adopters, the upstream project is the safer choice because this fork is substantially stale and likely missing major modern features and fixes.

Choose this fork if you want newer API/runtime capabilities and can tolerate substantial divergence from upstream. Choose upstream if you want the latest maintained release line, broader documentation, and lower integration risk.

Prefer this fork only if you specifically need its custom 2025-era behavior and are willing to maintain a large delta yourself. If you want current CrewAI capabilities, upstream is the safer choice; this fork looks materially stale and increasingly expensive to keep aligned.

Fork comparison

bhancockio/crewAI

38/100

stale

significant_divergence

Prefer this fork only if you specifically need its older behavior or the handful of added core features; otherwise upstream is the better default because it is far more current, actively maintained, and materially ahead on release, docs, and enterprise workflows.

Likely purpose

To experiment with or freeze a specific CrewAI codebase while adding a few core framework behaviors and documentation updates, without following upstream's later release and enterprise work.

Best for

Teams maintaining an older CrewAI deployment and wanting to preserve 2024 behavior.; Developers exploring or prototyping changes to task conversion, event emission, or agent context handling.; Fork maintainers who prefer a frozen base over staying aligned with fast-moving upstream.

Additional features

Adds a `Task` `converter_cls` option.
Adds task-created event emission.
Adjusts cloned-agent context copying behavior.
Includes broad documentation additions and updates, including new docs content and workflow-related changes.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

Appears far behind upstream release cadence and later upstream enterprise work.
Does not reflect newer upstream SSO/RBAC documentation and release-resilience updates.
Likely lacks newer upstream docs/tooling artifacts that were later reorganized or removed upstream, such as the current `tool.specs.json` and docs metadata flow.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want a snapshot with specific core-agent behavior changes already baked in.
May be easier to study than current upstream because the scope is frozen around a smaller 2024-era codebase.
Could suit teams wanting to preserve older semantics for existing integrations.

Risks

Large divergence from upstream makes merges and security/bug fixes harder.
Staleness means ecosystem, docs, and enterprise features are outdated relative to current CrewAI.
Some upstream capabilities may be missing or renamed, so adoption will likely require code and documentation reconciliation.

crewAIInc/crewAI · Discofork