Runtime intelligence,
where your AI work happens.
Start in your own assistant: MS Duplex reaches you through MCP in Claude, Codex, Cursor and Hermes. Then bring it into every agent your company builds, through MCP + hooks.
You start with a pilot on your own work, with the measures agreed before it begins.
Where your team works.
How MS Duplex joins each step.
Your assistant stays in charge, and brings MS Duplex in.
Step 1 of 3: Your assistant
What MS Duplex brings, in every connection.
The same four things in Claude, Codex, Cursor, Hermes and MCP + hooks.
Step 1 of 4: A result confirmed
Once your team confirms a correction, MS Duplex applies it the next time it fits, in any wording.
One intelligence, whichever agent you use.
Claude, Codex, Cursor and Hermes and your own agents draw on the same MS Duplex. Change the client, the model or the provider, and the work carries on as one.
One Agent Operating System beneath all of them: the same context, rules and history, whichever assistant or agent does the work.
Agents that stay themselves →Why MS Duplex is an Agent Operating System →Step 1 of 5: Session ends
The work starts in Claude Code. When the session ends, the goal, the decisions and the constraints stay.
The first three steps.
The first win is a confirmed correction, applied the next time it fits.
- 01
Choose where the work happens
MS Duplex in Claude, Codex, Cursor or Hermes, or in your company’s own agents through MCP + hooks.
- 02
Give it a head start
Pretrain MS Duplex on the examples, decisions and documents you already trust.
- 03
Keep working as usual
Confirm what worked. Every session starts further ahead.
One console across all five.
Your team keeps the final say over what MS Duplex learned.
Step 1 of 4: Review
Everything MS Duplex learned, with the agent and model it came from, and when.
Each team in its own work area.
What MS Duplex learns in a work area serves the people in it, and stays there.
Step 1 of 4: An area each
Each team works in its own area, and what MS Duplex learns there serves the people in it.
Where it runs.
Every connection works in MatterSpace Cloud and in your cloud. Choose one to see it.
Integration and portability.
One foundation for every agent, app and model you use.
Step 1 of 4: Your assistants
MS Duplex works inside the assistants your team already uses.
Start where the work already happens.
You start with a pilot on your own work, with the measures agreed before it begins.