Connect it once. MS Duplex joins every step.
Connect the agents your company builds through MCP, and the hooks bring MS Duplex in at every step: before each request, before each tool call and after each result. MS Duplex becomes the Agent Operating System they run on, and they learn, plan, simulate, decide and act within your rules.
You start with a pilot on your own work, with the measures agreed before it begins.
Where MS Duplex changes how your agents work.
Step 1 of 4: A broken rule
How you start with MCP + hooks.
From the pilot to every agent working under your rules, in three steps.
Step 1 of 5: What you need
Start from what you already have: The agents your company builds, on the models you choose.
Shared knowledge across your agents.
A correction your team confirms with one agent reaches every agent you build.
Step 1 of 3: One agent
What one agent did, and everything around it.
Carry every confirmed result across all your agents.
You start with a pilot on your own work, with the measures agreed before it begins.