The default changed, not the policy
How we organise
Unity AI Gateway is Generally Available (Databricks)
Databricks moved its AI gateway to general availability. The gateway sits in front of agents, models, MCP servers, skills and coding assistants. It reports cost by model, provider, team and application, and lets a team set a budget and enforce a hard spend cap. A Smart Routing beta, still invitation only, sends each request to a cheaper model where the task allows. Databricks says over a quadrillion tokens have passed through the gateway in the past year, naming Rivian, Asana and Edmunds among the customers running it.
Finance: spend control has been a reporting problem. Every finance function could see the bill after the fact, and almost none could stop it mid-month. A hard cap enforced at the gateway turns spend control into a configuration setting. The decision that follows is uncomfortable, because someone now has to name the number at which an agent stops working, and own it when the agent stops. That conversation is easier before the overspend than after it.
Find out this week whether anything in your stack can refuse an AI request on budget grounds. If the answer is a dashboard, you have observation rather than control.
What are code reviews even for? (Engineering Enablement, DX)
DX reports that lines of code per human-landed diff at Meta rose 106 per cent. Generation got faster and review did not. The piece argues the bottleneck exposed something older than AI. Code review was carrying four different purposes at once, including defect detection, knowledge sharing, style enforcement and accountability, and no team had agreed which one mattered most. Reviewers now cannot serve all four at twice the volume.
Talent: this is a capacity problem wearing a quality costume. Doubling the output of every engineer while leaving the review population fixed guarantees a queue. The organisations that cope will be the ones that decide what review is actually for, and then move the other purposes somewhere else. Style goes to a linter. Knowledge sharing goes to pairing or documentation. What remains is a smaller, sharper job that a human can still do well.
Ask your engineering leads which of those four purposes their review process is optimising for. If you get four different answers, that is your finding.
How we build
Introducing Muse Code and Muse Spark 1.2 (Meta Superintelligence Labs)
Meta released a terminal-only coding agent in beta. It runs persistent background agents that keep working asynchronously, and it writes a replay-exact append-only event log of everything that happened. Meta describes one kernel-optimisation case running over a thousand tool calls across as much as twenty-four hours. The underlying model, Muse Spark 1.2, was trained alongside the agent rather than adapted to it afterwards.
Engineering: an agent that runs for a day without supervision is only useful if you can reconstruct what it did. Replay-exact logging turns an autonomous run from an act of faith into something auditable, which is the precondition for letting an agent near anything that matters. Meta’s benchmark figures sit in chart images rather than text, so treat those numbers with care. The logging design is the part worth copying.
Check whether your own agent runs produce a record you could hand to an auditor. A transcript in a chat window is not one.
How I built a five-member Excel team (Operating, John Brewton)
Brewton measured what happened when he set a single general-purpose agent to work on spreadsheets, and came back with two numbers. It got 89.69 per cent of individual cells right. It got 34 per cent of the answers right. Those two numbers describe the same runs. He rebuilt the work as five separate roles with divided responsibilities, on the argument that a plausible edit and a correct answer are different achievements.
Architecture: the gap between 89.69 and 34 is what compounding error looks like in a business process. A model that is right nine times out of ten per step is wrong most of the time across a chain of steps. Any workflow you are considering automating end to end has this arithmetic in it. Separating roles works because it inserts a check between the steps, not because the smaller agents are cleverer.
Count the dependent steps in the process you most want to automate. Raise your per-step accuracy assumption to that power, and see whether the result is a business you would run.
How we assure
Sandboxing (Zed)
From version 1.14 Zed sandboxes the agent panel’s terminal and fetch tools by default, for every user. Enforcement comes from the operating system rather than the application, using Seatbelt on macOS, Bubblewrap on Linux and WSL on Windows. Writes outside the project directory are blocked. Writes to the .git directory are blocked. Every network request is blocked unless the user escalates it.
Risk: a safe default is worth more than a safe option, because most users never change a setting. Zed also chose OS-level enforcement over its own checks, which means the guarantee survives an agent that has been talked into misbehaving. Note what is denied: git writes and all network egress. Those are the two capabilities that turn a compromised coding agent into a supply-chain incident.
Look at the agent tools your developers already run and ask which of them can reach the network by default. That list is your actual exposure, whatever the policy document says.
Shieldstral (Mistral)
Mistral’s own announcement says Shieldstral matches or outperforms open guard models up to seven times its size. The aggregator headlines circulating this week say it beats a 20 billion parameter safety model. Mistral names no such model and claims no head-to-head win over one. The hedge, “matches or”, is doing real work in the vendor’s sentence and disappears in the retelling.
Ethics: we keep finding the same failure, and it is not lying so much as compression. Aggregators strip qualifiers because qualifiers do not fit a headline, and the stripped version is what reaches the person making a purchasing decision. The vendors are mostly careful. The layer between the vendor and the buyer is not. Treating a newsletter item as a claim rather than a lead is how organisations end up procuring against numbers nobody stands behind.
Take the last AI claim someone forwarded you and find the vendor’s own wording for it. We do this daily, and roughly half the time the hedge has gone missing.