ninjahawk / livenerf
git clone https://github.com/ninjahawk/livenerf.git
Benchmark for tracking model capability after release.
—
stars, 24h
—
stars, 7 days
+1.5k
stars, 30 days · #208
1.5k
★ total
20
forks · 3 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguagePython
LicenseMIT
Created2026-09-22 (28d ago)
Last pushtoday
Watchers25
OwnerUser
Links
README excerpt
# livenerf *A long-running, deterministic-as-possible benchmark for detecting whether a frontier model gets quietly worse after launch.* The plan · Results · How it works · Pre-registration · Discord --- livenerf is a small, boring, append-only benchmark for one question: does a model get worse after it ships? For months there have been reports that Anthropic "nerfs" models some days or weeks after release. That could mean quantization, a smaller model behind the same name, lower effort, or routing changes. It could also mean nothing happened and people are pattern-matching on noise. Nobody has had a clean day-0 baseline to check against, so every argument ends up as vibes versus vibes. Claude Opus 5.5 came out on 2026-09-22, so this is a chance to start the clock on launch day and keep it running. Right now v0 runs on a Claude Max subscription through headless Claude Code (`claude -p`), with no API key. You can't make these models deterministic: sampling params are gone and thinking can't be turned off. So livenerf makes everything *else* deterministic: frozen prompts, pinned CLI, exact graders, raw logs forever. It then measures drift statistically over thousands of samples. It's built on Inspect, the UK AI Security Institute's open-source eval framework. The stats follow Anthropic's own Adding Error Bars to Evals, so there's nothing homebrew to argue about. Each day's score is posted in the LiveNerf Discord, where people discuss the results and the method. For questions about the repo, open a thread in the Discussions tab or an issue. ## Status **The series is running.** Day 1 was 2026-09-24 22:10 UTC, about 2.5 days after launch. It runs once a day for 30 days: days 1–10 are the baseline, then there are two 10-day windows, so the first possible call is around 2026-10-24. The first Results row lands after day 20. The panel was chosen, confirmed, locked and validated under a pre-registered protocol (v2). Every number below is generated from the logs in docs/CALIBRATION.md. **Progress (2026-10-20):** 27 of 30 days collected, none missed. The baseline (days 1–10) is complete; window 1 (days 11–20) is complete (no change, see Results); window 2 (days 21–30) has 7 of 10 days. All 27 days ran the full 90 samples on the same harness hash (`461391b6fce64167`) and pinned CLI (2.1.280). Days 5 and 12 ran with the budget guard overridden. The realized MDE from the baseline is 6.6 points per 10-day window (predicted 7.5). Day 12's first attempt crashed when the PC ran out of memory and is excluded whole; a complete rerun the same day is day 12 (see the deviations log). Day 19 (2026-10-12) ran on Anthropic API credits instead of the Max plan, because the Max weekly meter was exhausted; its logs are labeled `funding_source=anthropic_api` (deviations log, 2026-10-11). - **The panel.** 2,336 GPQA Diamond, MMLU-Pro, competition-math and AIME 2025–26 questions were screened with 4 samples each. Opus 5.5 gets about 93% right on the first try, and 97% of the qu