posts · 2026-08-13

The headline number is what makes this worth opening: a jump from roughly $120bn in the last private round to nearly $2tn at IPO. The FT cites people familiar, but the post doesn't give offering size, timeline, or underwriters. A private-to-public markup this steep needs revenue growth and margin data from the S-1 to back it up. I'd discount it for now—we've got a directional signal and a big number, but no filing to check the math against.

The $6B number is what makes this worth clicking: a 50-person startup founded last year, valued at that price, tells you how desperate the infra talent war has gotten. Decart works on training optimization and AI infrastructure — exactly the kind of team OpenAI and Google are also chasing. But the post relies on a single Bloomberg source, with no details on deal stage, payment structure, Decart's technical metrics, or customers. Neither company commented. I'd discount this for now: it's a signal of intent, not a done deal. If it closes, Anthropic could patch its training-efficiency gaps faster, but $120M per head only makes sense if you're staring at a severe talent shortage.

This is worth opening because it turns paper reproduction from manual labor into a scaled pipeline. In 19 days, over 1,200 people armed with Claude Code and Codex ran through 2,226 ICML 2026 papers. The headline case: a spotlight paper where the reviewer admitted they didn't check the proofs carefully, and the reproduction caught real issues. I'd discount the coverage a bit — this wasn't deep reproduction of all 2,226 papers, but claim-by-spot-check, so quality varies. The direction matters more than any single result. When agents can read papers, write code, and run experiments at scale, the peer review bottleneck shifts from "not enough reviewers" to "how do humans audit agent output." HF's own question in the post: if agents handle experiments and writing, what's left for humans? Their current answer: setting direction, judging results, and being the final sign-off.

This one's worth opening because Anthropic laid out the engineering ledger of a math search campaign. Two Claude Code sessions burned 31M output tokens. Round one produced 650 ideas—all failed—but left a ledger of 106 partial survivors, each tagged with where it died and what new evidence would reopen it. Round two coordinated ~60 subagents to recheck that ledger and stitch a final route via stepping-stone transfers. I'd discount the headline number a bit. The proven lower bound of Riemann zeta zeros on the critical line went from 41.6% to 67.2%—still nowhere near proving the Riemann Hypothesis, and Anthropic admits this technique won't get there. Baluyot et al. already reached 67.25% under a narrow-box assumption in 2024-2026. Claude's real contribution was dropping that assumption, not inventing 25.6 percentage points from scratch. The search architecture is the useful bit. Each route got kill criteria, and subagents returned death reports, not half-baked proofs: what broke, which local derivations still hold. One hostile review subagent caught a hidden math error and supplied a fix. Failure information became a do-not-repeat list, and it even enabled cross-route stepping stones—the post documents one case where a seemingly useless local judgment from round one resurfaced 12 hours later to fill a critical gap in a new route. The verification side is less rosy. Lean code is sorry-free and hooks directly into Mathlib's riemannZeta definition—solid L2 machine checking. But the effective form mentioned in the paper isn't in the headline statements, and the reference script for symbolic checks didn't make it into the frozen repo. L3 intent alignment has backing from two Anthropic mathematicians, but no independent third-party review. L4 peer understanding amounts to Brian Conrey and Dan Goldston reading on short notice—no public referee report a day after release. Stack this against OpenAI's ten math advances and GPT-5 on Erdős, and the pattern is clear: generation and formalization are accelerating fast, while human understanding and absorption stay flat. The bottleneck is shifting from discovery to comprehension.

This piece connects the dots on why coding agent form factors keep shifting—desktop apps, managed cloud agents, remote control—and the answer is execution data. Once a model outputs code, the real gold is what happens next: which edits users make, where errors pop up, how many rounds it takes to get something working. LangChain's test showing a 10–20 percentage point gap with vs. without tuned runtime config makes that concrete. DeepSeek previously only sold API access and left the tooling layer to third parties. Now it's hiring an Agent Harness PM, which signals it sees the gap. The article is careful not to overclaim—this is a job posting, not an official strategy reversal—but the direction is clear. The framework worth keeping: stop comparing feature checklists. Ask who controls the execution environment, who sees the data, and who's inside the data flywheel. Interfaces converge because they're cheap to copy; execution layers diverge because that's where the moat is.

This one's worth opening because DeepSeek finally open-sourced its agent harness, and the architecture is genuinely different from Codex or Claude Code. The core agent loop—the logic that decides how the model thinks, calls tools, and iterates—is a plugin you can swap at runtime. In every other harness, that logic is hardcoded and untouchable. To support this, DSH ships with a runtime called Cordis that handles side-effect cleanup, dependency notifications, and transactional rollbacks during hot swaps. A single file, fiber.ts, runs 750 lines—you can see they've hit real concurrency and rollback edge cases, not just paper abstractions. But I'll be real: for most daily coding, this is overkill. Codex's declarative plugins are dead simple—edit a config, restart in two seconds, done. DSH forces you into a heavier model where every plugin registers side effects, declares dependencies, and returns teardown functions. You just don't need in-process hot-swapping for search or skill plugins. The useful bit is self-evolution. If an agent can generate new tools or even a new control loop mid-run, DSH is the only harness with the infrastructure in place. Model capability is right at the edge too—generating a 50-line tool is routine, and a few-hundred-line agent loop is within reach of top models. Codex's loop is compiled into Rust with no slot to swap it. DSH provides that physical interface. The post doesn't include performance benchmarks or production data—it's architecture analysis and source-code reading. I'd treat this as infrastructure for self-evolving agents, not something that'll speed up your daily coding.