Glean 拾遗
中 EN
Submit a link
Daily · timeline

A few picks a day.

Fri, Nov 13, 2026 3picks
← 11-12
Calendar ▾
2026 · 11
MoTuWeThFrSaSu ······123456789101112131415161718192021222324252627282930
has picks today
11-14 →
06:00

How the Claude Code team reviews 30,000 changes a day

Claude Code 团队如何用六层流水线取代逐行人工评审

Anthropic's Claude Code team describes its internal review pipeline, built for a repo where daily merged changes went from ~2,500 in May to over 30,000 in September. Review is split into six layers: runnable verification and a fresh-context subagent before the PR exists; a Claude reviewer on every PR that reads the diff against the whole repo and the stated intent, with findings voted on by several agents before posting; a security review that can block merge; CI; risk-tiered human approval (0/1/2 people) assigned by a classifier reading the change rather than the author; then merge queue, flags, internal dogfooding and one-step rollback. They also document the failure modes: one CLI PR ran more than fifty review rounds overnight, and git blame showed ~59% of flagged lines predated the reviewer's first pass, prompting a three-round cap and diff-only re-review. Useful for teams wiring agents into their own review flow.

claude.dev · 19 min · Agentic Coding · Claude Code · Code Review · Code Verification · Coding Agents
06:00

1,000 agents, no researcher: a self-organized Lean proof of Fermat

1000 个 Agent 自建协作体系，28 小时证完费马大定理

A thousand agents running an early build of Claude Fable 5.2 formalized Fermat's Last Theorem in Lean in 28.7 hours, without the Prove2Me coordination platform or a researcher steering the work. Each agent got its own network-isolated sandbox, a Git branch, a shell, Lean plus Mathlib, and access to a shared Postgres database. The lead model spent its first ten minutes creating five tables to announce orders, assign statements, collect notes, queue subtasks and log finished work; helpers then claimed tasks and reported progress through them. After most agents judged 47 of 60 statements infeasible, the lead reallocated nearly everyone to the remaining ten, and later built a 2,418-node task tree up to ten levels deep for Langlands–Tunnell. The post details the safety stack—sandboxing, a blocking classifier on every tool call, and offline monitoring—and concedes that agents still misjudge difficulty and quit early.

claude.dev · 23 min · Agent Harness · Ai Safety · Formal Verification · Multi-Agent · Sandboxing
06:00

Shopify's 12-week rewrite: agents wrote code, humans rebuilt the loop

Shopify 用 30 人 12 周重写 App：agent 写代码，人改流程

Thirty Shopify engineers moved a 300+ screen app from React Native to Swift and Kotlin in 12 weeks, with agents writing most of the implementation. The post is about what surrounds the code: business logic runnable without a device, the Reflex architecture and a CLI that loads any screen in milliseconds, one shared architecture across iOS and Android, an example and .md file per screen, and CI that fails when the two platforms diverge. Spec-driven development was abandoned because specs went stale in days; the legacy React Native app became the reference. The second half covers the bottleneck shift — laptops saturating on emulators, review and merge queues, tickets lagging behind Slack-reported fixes — and the responses: a remote dev environment for agents, adversarial agent-first review, and a self-healing loop that reproduces crashes every 15 minutes. Results: Android launch 1.71s to 0.87s, binary 80.4MB to 47.6MB.

shopify.engineering · 19 min · Agent Workflows · Agentic Coding · CI/CD · Code Review · Mobile