Microsoft Copilot Home, Code and Autopilot: What Changed
Microsoft is rebuilding Copilot around Home, Code and Autopilot, adding AI app creation, persistent agents, Office integration and new controls for AI spending.
On this page
Microsoft rebuilt Copilot around three distinct jobs on September 25: finding your way through ongoing work, building software from natural-language instructions, and delegating tasks to an agent that can keep working without you. The new Home, Code and Autopilot experiences are arriving in stages rather than as an immediate upgrade for every Copilot user, but together they show a clear shift from AI that answers questions to AI that can create and operate work.
Microsoft Copilot now has three different ways to work
The redesigned Copilot is organized around Home, Code and Autopilot rather than treating chat as the center of everything. Home combines Copilot Chat with Cowork, Microsoft's experience for delegating larger jobs, while Code lets users describe applications and automations in natural language. Autopilot, previously called Scout, is the persistent agent that can continue working after the user has left the computer. Microsoft says Home and Code will begin rolling out through its Frontier program in the coming weeks, while Autopilot is scheduled to enter private preview at the end of September.
That separation matters because the three modes solve different problems. Chat is useful when the human needs an answer or draft immediately, Cowork is intended for work that can be delegated from start to finish, Code turns an idea into a working software solution, and Autopilot is designed for tasks that continue over time. Microsoft is effectively making the Copilot interface a dispatcher for several kinds of AI work rather than one chat box with an ever-growing list of commands.
Home puts chat, delegated work and Office in one place
Home is the new starting point for Copilot. Microsoft says it brings Chat and Cowork together so users can move between quick questions and larger delegated tasks without choosing a separate product. Home can also surface recent activity and suggestions, while the broader experience brings Word, Excel and PowerPoint directly into Copilot. That means a user can ask Copilot to create or modify an actual document, workbook or presentation rather than receiving text that must be copied into another application.
The practical difference is less about adding another chat feature and more about removing the handoff between conversation and the application where the work eventually lives. Microsoft says Office files remain synchronized with their corresponding Office applications, allowing teams to continue editing the same work. For someone preparing a customer briefing, for example, the workflow can move from asking Copilot to gather and organize material to producing an editable Word document without rebuilding the context manually.
Code turns natural-language requests into working software
Code is the part of the redesign that moves Copilot closer to an application-building environment. Microsoft says users can describe an app, tracker, dashboard or automation in natural language and have Copilot build the solution. The feature uses technology underlying GitHub Copilot and runs generated code in a sandboxed environment, while Microsoft says the resulting solutions can be hosted securely within an organization's tenant.
For non-developers, the important change is that the output does not have to stop at an explanation or a block of sample code. A person could describe the information they want to track and the workflow they need, then iterate on the resulting application. Developers still have reasons to use GitHub Copilot for traditional software development, but Microsoft is positioning Code as a way for more knowledge workers to create smaller business solutions themselves. That puts it closer to the same general territory as dynamic brief-driven agent building, although the new Code experience is aimed at turning natural-language requirements into executable applications and automations.
Managed Runtime is the safety layer behind Copilot Code
Generating software is only half the problem in an organization. Someone still has to decide where that software runs, what data it can access, how it is shared, and which security policies apply to it. Microsoft introduced Copilot Managed Runtime alongside Code as an enterprise hosting environment for applications created through Copilot, with the service running inside the Microsoft 365 tenant boundary and remaining subject to IT governance.
Microsoft says Managed Runtime is now in public preview and is intended to handle some of the operational work that normally follows application creation. The company describes capabilities for sharing applications, connecting them to live data and controlling them through organizational governance. That does not eliminate the need for security review, but it changes where that review happens: instead of every employee improvising a separate deployment path for an AI-generated app, administrators can govern the execution environment centrally.
Autopilot is the biggest change because it keeps working
Autopilot is the most substantial departure from ordinary chatbot behavior. Microsoft describes it as a cloud-hosted personal agent with its own identity, memory, computer and workspace. A user gives it a name, role and goal, and it can continue following up on work, monitor conversations, perform recurring tasks and resume projects later without waiting for another prompt.
Microsoft's example is a supplier-review process. Instead of asking Copilot one question at a time, a user could give Autopilot the objective and boundaries, after which the agent could prepare a schedule, handle meeting preparation, follow up with participants and request updates. Because the agent operates in the cloud, the work can continue while the user is away from the computer. Microsoft says Autopilot will appear in places such as Teams, Outlook, chats, channels and documents, with permissions, auditing and governance behind it.
That also creates a new boundary for users to think about. A chatbot normally waits for the next instruction, so the human decides when another action should happen. A persistent agent can decide that an action is due based on the objective it was given. The useful question therefore becomes not simply whether an agent can complete a task, but whether its permissions, memory and operating boundaries are narrow enough for the task it has been trusted to perform.
Microsoft is adding spending controls because agentic work costs differently
The new Copilot also changes how Microsoft describes AI consumption. Microsoft says ordinary Copilot use remains associated with a user subscription license, while agentic capabilities such as Cowork, Code and Autopilot can use usage-based billing. In that model, organizations can control which models are available and monitor the credits consumed by AI work rather than treating every operation as an identical request.
This is an important distinction because an agent that runs a multi-step process can consume substantially more computing than a single question-and-answer interaction. Microsoft's new FinOps for AI features are intended to give administrators visibility into that spending, including policies for model access and controls around usage. Microsoft says cost management is expanding to Code and Managed Runtime, with support for agents built in Copilot Studio planned for October.
The rollout is gradual, so the new Copilot may not appear yet
Seeing the announcement on September 25 does not mean every Microsoft 365 user can open Copilot and immediately find all three experiences. Microsoft says Home and Code are rolling out through the Frontier program in the coming weeks, while Autopilot is moving into private preview at the end of September. Code is also planned for preview for Microsoft 365 Premium and Pro subscribers later this year.
Microsoft is also previewing a feature called Today inside Home. It is designed as a proactive command center for email, calendars, Teams conversations, meetings and tasks, surfacing missed work and actions that need attention. Microsoft says Today enters private preview in October and is planned for Outlook and Teams as well. Another planned capability will let users invoke Copilot inside Teams with the shared context and permissions of the relevant channel, chat or meeting.
The real change is the move from answering to operating
Microsoft's September update is easier to understand when the three pieces are viewed as a workflow rather than three separate features. Home is where a user starts and decides what needs doing, Code can turn a described requirement into a working solution, and Autopilot can keep a longer-running objective moving after the initial instruction. Managed Runtime supplies an enterprise execution layer, while spending controls give administrators a way to monitor the additional computing that agentic work requires.
The rollout will determine how much of that vision becomes useful in everyday work. For now, the important distinction is between what Microsoft announced and what users can actually access: the new architecture is public, but several of its most significant pieces remain in preview or staged rollout. The next test is not whether Copilot can generate another impressive demo, but whether people can safely hand it a real piece of work and get back a result that is worth the cost, review time and permissions involved.
Share this post
Written by



