Anthropic folds Cowork into chat and adds Docs and Slides
Anthropic stopped making people choose where work goes today, and Google opened the smart home to any agent that speaks MCP. One of those is a product decision, the other is an access decision.
Anthropic merged Claude chat and Cowork into a single product and shipped Claude Docs and Claude Slides inside it, ending the split between the assistant you ask questions and the one you hand work to. Cowork's agentic jobs — writing a report while you're away from your desk, building a deck, working from your connectors and skills — now start from any conversation, with Claude deciding what a task needs instead of the user picking a surface. Docs and Slides live at one shareable link, support simultaneous editing and comments, and export to PowerPoint. The rollout starts with Pro and Max on web, desktop and mobile over the coming weeks; Team and Free follow later, and Enterprise admins get 30 days' notice. By default Claude asks before acting.
The reason this lands is precedent. Cowork arrived as a separate app with its own memory model, and Anthropic's own explanation for the merger is that people kept telling it the frustrating part was deciding where a task belonged, and that work started in one place didn't carry into the other. That is the same failure OpenAI ran into with a stack of separate work surfaces, and it is the strongest argument against treating agents as destinations rather than capabilities. It also puts Claude directly on top of Google's Docs and Slides franchise for the casual case, which is the market worth having. We followed Cowork through its browser launches — Claude Cowork arrives in Chrome with skills and plugins — and the pattern holds: the interface keeps dissolving into wherever the work already is.
Google opened early access to an MCP server for Google Home, letting any MCP-capable agent — Claude, ChatGPT, Hermes, OpenClaw, Google's own Antigravity — control smart home devices, read event history and build its own dashboards. Setup means creating a Google Cloud project, handing the configuration to your agent, and approving permissions when it asks. It covers Nest doorbells and thermostats plus Matter and "Works with Google Home" gear, and supports cross-camera reasoning (what your kid did after school), device-state history (how many loads of laundry ran last week), voice updates through a Home speaker, and agent-built control panels.
The strategic read is bigger than convenience: Google is accepting that the assistant layer will not be its own. Google would not say whether access widens beyond the current tier or markets, which is the tell — this is an early-access concession, not a launch. The genuine trade-off is that a system reasoning across your cameras, thermostats and routines is far more useful than one that says it can't do that, and it holds a far richer picture of your home than any single vendor device did.
Half a year after Iranian drone strikes crippled its Gulf data centers, Amazon told customers it cannot restore some of their data at all — a region's worth of information now written off as permanently lost. The September 15 AWS dashboard update, first reported by Reuters and detailed by Ars Technica, states that AWS is "unable to restore access to the resources and data" in one of three availability zones in the United Arab Emirates and across all three zones in the Bahrain region. Billing in both regions stays suspended; the company promises UAE recovery updates in the coming months and a Bahrain assessment in early 2027, after strikes on March 1, a second wave on April 1, and a July missile attack on the last standing Bahrain structure confirmed by satellite imagery.
Multi-zone redundancy is the product cloud buyers are told to trust, and it did not survive contact with a state adversary — the damage exceeded what those services were built to absorb. For AI infrastructure the implication is less about AWS than about underwriting: the Gulf's compute build-out, Stargate UAE's 5-gigawatt campus included, was priced on cheap power and sovereign capital, not on missile risk, and insurers and customers now have a documented case of data that cannot be recovered at any price. We covered the first confirmation that the regions would not come back — AWS can't restore Bahrain and a UAE zone, six months after the drones — and today's update closes the question that was still open then: not whether the buildings come back, but whether the data does.
What to watch: whether Team and Free users get Docs and Slides on the same terms as Pro and Max, and whether Google Home's MCP access widens beyond early-access tier or quietly stays a developer toy.
Should a cloud provider be required to disclose when customer data is gone for good, or is the dashboard update enough? Tell us in the comments.
