Microsoft Rebuilds Copilot as OS for Work With Coding, Office and Autopilot
Satya Nadella hosted an intimate, invite-only event for leaders from key Microsoft enterprise customers to pitch the Copilot rethink as the "OS for work." The Verge
Microsoft is adding coding and agent capabilities directly into Copilot. It is bringing the full power of Office into Copilot for the first time. The pitch is consolidation. One surface, three modes.
The company spent the past few months fusing its consumer and enterprise Copilot apps into a single unified user interface. The redesigned app has separate tabs for chat, coding, and the Autopilot AI agent. That structure keeps conversational assistance, development work, and delegated agent execution inside the same container, rather than in separate products or sidebars.
The organizational change behind the interface centers on Jacob Andreou. He was appointed in March as the single head of Copilot across commercial and consumer, reporting directly to Nadella. He is responsible for the design, engineering, and growth of Copilot. Andreou joined Microsoft AI last year focused on product and growth. Separately, Charles Lamanna leads Microsoft's Copilot, Agents, and Platform (CAP) team.
On agents, Microsoft announced Scout at its Build developer conference in June as a desktop preview app. Microsoft has since put that Scout desktop app into maintenance mode to focus on a cloud version rebranded to Autopilot. Nadella favored the name Autopilot over Scout to present Microsoft's AI agent in a more enterprise-friendly way. In a post on X, Nadella said Microsoft is building Copilot as "a new OS for work that spans every model, every form factor, and every task." The Verge
The broader context here is a reversal of where Copilot lived. Until now, Copilot largely lived inside Office, inside the browser, or inside developer tools. This plan inverts that relationship. Office capabilities move inside Copilot, coding moves inside Copilot, and agents run alongside chat in tabbed proximity.
In my view, that inversion matters more for IT architecture than for the demo. A single Copilot with shared identity, permissions, and work context across chat, code, and agents reduces the integration work that enterprise teams otherwise carry. It also concentrates questions of governance, audit, and model routing in one place. Nadella's phrase about spanning every model points to that abstraction, where model selection becomes infrastructure detail rather than user choice.
Looking at what this means for practitioners, the tab design is worth attention. Separate tabs suggest distinct interaction patterns and safety boundaries, not a single prompt box for everything. Chat is synchronous. Coding is iterative and artifact-driven. Autopilot implies delegated, asynchronous execution in the cloud rather than on the desktop that Scout originally targeted. For enterprise buyers, the shift from desktop preview to cloud agent simplifies deployment and policy enforcement, at the cost of making Copilot the control point for work that previously stayed in local files and local IDEs.
Worth flagging as an open design problem is how much Office fidelity survives inside Copilot. Full power implies more than file summarization, and more than launching Word or Excel elsewhere. For technology leaders, the useful test will be whether documents, spreadsheets, code, and agent outputs remain editable, traceable, and permission-aware when they cross those tabs. If they do, Copilot starts to function like an operating layer for knowledge work. That outcome would make routine coordination cheaper and leave more room for work that actually requires judgment.
