Microsoft Pitches Copilot as the OS for Work
Satya Nadella hosted an intimate, invite-only meeting for leaders from key Microsoft business customers to pitch the rethought Copilot as the “OS for work.” The Verge
Microsoft is adding coding and agent features 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 merging its consumer and business Copilot apps into a single interface. Think of it like a workshop with three benches in one room. The redesigned app has separate tabs for chat, coding, and the Autopilot AI agent. That keeps everyday conversation, software work, and delegated tasks an agent runs on its own inside the same container, rather than in separate products or sidebars.
The management change behind the interface centers on Jacob Andreou. He was appointed in March as the single head of Copilot for business and consumer, reporting directly to Nadella. He is responsible for design, engineering, and growth. 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, software that can carry out multi-step tasks for a user, 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, with only basic upkeep, to focus on a cloud version renamed Autopilot. The cloud version runs on Microsoft servers rather than a user PC. Nadella favored the name Autopilot over Scout as more business-friendly. 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 Model means the AI system behind the answer. Form factor means the type of device.
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 turns that around. Office features move inside Copilot, coding moves inside Copilot, and agents sit beside chat in tabs.
In my view, that reversal matters more for company IT systems than for the demo. A single Copilot with shared login, permissions, and work history across chat, code, and agents cuts the integration work business tech teams otherwise carry. It also puts governance, record-keeping, and model routing in one place. Nadella's phrase about spanning every model points to that setup, where model choice becomes background detail rather than user choice.
Looking at what this means for practitioners, the tab design is worth attention. Separate tabs point to different ways of working and different safety rules, not one prompt box for everything. Chat happens live. Coding builds step by step around files. Autopilot means tasks handed off to run later in the cloud, not on the desktop as Scout first planned. For business buyers, moving from desktop test to cloud agent makes setup and rule enforcement easier, at the cost of making Copilot the control point for work that used to stay in local files and local coding tools.
Worth flagging as an open design question is how much Office strength survives inside Copilot. Full power implies more than file summaries, and more than opening Word or Excel elsewhere. For tech leaders, the test will be whether documents, spreadsheets, code, and agent results stay editable, traceable, and tied to permissions when they cross those tabs. If they do, Copilot starts to work like a base layer for office work. That result would make routine coordination cheaper and leave more room for work that needs judgment.
