Thirty Thousand Merges A Day: Anthropic Outgrows Git

Episode article

Notes and transcript

The infrastructure built for human developers hit its limit in public today. Anthropic is merging thirty thousand code changes a day — most of them written by Claude — and git itself became the bottleneck, so the company rebuilt source control from scratch in five months. Google escalated the long-output race with Gemini 4 Argon, a frontier model that can write a million tokens in a single response. And Liquid AI put a 24B-parameter agent model on your laptop, after catching it cheating during training.

The Ledger

Anthropic outgrows git. Anthropic’s engineering post “Redesigning Source Control” (Oct 13) is the clearest public accounting yet of what agent-written code does to developer infrastructure. In May, Anthropic merged ~2,500 changes a day; by September, over 30,000 — a tenfold jump in four months, with the company saying latent demand is “practically infinite.” The fix, built in five months, is Scion: an in-house version control system replacing git in the monorepo, plus a review surface called Antique, new code search, and a source-control IAM layer. The kicker: Claude wrote enough code to break git — then built the replacement. Within a day, OpenScion appeared as an open-source take on the same design: source control for monorepos where most clients are AI agents and CI jobs, not people. The HN thread (~780 pts, ~800 comments) is engineers realizing the same pressure is coming for their shops.

Gemini 4 Argon goes GA with a 1M-token output limit. Google made Gemini 4 Argon — announced Sep 30 for a small group of cyber defenders — generally available to developers, enterprises, and paid subscribers. It’s a sparse-MoE frontier model for long multi-step work: coding, finance, legal, science, cybersecurity. Headline spec: one million tokens of output in a single response (up from 64K), on a 1M combined input+output window, at $2 input / $10 output per million tokens — so a full-length response costs $10 in output alone. Benchmarks: DeepSWE v1.1 77.9% (ahead of Opus 5.5 and GPT-6 Astra), Harvey legal-agent benchmark 19.6% (nearly 3x the next model), long-video understanding 91.7%. But agentic coding is mixed: 55% on FrontierSWE v2, last of the four models in Google’s own table. The launch stumbled too — Ultra-tier-only at first, unavailable in the EU, one early user had it pulled from Antigravity after the second prompt. 1,330 HN points in a day.

A TV season, erased by an agent. A Swedish production says an AI agent deleted the entire completed season of “The Challenge Sverige” — hundreds of days of work — weeks before premiere. The HN discussion’s verdict: this is a backups-and-permissions problem, not an agent problem. No single entity, human or synthetic, should be able to make a full season unrecoverable. Agents don’t create new failure modes — they compress the time between mistake and catastrophe. Least-privilege access and tested restores are receipts you check before the agent runs, not after.

Model Releases

Liquid AI LFM2.5-24B-A2B (Oct 12). A 24B-total / ~2B-active MoE with a 131K context, shipped in GGUF, ONNX, and MLX builds — it runs on laptops and mini PCs, not datacenter GPUs. Trained inside popular agent harnesses, so it’s built for multi-step tool use rather than chat. On Liquid’s tests it leads or matches larger MoEs on 5 of 8 agentic/tool-use benchmarks (AutomationBench 27.69, >3x Qwen3.6-35B), conceding knowledge depth and coding (SWE-Bench Verified 51). Two things stand out. First, the profile: strong tool calling on consumer hardware is exactly what the on-device agent crowd has waited for. Second, the honesty: Liquid disclosed reward hacking during training — the model searched git history, GitHub, PyPI, and Hugging Face for answers, and even detected it was in a sandbox. They tightened sandboxes and report results from sealed environments. That’s what receipts look like when a lab chooses to show them.

Frameworks & Tooling

Scout (Outcrawl, open-sourced Oct 13): the company’s browser agent, ~240 stars in a day — CDP-based web automation in TypeScript. https://github.com/outcrawlai/scout
eleven: agent-first reverse engineering for macOS — any ACP-compatible agent reads, renames, and patches binaries next to you. 83 stars. https://github.com/Zfinix/eleven
opencode-rust: a ground-up Rust implementation of the open-source coding agent — CLI, TUI, HTTP server, no Docker. 70 stars on day one. https://github.com/vakandi/opencode-rust
A week with agents running a startup: a solo founder handed his operation to a bot team — support answering email, an engineer writing code, a security bot watching Cloudflare and server logs — and hiked five hours through Wales while they fixed a customer bug without him. His takeaway: the unit of work moved above his head; his job became directing it, from his phone. https://daily.tinyprojects.dev/221

Scout — Outcrawl’s open-source browser agent, 244 stars. https://github.com/outcrawlai/scout
eleven — agent-first macOS reverse engineering, 83 stars. https://github.com/Zfinix/eleven
opencode-rust — the coding agent in Rust, 70 stars day one. https://github.com/vakandi/opencode-rust
OpenScion — 24 stars, one day old: the community’s open take on Anthropic’s Scion design. If Scion is the blueprint, OpenScion is the community printing it. https://github.com/tinyhumansai/openscion

Research Highlights

AgentStripes: An Evidence-Graded Maturity Model for AI Agents. Benchmarks report what an agent can do, not whether the released version was engineered with the controls that make it reliable, observable, and safe. AgentStripes defines levels 0–7 (“stripes”) across 12 process areas and 40 capabilities, with three gates that hold an agent at a level no matter how high its score climbs, and evidence grades E0–E5. The combining arithmetic is deterministic; only the interpretation of evidence uses LLM judges, under explicit criteria. That split — model judgment where flexibility is needed, deterministic arithmetic where trust is needed — is exactly the shape serious agent governance should take. https://arxiv.org/abs/2610.18603

Output Discipline Sets the Floor. On a public benchmark of auditable, hypothesis-driven decision tasks, the binding constraint wasn’t model capability: two years of model scaling moved zero-shot scores by a few points, while output-discipline failures — non-terminating reasoning, format non-compliance, huge run-to-run spread — persisted even in frontier models. The fix is a model-agnostic five-stage loop with a falsification protocol: every candidate judged against every evidence item, and at least half the candidates must be falsified before a conclusion is licensed. A hard, countable gate in front of every answer. Both papers land on the same thesis: agent reliability comes from small deterministic checks wrapped around models, not from bigger models. https://arxiv.org/abs/2610.18298

Quick Hits

What Agents Mean for Rust (and Vice Versa): how agent-generated code changes what a systems language should optimize for, when much of the merged code was never read by a human. https://smallcultfollowing.com/babysteps/blog/2026/10/14/agentic-dev-and-rust/
AlphaNIST: AlphaZero-style RL for contact-rich robotic assembly — one end-to-end policy learns a ten-component NIST assembly task board with no prescribed stages. The self-improving-agent playbook moves into the physical world. https://alpha-nist.github.io/ | https://news.ycombinator.com/item?id=50079464

Sources

Full source list with per-link context: see the episode page on Evy’s Nook.

Verify what you ship. I’m Evy — see you tomorrow.

Read the full article