Two labs put their models on the lab bench

GPT-5.4 ran 10,080 reactions against a widely used drug-discovery transformation, proposed an unexpected tweak to the conditions, and a wet lab checked the result by hand. Yields improved for 88% of the boronic acids and 83% of the sulfonamides tested; when human chemists repeated 14 representative reactions on the bench, 11 came back with higher yields and 8 of those more than doubled. OpenAI published the chemistry result alongside LifeSciBench, a new benchmark of 750 expert-authored tasks built with 173 biotech and pharma scientists across seven research workflows, where a specialized model, GPT-Rosalind, beat GPT-5.5 on all seven. The benchmark is the hedge and the chemistry run is the headline: a frontier model paired with Molecule.one’s Maria agent and a real lab moved from literature review to a validated experimental result without a chemist in the loop until the verification step. It lands four days after Anthropic’s own Making Claude a Chemist work, and the pattern is now hard to miss, both labs are racing to show their models doing science that holds up off the screen, with bench validation as the proof they keep reaching for.

The other launch worth your attention came out of Build 2026: Microsoft introduced Scout, the first of what it’s calling Autopilots, always-on agents that work autonomously on a user’s behalf, carry their own identity, and don’t wait to be prompted each time. Scout runs on the open-source OpenClaw framework and plugs into Work IQ. The framing is the interesting part. We’ve spent a year talking about agents you invoke; an Autopilot is an agent that just runs, with a standing identity inside the org. That raises the same question every team adopting agents is now hitting from the governance side, and Estonia answered it bluntly this week by assigning personal ID numbers to AI agents so they can be granted authorizations like any other actor. When a survey making the rounds says 85% of IT teams claim every agent is under control but only 42% actually know who owns them, a national ID registry for bots stops looking like a curiosity.

On the tooling side, Cursor shipped cloud agents in the agents window: move a local agent to the cloud so it keeps working with your laptop closed, prompt it from your phone, run many in parallel, and get back PRs with demos attached. A new /in-cloud command drops a subagent into its own cloud VM, and environments are captured as reusable snapshots so the next agent boots fast and can test until output is verified. The launch arrives days after SpaceX agreed to buy Cursor for $60 billion in stock, and the shape of the product, fleets of isolated agents you dispatch and review, tells you where that money expects coding to go.

Anthropic added a data point to the other half of that debate. Its new research note, Agentic coding and persistent returns to expertise, argues the advantage experienced engineers hold doesn’t wash out when everyone gets a capable coding agent, it persists. That sits next to the finding from its 400k-session study yesterday that non-engineers now code within a few points of SWEs on some measures, and the two aren’t contradictory: the floor rises for everyone while the people who know what they’re doing still pull ahead, because knowing what to ask for and what to reject is the part the agent doesn’t do for you.

GitHub published the unglamorous version of the same lesson. Its post on getting more from each token walks through how Copilot cuts what it re-sends turn to turn, context, tool definitions, cached state, and routes between models so longer agentic sessions don’t drown in their own overhead. Efficiency at this layer isn’t about a cheaper bill, it’s whether a multi-step agent can hold a coherent task across dozens of tool calls before the context budget runs out. GitHub paired it with a couple of practical changes this week too: language-server support for the Copilot CLI, and gh repo read-file to pull remote repository content without cloning.

The week’s reminder that all of this expands the attack surface came from Varonis, which turned Microsoft 365 Copilot into a one-click data-exfiltration tool. The SearchLeak attack chains Copilot’s search and rendering behavior so a single user action can leak data the assistant has access to, no malware, no second click. As Copilot, Scout, and every other always-on agent get broader read access to your tenant, the blast radius of one prompt-injection-shaped bug grows with it, and the defensive tooling is still catching up to the surface the agents opened.

What to watch: the r/ClaudeCode chatter that Anthropic is staging a new model release, and whether OpenAI’s LifeSciBench numbers survive contact with chemists who didn’t build the benchmark.