Microsoft brings chat, coding and agents together in a new Copilot app

One app to bring together different Copilot experiences

Microsoft wants to bring several Copilot experiences together in a single work app. As described in the available information, the idea is to put AI chat, coding tools and agents that can carry out tasks in one interface. The company has framed the project for both consumers and businesses, but that does not mean every feature will be available to both groups at the same time or on the same terms.

The strongest institutional indication among the sources provided comes from Microsoft’s fiscal 2026 fourth-quarter earnings call. There, Satya Nadella said Microsoft would bring Copilot experiences, including Code, together in a super app for consumers and businesses. That statement supports the product direction, but it does not in itself provide a launch specification covering timing, regions, requirements or a detailed feature list.

Reports published on September 25 described an updated version of the Copilot app that combines chat, code and agents. One report says Microsoft presented that version on that date. However, the verified sources available here do not include a specific official announcement that would allow us to confirm the rollout’s scope directly. It is therefore important to distinguish the strategy confirmed on the earnings call from presentation details attributed to Microsoft by secondary outlets.

The term “super app” describes an intention to bring capabilities together, not a guarantee that they will all be connected from day one. A shared interface may make features easier to find, but it does not show that an agent can use any app, that context is automatically shared between tabs, or that the same features are included with every account.

Chat, coding and agents: three capabilities, but not the same level of detail

Chat is the most familiar part: users can ask questions and request help through a conversation with the assistant. In a unified app, its value would also depend on how it interacts with the other tools. The sources describe bringing experiences together, but do not explain what information is retained between chat and the rest of the app or what controls users have over that context.

Coding appears under references to Code or coding tools. The earnings call confirms that this experience is part of what Microsoft intends to bring together. Some reports describe code-writing capabilities, but the documentation available here does not specify supported languages, environments, execution options, error-checking features or access conditions. It is therefore not possible to conclude that the app includes a complete development environment or that any user can run generated code from the same interface.

The third category is agents: systems assigned tasks, rather than simply asked to answer a question. The word “agent” does not, by itself, indicate a particular degree of autonomy. To understand what an agent in this app can do, users would need details about its permitted actions, the accounts and apps it can access, when it requests approval, and how it reports what it has done. The sources on the new app do not describe those permissions in sufficient detail.

A relevant precedent, which should not be confused with the new app, is Microsoft Scout. In a company post, Microsoft presented Scout as an always-on personal agent and described the Autopilots category in relation to identity, permissions and organizational policies. That post can help explain that Microsoft distinguishes agents from access controls. It does not, however, prove that Scout has been renamed Autopilot or that those features are incorporated unchanged into the announced Copilot app.

Access, Office integration and price: questions that remain open

The sources provided do not establish a reliable availability matrix by country, platform, account type or start date. Some coverage reports that a version was presented in September, but the information available here is not detailed enough to confirm which users receive it, whether access is being enabled gradually, or whether the consumer and organizational versions differ. Until Microsoft publishes specific terms, “launch” should not be read as meaning general availability.

Integration with Microsoft 365 is also unclear. Some reports mention Office or productivity tasks, but the institutional information among the sources does not list which Microsoft 365 apps are connected, what data agents may access, or whether integration depends on a license, an organization’s configuration or a gradual rollout. A unified interface does not automatically mean deep integration with Word, Excel, Outlook, Teams or other services.

The available sources also do not detail pricing or access terms. ZDNET’s coverage raises the question of whether the price is “evolving,” but the page could not be accessed directly during the verification process described in the source notes. There is not enough evidence here to say that the new app will be free, include paid features or replace an existing subscription. For businesses, it would also be necessary to distinguish the cost of the product from any licenses and services that individual features might require.

For an organization, an agent’s autonomy matters as much as what it can do. Microsoft has already described identity controls, permissions and organizational policies in the context of Scout and Autopilots. Applying those controls to the new app without specific confirmation would nevertheless be speculative. Before enabling automated tasks, administrators would need product documentation setting out minimum permissions, approval requirements, data scopes and audit mechanisms.

What to check before calling it a general launch

To interpret the presentation carefully, it helps to keep four stages separate: an announcement of intent, a product presentation, a rollout and general availability. The earnings call supports the view that Microsoft planned to bring the experiences together. Later reports describe a presentation of the updated app. Neither, on its own, establishes who can use it today or which features are active in each region.

It is also important not to treat product names and categories as interchangeable. A Microsoft post describes Scout as an always-on personal agent; in that post, Autopilots refers to a category associated with identity, permissions and policies. The verified sources do not confirm that Scout was renamed Autopilot or that this name applies to the unified app. Until there is an explicit statement, that connection should be treated as unverified.

The feature list calls for the same caution. Grouping chat, coding and agents together does not prove that they have the same maturity, access or integration. One experience may be available while another is limited to certain users, and an agent may require permissions that chat does not. The information provided also does not let us assess code quality, the reliability of automated tasks or time saved; those outcomes depend on tests and usage conditions that have not been described.

The most useful reference for following the story will be an official post specifying dates, markets, platforms and requirements, alongside administrator documentation on data access and agent controls. Pricing and Microsoft 365 integration will then need to be checked against the specific terms of each plan. Until then, what is confirmed is a strategy of unification and a presentation described by media reports; availability and operational details remain open.

Conclusion: unification announced, terms still need verification

The significant change is Microsoft’s intention to bring chat, coding and agents together in a shared Copilot experience for consumers and businesses. The earnings call supports that plan, and September coverage describes an updated version of the app. But the available evidence is not enough to present the product as a general launch with defined features and terms.

The practical question is not just whether the three capabilities appear under the same name, but what each can do, what data it uses, who has access and how much it costs. Until Microsoft publishes those details in a verifiable form, it is best to understand the new app as an announced product direction and to treat rollout, Office integration, agent permissions and pricing as unresolved.

Keep exploring

Corrections and transparency

If you spot incorrect or outdated information, send us a correction with the page and source we should review.