karpathy/nanochat

Prefer upstream unless you specifically need this older, unchanged snapshot. This fork adds no visible capabilities, while lagging 345 commits behind upstream means it likely misses newer fixes and training improvements.

Choose upstream unless you specifically want this fork’s exact pinned state; it adds no visible capability and is already materially behind active upstream work.

Choose this fork if your priority is deployment and demo workflows across hosted platforms; choose upstream if you want the latest training-efficiency work, benchmark tuning, and a smaller moving target.

Choose the fork only if you specifically want a frozen older baseline; otherwise upstream is the better choice because this fork is materially stale and provides no evident added capability.

Choose the upstream repo unless you specifically need this older checkpoint; this fork adds no visible capabilities and is materially behind on active development.

Choose upstream instead unless you specifically want this fork as a frozen, unmodified snapshot. It adds no visible features and trails upstream by 363 commits.

Choose this fork if you want an EBT-focused research branch with substantial new training and model code. Choose upstream instead if you want the current minimal ChatGPT-style harness, the latest benchmark optimizations, and the most active reference implementation.

Prefer this fork if your goal is MoE experimentation and richer training/export workflows. Prefer upstream if you want the current, simpler nanochat benchmark-oriented stack with less maintenance risk and better compatibility with ongoing upstream improvements.

Prefer upstream unless you specifically need this exact historical snapshot; the fork adds no new capability and is substantially behind current nanochat.