Microsoft relaunches Copilot as three-tab super app with Autopilot agent

By Splitfeed EditorialLast updated Sep 26, 2026, 19:06 UTC

On September 25, 2026, Microsoft officially launched a redesigned version of its Copilot app, restructuring it around three tabs: Home, Code, and Autopilot. The launch also brought a rebranding, with Scout, the AI personal assistant Microsoft had introduced at its Build 2026 conference, renamed Autopilot. The Autopilot agent is built on OpenClaw and is designed to run persistently in the cloud, meaning it can monitor Microsoft Teams channels and carry out tasks without requiring a user to actively prompt it each time. Alongside the interface changes, Microsoft announced a shift to usage-based billing for both the Autopilot and Code features, replacing the flat-rate pricing model it had previously used.

The billing change is arguably as significant as the product design itself. Microsoft's earlier approach involved subsidizing AI costs to attract users with predictable pricing, and moving to consumption-based charges signals that the company believes demand is now stable enough to pass variable costs more directly to customers. Microsoft has framed the redesigned Copilot app as potentially as influential as its Office suite, a comparison that sets a high bar and invites scrutiny. The central questions are whether an always-on autonomous agent integrated into workplace tools like Teams represents a genuine productivity shift, and whether usage-based billing will make the product more or less accessible to the businesses Microsoft is targeting.

Because no reactions from the Pro-AI, Anti-AI, or Middle Ground camps have been published yet, their likely positions can only be anticipated based on how each typically responds to stories of this kind. Pro-AI observers would be expected to highlight the Autopilot agent's autonomous capabilities as a meaningful step toward AI handling routine knowledge work, and to view the Office comparison as plausible given how deeply Copilot is embedded in Microsoft's ecosystem. Anti-AI voices would likely raise concerns about an agent that monitors workplace communications and acts independently, pointing to questions around employee surveillance, accountability when tasks go wrong, and the concentration of workplace infrastructure in a single vendor's AI stack. Middle Ground commentators would probably focus on the billing model shift, noting that usage-based pricing can produce unpredictable costs for organizations and that the real test is whether the productivity gains justify what users will actually pay.

The clearest near-term signal to watch will be how enterprise customers respond to the usage-based pricing once they have real billing data, and whether Microsoft publishes adoption figures or case studies that substantiate its Office-scale ambitions for the platform.