October in review: the assistant moved into the browser
A month of one consistent theme, an anniversary, and a cloud outage that was more instructive than any of the launches.
October had a single direction running through it: AI stopped being a place you go and started becoming a layer over the places you already are.
The month in one line each
Apps and agent tooling inside the assistant, on the 6th. A smaller, faster model on the 15th. A cloud outage on the 20th that took down a long list of services. A browser with the assistant built in on the 21st. A corporate restructuring on the 28th that changes little for buyers.
The theme, and why it matters more than any single release
Three of those five are about placement rather than capability. The assistant is moving into the browser, into other software, into the flow of work — and each step makes it more useful and slightly harder to see.
This is why October’s posts kept returning to one question: what can it do without asking me? That question is becoming the main governance instrument available to a small company, and it works regardless of which product is in front of you.
The most useful thing that happened
The outage on the 20th, which cost a lot of people an afternoon and taught something no announcement could: most AI-assisted work has a manual fallback, and the short list where it does not is the only continuity planning a company your size needs.
Into November
Two things from this month carry forward. The one-page record from Tuesday, written before December while the reasoning is fresh. And the quarterly numbers from 3 October, to be repeated on 2 January.
This blog passed its first anniversary on the 13th. The most-read advice of that year remains the least technical: name the person who decides, and write down why.