Big Tech

Microsoft’s Copilot Is Getting an Agent That Works While You Sleep

Microsoft Copilot AI agent multitasking on a laptop, reading mail, mixing food and feeding a dog while a person sleeps.
Microsoft is giving Copilot an AI agent designed to keep working in the background, handling multiple tasks while the user sleeps.

Microsoft Copilot Autopilot is designed to keep working after the user has walked away. Microsoft says the agent can be given a name, role and goal, continue long-running tasks in the cloud, and return to a project days later without needing the entire job explained again.

The company describes it as a digital teammate rather than a one-off chatbot. It can appear in Microsoft environments such as Teams and Outlook, use its own workspace and memory, and continue recurring work while the person who set the task is asleep or doing something else.

That is a bigger behavioural change than another chatbot interface. The question shifts from whether Copilot can answer a prompt to whether organisations are comfortable assigning an AI worker an ongoing job.

What Microsoft Copilot Autopilot is meant to do

Microsoft says Autopilot is the new name for a system previously known as Scout. It is intended for work that unfolds over time rather than a single request. A user might give the agent an objective, let it watch relevant channels or documents and ask it to continue a recurring process without starting from scratch each day.

The company says the agent has its own identity, memory, computer and workspace. Those phrases should not be mistaken for human independence. The agent still operates inside permissions, governance and audit controls set by the organisation, and its capabilities depend on the systems it is allowed to access.

A second Microsoft announcement describes the same new Copilot line-up, including Home, Code and Autopilot. Autopilot is expanding in private preview at the end of September rather than launching to every Copilot user at once.

Why working while you sleep is not just marketing language

Traditional assistants wait. They respond when a user opens the interface and asks a question. A cloud-based agent can instead keep a process alive between interactions. That could mean monitoring a project, preparing material for the next morning or continuing a task that takes longer than one chat session.

The attraction for businesses is obvious. Work that previously stopped when an employee stopped typing can continue in the background. The risk is equally obvious: an error can also continue in the background unless the system has sensible limits, permissions and checkpoints.

That makes agent design less like giving an employee a clever search box and more like configuring a junior digital operator. The important controls become what the agent may access, which actions require approval and how a human can see what it has done.

The agent still needs a human boundary

Microsoft says Autopilot is designed to fit within enterprise security and governance. That is important because a persistent agent can accumulate context and touch multiple systems. The more useful it becomes, the more damaging an excessive permission or misunderstood instruction could be.

The basic principle should be familiar from ordinary IT administration: give a system only the access it needs. A sales agent does not automatically need payroll data. A research agent should not be able to send external messages merely because it can read internal documents.

LiveAIWire has previously covered the move towards assistants that cross app boundaries. Autopilot extends that idea from moving between apps during one task to maintaining work over time.

Copilot is also becoming a place to build software

The broader Copilot update includes a Code experience intended to help users create applications with natural-language instructions. Microsoft is effectively bringing together three roles: a home screen for work, a coding environment and an agent that can continue tasks without constant supervision.

Those roles will appeal to different users, but they point in the same direction. The chat window is becoming less important than what the system can do after the conversation. A successful agent will be judged by completed work rather than by how eloquent its response looks.

That changes costs as well. Microsoft says long-running agentic work can involve usage-based billing. Businesses will have to think about the cost of letting an agent continue processing in the same way they already think about cloud computing or API usage.

Why this matters for ordinary office work

The near-term use cases are likely to be repetitive rather than dramatic. An agent might prepare a morning summary, keep a project status document current, chase information from approved internal sources or organise work that would otherwise be rebuilt at the start of every session.

LiveAIWire has reported on how workers are already spending money and time on AI tools for work. Persistent agents raise the stakes because the tool becomes part of the workflow rather than something an employee consults occasionally.

For users, the best test will not be whether Autopilot sounds intelligent. It will be whether people can hand it a bounded responsibility, inspect what happened and recover quickly when the system misunderstands the job.

The important word is preview

Microsoft is presenting Autopilot as a significant part of Copilot’s future, but it is not yet a universally available digital employee. The expanded private preview gives the company and participating organisations a chance to test how persistent agents behave before wider deployment.

That distinction matters because the hardest agent problems often appear outside demonstrations. Permissions interact, documents change, instructions conflict and organisations discover that a task described as routine contains more human judgement than expected.

The idea of an AI that keeps working while its owner sleeps is easy to understand. The practical success of Microsoft Copilot Autopilot will depend on something less glamorous: whether companies can make that persistent work predictable, visible and controllable.

About the Author

Stuart Kerr is Technology Correspondent at LiveAIWire, covering artificial intelligence, cybersecurity and the social impact of emerging technology. LiveAIWire is an independent, human-led technology publication using AI-assisted research, editorial production and original AI-assisted editorial illustrations under his direction.