3DNews AI→ original

Microsoft taught Copilot Researcher to cross-check GPT and Claude answers in a single process

Microsoft has begun implementing Critique mode in Copilot Researcher: now a research answer can be prepared by GPT, with Claude checking it for accuracy…

AI-processed from 3DNews AI; edited by Hamidun News
Microsoft taught Copilot Researcher to cross-check GPT and Claude answers in a single process
Source: 3DNews AI. Collage: Hamidun News.
◐ Listen to article

Microsoft has begun implementing a Critique mode in Copilot Researcher, where two models work simultaneously on a single research answer — OpenAI's GPT and Anthropic's Claude. In parallel, the company has launched the rollout of a new AI-agent Copilot Cowork, demonstrating that Copilot is increasingly transforming from a single assistant into a set of coordinated helpers.

How Critique Works

The Critique scenario is straightforward: one model first prepares a draft answer to a user's request, and the second then checks it for accuracy. In the first phase, GPT answers, while Claude acts as an internal reviewer. For a research assistant, this is more important than it may seem: in search, summarization, and analytics tasks, the challenge is usually not to quickly write text, but to catch weak points, imprecise wording, and questionable conclusions before the result reaches the user.

Microsoft is already talking about the next step: they want to make the process bidirectional so that models can swap roles. That is, not only will Claude critique GPT's answer, but GPT will also be able to check Claude's drafts. Essentially, the company is assembling a mini-editorial process within a single workflow, where generation and verification are separated.

This is a notable shift for corporate AI: the bet is not only on the strength of a single model, but on how they argue, check each other, and increase the reliability of the final answer.

Why This for Microsoft

For Microsoft, this is also a way to transform having models from different vendors into a practical advantage, rather than just a long list of compatibilities. Previously, multi-model approaches often sounded like a formal plus: the client gets a choice between several engines, but each task is still performed by one of them. The logic here is different — models start working together and cover each other's weaknesses directly within a single scenario.

This approach especially fits well with Microsoft 365, where Copilot is expected not as an experiment, but as a predictable result in real documents, spreadsheets, and research.

In practice, this approach provides several tangible benefits.

"Customers should receive not a set of models, but the benefit of their joint work," — this is how

Microsoft describes the idea of the new mode.

  • more careful answers to research queries thanks to a separate verification stage
  • less dependence on the strengths and weaknesses of one specific model
  • a more understandable workflow where generation and critique are divided by role
  • a foundation for future scenarios where multiple models debate each other before delivering results

Microsoft is not yet promising the magical disappearance of errors, and this is the right position. One model checking another does not automatically guarantee truth: both systems can make mistakes, agree with an incorrect premise, or miss problematic areas. But even this scheme is already better than a single answer without internal control, especially in products where the result then goes into work correspondence, presentations, or analytical notes in company workflows.

Cowork Launches in Parallel

At the same time, Microsoft has begun rolling out Copilot Cowork — another AI-agent in the Copilot ecosystem. The original note contains few details about its functions, but the timing itself is important: the company is showing not just one local feature, but a broader transition to a set of specialized agents and modes of operation.

Researcher handles research scenarios, Cowork expands the lineup, and the combination of different models within a single process hints at where Copilot will go next. If previously a corporate assistant was mostly perceived as a single chatbot, the architecture is now becoming modular. One agent can gather material, another verify it, a third help with team collaboration. For Microsoft, this is a convenient way to scale Copilot without promising a universal super-agent that is equally good at everything.

Instead, the company is assembling a more practical system: separate roles, separate processes, and more control over result quality at each stage.

What This Means

Microsoft is moving Copilot toward a multi-step AI system where answer quality increases not only through a stronger model, but through internal verification. For the market, this is an important signal: the next competition in corporate AI will take place not only between GPT, Claude, and other models, but between entire workflows in which these models interact.

ZK
Hamidun News
AI news without noise. Daily editorial selection from 400+ sources. A product by Zhemal Khamidun, Head of AI at Alpina Digital.

Want to stop reading about AI and start using it?

AI News is a curated feed of AI/tech news. Hamidun Academy teaches you to use AI systematically in your work.

What do you think?
Loading comments…