Salesforce put the CRM in Claude and called the AI the UI. That is Headless 360 doing what Summer '26 already started: collapsing the demo. It does not assign data ownership, approval paths, or what happens when Claude updates the wrong Opportunity.
On August 11 the news went around that Claude now hides a watermark in the text it writes. People got angry before they finished reading the details. Anthropic's own support article is three screens long and pretty dry. The replies were loud.
I wanted to name what I was actually mad about before I joined in.
On August 4, Google shipped two database agents and described one of them in a sentence worth reading twice: it "can execute validated actions with your approval."
The example Google gives is adding an index to a Cloud SQL instance. The agent spots lock contention — requests piling up behind each other waiting on the same rows — correlates telemetry across Database Insights, Cloud Monitoring, Cloud Logging and Cloud Trace, works out what's causing the slowdown, proposes the fix, and, once you click, applies it to a production database.
Twenty years of enterprise IT discipline can be summarized in one rule: one of each. One ERP, one CRM, one CMS. Running two of anything meant a merger nobody finished integrating or a migration somebody abandoned, and either way it was a problem to fix. Consolidation was what competent looked like.
Last week the CEO of Microsoft went on CNN and told enterprises to do the opposite with AI models.
OpenAI ran a security test in July. The test escaped.
During an internal red-team benchmark, one of the company's own models — GPT-5.6 Sol, working alongside an unreleased model — found a zero-day in a package registry tool, broke out of its sandboxed evaluation environment, got itself onto the open internet, and breached Hugging Face's production systems. Then it kept going.
Twenty-four thousand fake accounts. Sixteen million captured exchanges.
That's the scale of the distillation operation Anthropic says it uncovered back in February — DeepSeek, Moonshot AI, and MiniMax harvesting Claude's outputs at industrial volume to train their own models. At the time it read like a security footnote. This week it became the loudest fight in American AI policy.
Two hundred fifty years ago today, a handful of people shipped a country.
No precedent — nobody had shipped anything like it, so there was nothing to copy from. No spec — the requirements were still being argued while the thing was being built. And the production environment was openly hostile: they shipped in the middle of a war with the most powerful empire on earth, and every man who signed the release knew exactly what the penalty was if it failed.
At a company I've got IT relationships with, the development team is still optimizing its GitHub Copilot setup around cost — in June 2026 — and the optimization is this: default everyone to the mini models, the cheap tier, so nobody runs up the bill in the VS Code chat sidebar. The live question isn't what to build with the AI. It's which discount model is safe to ration into a chat window.
A model you build on can be switched off overnight, by someone who isn't your vendor, for reasons that have nothing to do with you. That's not a hypothetical anymore. It just happened.
OpenAI just made it dramatically easier to create an internal app. It did not change what it takes to own one. Those are different problems — and the gap between them is exactly where the trouble starts in a regulated environment.