NanoChat: Python vs the web runtime

The browser implementation measured against the same Python reference.

33% parity

How much of nanochat survives the move to the browser?

12 of 36 capabilities fully present · baseline nanochat (Python) → target NanoChat Web · 36 compared

assessment v1 · 2026-08-02 · authored match

36 runtime capabilities: 12 aligned, 18 partial, 4 missing in Web, 2 intentional differences. UI excluded. Target is codex/foundation at c950592 with recorded dirty runtime manifest; no commit made.

Different 2

Both sides implement the capability — but not the same way. This is the verdict a simple has-it check cannot express, and it is where a port quietly diverges from its reference.

Missing in NanoChat Web 4

The work queue: capabilities the baseline has and the target does not.

Partial 18

Started, not finished — present but not equivalent.

Only in NanoChat Web 0

Not defects. Parity is directional, so what the target adds beyond the baseline shows up here rather than counting against anyone.

None.

nanochat (Python) spec NanoChat Web spec comparison.json

36 runtime capabilities: 12 aligned, 18 partial, 4 missing in Web, 2 intentional differences. UI excluded. Target is codex/foundation at c950592 with recorded dirty runtime manifest; no commit made.