IT Fulfilment Agent
The IT Fulfilment Agent is the hands behind the support desk. It carries an approved IT request out in a real admin console — assign or reclaim a licence, reset MFA, add someone to a group, disable a leaver — and attaches the evidence.
At a glance
| Handle | @it-fulfilment |
|---|---|
| Availability | Seeded in every organisation |
| Model tier | default |
| Autonomy | supervised — every write pauses for a person |
| Tools | browser_use — the only built-in that declares it |
| Max turns | 16 |
| Egress | Default-deny. One seeded allow for the demo console; an admin adds their own hosts. |
How it works
It drives a browser. Reads flow through — navigate and
extract run immediately, and extracted text is DLP-screened before
the model sees it. Writes do not: click, type,
submit and download go through the
approval gate and execute exactly
once. Every operation records a browser-recording.json artifact on
the run.
-
Look before acting
It opens the console and reads the current state first — which licence the person holds, whether the account is already disabled — so the approver sees what is actually there rather than an assumption. -
Propose one change, and wait
Each write is described and parked. The approver sees the operation, the target and the page it will act on, may edit the arguments, and approves. -
Attach the evidence
The recording, and optionally a full-page screenshot per step, land in the run's artifacts beside the trace.
browser_egress
policy; the seeded allow covers the demo
console only, never *.
Screenshots are opt-in. A screenshot is un-redactable pixels —
safe on a fake demo console, not on a real tenant — so capture is off unless an
administrator turns it on.
Signing in
The agent never types a password. It works from a browser session an administrator has already established for it, which is why the demo console is login-less: credentials are not something a conversation should hold. See Browser actions for the full model.