How it works · Acme walkthrough
Uninstall Chrome on a Windows endpoint, with a human still in the seat.
In the Acme walkthrough, an operator acts as a responsible fleet custodian needing to remove Google Chrome from an Acme Corp Windows workstation (CAKE-PC). In Cohort 01, that kind of mutating work lands in Actions for approval before the agent runs, giving caretakers complete control and an audit trail to hand off cleanly.
The path
Four steps from request to handoff.
- 01
Request
An MCP client (or an operator) queues a mutating command against the Acme Windows endpoint, here, winget uninstall of Google Chrome on CAKE-PC. It does not run yet.
- 02
Review
On Actions, a human reads the payload, target, and risk. Approve & run dispatches immediately; Reject stops the work and keeps the record.
- 03
Execute
The Windows agent runs the approved command on the endpoint. Output comes back on the same action, exit code, stdout, and status.
- 04
Audit
The timeline shows created → approved → dispatched → completed, so the next person on the ticket is not starting from scratch.
winget uninstall --id Google.Chrome --exact --silent --accept-source-agreements --disable-interactivity
Same console, Windows agent
See the machine, then act with accountability.
Operators can open Remote Console on the Windows endpoint when they need eyes on the desktop, then use Actions for commands that deserve a second look. Governance sets four-eyes defaults and when self-elevate is allowed.
Boundary
Not autonomous remediation.
This story is operator-guided work with human approval, not unattended self-healing, monitoring-led remediation, or fleet-wide uninstall automation as a Cohort 01 promise.
Agents and MCP clients can propose and queue work; consequential commands still meet a person on Actions before they run on the endpoint.
Next
Walk this path with your own ticket queue.
Book a demo to see the remote console and approval plane, or apply for Cohort 01 if you want a structured pilot.