Navigara
OpenAI

codex — Engineering Performance

33 engineers all time · Apr 2025 – Nov 2026 · built 2026-11-22 · GitHub

Performance snapshot

Today's rolling 90-day reading for codex, compared with the start of the series. Pick a window to move that comparison point.

Avg. perf / dev / mo

+432.9%

1.73 → 9.21 ETV

Active engineers

+242.9%

7.0 → 24.0

Features

−27.0pp

60.1% → 33.1%

vs. OpenAI

0.95x

1.6x → 0.95x · −5% below

codex vs. OpenAI

Per-engineer ETV for codex against OpenAI as a whole. Both lines are 90-day rolling averages scaled to a 30-day month, so they share one axis and can be read against each other at any point. Pick a window to zoom the chart to it.

codex
9.21ETV / dev / mo
+1.86 (+25.3%) past 90d
OpenAI
9.65ETV / dev / mo
−1.98 (−17.0%) past 90d

Performance Composition

Each month's output split by type of work: Features (new value), Maintenance (sustaining systems), Tests, Docs, and Fixes (rework). The yellow line is output per engineer, so when it rises each engineer is delivering more, whatever the team size did. Unit: Engineering Throughput Value (ETV).

Engineering capacity

Effective engineers behind codex, against its pre-AI baseline. Each subject has its own: codex's is 1.73 ETV / dev / mo, its first reading in Q2 2025. Per-engineer ETV divided by that gives a capacity multiple, and that multiple applied to the engineers active in the trailing 90 days turns it into engineer-equivalents. The line is the real headcount, so the gap between line and area is what the leverage is worth. Because each baseline is its own, every subject opens at 1.0x on its first day: multiples measure improvement and are not comparable between subjects.

Effective engineers
128engineer-equivalents
+104 engineers above real headcount
Real engineers
24engineers
active in the trailing 90 days
Capacity vs pre-AI
5.3x
per engineer, vs 1.73 pre-AI

Knowledge concentration

How dependent is this repo on a small number of engineers? Higher top-1 share = higher key-person risk.

Top 1
23.8 %
Top 3
49.1 %
Top 5
63.8 %

jif owns 23.8 % of commits.

Behind the numbers

Sep

Written summary of the work completed each month.

In September 2026, development activity surged across the repository with 1,617 total commits, delivering major enhancements in asynchronous classification for Guardian v2, exec-server streaming, and thread persistence. Total output increased across every category, with Features up 63% and Tests rising 135% compared to the 5-month average. The period represented a genuine step up in volume and delivery, exceeding both the 5-month average and the preceding two months.

Highlights

Observations

  • Total commits reached 1,617 (a 64% increase over the 986-commit 5-month average), yielding a total output score of 772 versus the 394 5-month average (+96%).
  • Features score rose to 254 compared to the 156 5-month average (+63%), driven by major feature additions in Guardian classification, exec-server protocols, and TUI capabilities.
  • Fixes score reached 126 vs the 52 5-month average (+143%), involving targeted fixes for session lifecycle interruptions in ec0cfa5d (Benjamin), TUI paste handling in cca44069 (Benjamin), and thread naming persistence in 1f77c0cf (Raunak).
  • Significant performance refactoring moved blocking I/O operations off async runtimes, including session index I/O in 4f699cd6 (Charlie), thread history projection in ecc205ed (Charlie), and rollout directory scanning in 5aa92804 (Charlie).
  • Tests score surged to 292 (+135% above the 124 5-month average), reflecting comprehensive snapshot, regression, and unit test suites across TUI, exec-server, and state recovery modules.

Based on 1,617 commits463.2 ETVUpdated Nov 22, 2026, 5:01 PM

Most impactful commits

Top 10 by ETV in the all-time window.