remix-run/remix

Prefer this fork only if you want its custom package/demo/agent workflow layer and are willing to own a large backport burden. If you want current Remix, this is too stale and too far from upstream to be a low-risk adoption.

Prefer upstream unless you explicitly need this older fork’s custom tutorials, demos, or experimental package work. For most adopters, the maintenance burden and missing upstream progress outweigh the fork-specific additions.

Choose this fork only if you want its specific customization or tutorial-heavy shape; if you want current Remix behavior, upstream is the safer default.

Prefer this fork only if its older Cloudflare/single-fetch direction is the product you want. If you want current Remix 3, upstream is the better starting point because this fork is stale and materially behind.

Prefer upstream unless you specifically need this fork's older snapshot, custom tutorial/doc work, or test-focused experimentation. For most adopters, the staleness and large divergence outweigh the visible additions.

Prefer this fork only if you need its older customizations or legacy behavior. For most adopters, upstream Remix is the better base because this fork is extremely stale and significantly diverged.

Choose this fork only if you value the existing custom workflow/docs/test scaffolding more than staying current with Remix upstream. For most adopters, the stale base and large divergence make upstream the safer default.

Prefer this fork only if you need its specific customizations and are prepared to maintain a large upstream gap. If you want the current Remix release line, active support, and lower merge risk, upstream is the better choice.

Choose this fork only if you specifically want its added workflow scaffolding or older demo/tutorial state. If you want a current, actively maintained Remix codebase, upstream is the better starting point.