⚡ 60-Second Catch-Up
A fintech company built its own coding agent and is now ahead of the labs that sell them. Ramp's internal harness, Inspect, raised 75% of all merged pull requests at the company as of May, up from about 60% in January, crossed a million sessions in July, and is maintained by five and a half people — four engineers, a director and a part-time PM — while more than 150 Ramp engineers have contributed to it. Roughly 80% of Inspect is now written in Inspect. Gergely Orosz, who reported the story with Jessica Salmon and Ivan Klaric, gets the founding team to explain why they turned down Claude Code, Cursor and Codex: not model quality, but that local machines cap you at one or two parallel sessions, and that a third-party harness cannot see your telemetry, your feature flags or your read-only prod replica. So Inspect runs on remote sandboxes that spin up in under five seconds and verifies its own work — running tests, querying flags, screenshotting frontend changes. → The transferable part is not "build your own harness." It is the observation that the ceiling on your agents is access, not intelligence. Before you pay for a smarter model, write down the three things you check by hand after every agent run — the test suite, the staging screenshot, the log line — and ask whether the agent can reach any of them. That list is your actual roadmap.
Generation speed became a product category this week, and the cheap tier got very loud. NVIDIA put Groq 3 LPX into full production, an inference accelerator aimed squarely at the decode phase — how fast tokens come out for one user — hitting a record 3,400 output tokens per second on Gemma 4 31B at a 100,000-token context, which NVIDIA says is four times the nearest alternative. Nebius is first to deploy. At the other end of the market, an anonymous model called Ox Alpha ran 26 trillion tokens through OpenCode in four days across 327,000 users, free, from a maker nobody has named. And Tomasz Tunguz argues the whole stack is caught in an AI bullwhip — GPU scarcity cascading into memory, storage and datacenter construction costs. → Latency is about to stop being a fixed cost you design around. If your product has a step where the user waits on a model — a summary, a search, an agent turn — you have been building the UX for a constraint that is being engineered away. Time that step today and write the number down, because the version of your product that assumes it is three times faster is a different product.
Everyone is discovering that agents need documentation written for machines, not for people. A design team rebuilt its design system into layered Markdown files so agents could reason over it, after finding that AI-generated frontend code looked right but kept missing hover states, spacing tokens and button rules. Ron Bronson argues agent systems need failure affordances — an explicit channel for "something went wrong", separate from the permission layer that decides what an agent may do — citing an agent that discovered it could cancel other users' gym reservations. And the skills themselves are going multilingual: the share of newly created agent skills written in a language other than English rose from 13.0% in the first quarter of 2026 to 16.3% in the second, with Chinese leading. → Your README is now an API surface. Pick the one internal doc your agents get wrong most often — the deploy runbook, the component rules, the data model — and rewrite it as explicit constraints rather than prose explanation. "Buttons use --space-2" beats three paragraphs on spacing philosophy, and it is the difference between an agent that is almost right and one that is right.