A new model version passes its checks before anyone drafts with it.
Step 1 of 5: Reachable
Model connections, checked after every change.
A model connection is checked before first use and after every change.
Tool execution. It runs Before first use, and after changes. In the Agent Operating System, it runs every agent’s actions under your rules and carries long work to the finish.
A Friday change, caught before Monday.
A change can break a connection that worked yesterday. A check right after the change finds the fault before any work depends on it.
Step 1 of 5: The change
Friday 16:00: the HR team’s model is moved to a new account.
A bad change shows up in a check, not in someone’s work.
After a change, the connection is checked before it is used again, so a fault costs a check, not a morning.
Step 1 of 3: The change
New credentials are added for a model provider.
Only a connection that passes goes back to work.
A connection that fails its check stays out of use until it is fixed and passes.
Step 1 of 3: First use
A newly connected model is checked before its first call, and passes.
Runs model and tool calls under your rules.
Every model call and tool action runs once, after MS Duplex approves it, with credentials out of the model’s reach.
- A model call, approved first and run onceA model call runs once, after MS Duplex has approved it for that request.
- The same call, streamed as it is writtenAnswers appear as they are written, with the same rules applied.
- A tool action, exactly as approvedA tool action runs once, with exactly the arguments MS Duplex approved.
- Long tool runs, streamed and safe to cancelA long-running tool streams its progress and can be cancelled safely.
- Each model provider, with its own identityYour team connects each model provider with its own identity and credentials.
- Which model connections are healthyA failing model connection is spotted before it slows anyone down.
- Model connections, checked after every changeA model connection is checked before first use and after every change.
- Each tool, with its own permissions and riskEach tool is connected with its own identity, permissions and risk level.
- Which tools are connected and healthyA broken tool connection is visible before an agent depends on it.
- Tool connections, checked after every changeA tool connection is checked before first use and after every change.
See it on your own work.
From your own assistant to every agent your company runs, a pilot puts MS Duplex on your own work, with the measures agreed before it begins.