AntonOsika/gpt-engineer

Prefer this fork only if you specifically want an older, stripped-down codegen CLI to modify. If you want an actively maintained, feature-complete gpt-engineer experience, upstream is the safer choice.

Choose this fork only if you specifically want an older, heavily modified baseline to hack on. For most adopters, upstream is the safer choice because this fork looks stale, divergent, and likely missing later improvements.

Choose this fork only if you specifically want its older, customized CLI behavior and are willing to own maintenance. If you want current fixes, documentation, and lower integration risk, upstream is the safer choice.

Prefer this fork only if you specifically want its older experimental internals or need to preserve its custom CLI/file-selection behavior. For most adopters, upstream is the safer choice because this fork is much older, significantly behind, and likely missing a lot of later fixes and support material.

Choose upstream unless you specifically need this exact older snapshot. This fork adds no clear capabilities and is materially behind, so it is mainly useful as an archival or experimental copy rather than a preferred adoption target.

Prefer upstream unless you specifically need this exact old snapshot; this fork adds no visible capabilities and is materially behind on maintenance.

Choose this fork only if you specifically want the gpt-engineer workflow in a JS/TS stack and are comfortable owning a divergent codebase. If you want maximum compatibility, documentation continuity, or access to the original Python ecosystem, upstream is the safer choice.

Choose this fork if you want a lightweight but opinionated experiment around worker orchestration and iterative improvement. Stay on upstream if you want the most established baseline and do not need the extra orchestration layer.