anthropics/claude-code

Choose this fork if you want a more controlled, opinionated Claude Code distribution with standards enforcement and custom hook workflows. Stay with upstream if you want the newest features, lowest-friction setup, and a broadly supported default experience.

Choose this fork if you want a broad, opinionated agent catalog and are willing to trade upstream freshness for customization. Choose upstream if you want the latest maintained baseline with less merge risk.

Prefer this fork if you want a customized Claude Code derivative centered on plugin/workflow development and can live without upstream parity. Prefer upstream if you want the latest features, documentation, and lower integration risk.

Prefer upstream unless you specifically need this fork’s namespace or plan to extend it yourself. For adopters, the main signal is staleness: it offers no visible added functionality and is materially behind current upstream.

Choose this fork if you want a more specialized, workflow-oriented Claude Code base and are comfortable owning the maintenance gap. Avoid it if you want upstream parity, full docs/examples, or the latest release cadence.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible capabilities and is far behind current upstream, so it is a poor adoption candidate for most users.

Choose this fork if your main pain point is the code-review plugin’s phrasing or issue-detection guidance. Skip it if you want an actively tracked upstream base, because the fork is materially behind and adds only a small workflow refinement.

Prefer upstream unless you specifically need this older snapshot. This fork adds no visible functionality and is materially behind the active project, so it is a poor choice for adopters who want current features or support.

Choose upstream unless you specifically need this fork’s repository identity; it does not show meaningful added capability, and it is materially behind current upstream.