Discofork
Repository brief

anthropics/claude-code

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:19.704Z
1mo ago

anthropics/claude-code

anthropics/claude-code is a large, active terminal-based agentic coding tool with very high adoption (84,469 stars, 7,148 forks). It is still being updated regularly, with recent commits on 2026-03-29 and the repo marked unarchived. Forks may be interesting if you want to extend a widely used CLI coding assistant that already ships plugins, examples, and repo tooling.

GitHub
Loading tags...
Stars84,469
Forks7,148
Default branchmain
Last pushed2026-03-29T02:17:02Z
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

10 of 10 fork briefs
Selected

Prefer this fork if your main need is a Traditional Chinese-facing version of Claude Code documentation and changelog maintenance. Prefer upstream if you want the latest product behavior, because this fork is mostly a localization layer and is materially behind current upstream.

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.