Archfleet is the newest product in the suite and is in active development. This
page describes the shape of the tool; install and configuration docs land with
the first tagged release. Follow
perceo-ai/archfleet for progress.
The problem it solves
Computer-use agents need a real desktop — a window manager, a browser with a profile, a file picker, a login session. Giving one your actual machine is not something you want to do twice. Archfleet gives each run its own VM instead. The agent gets a full desktop; you keep yours.How it works
1
Draw the workflow
Define what the agent should accomplish as a workflow rather than a single
prompt, so a long task has structure the runner can follow and you can inspect.
2
Run it on an isolated VM
Each run gets its own libvirt guest. The agent has a real desktop with real
applications, and nothing it does touches the host.
3
Driven by Agent S
Agent S is the computer-use harness — it does the perceiving and acting inside
the guest. Archfleet owns everything around it: VM lifecycle, workflow
definitions, scheduling across the fleet, and run history.
4
Take over when it stalls
Connect to the guest over XRDP and drive it yourself. Computer-use agents get
stuck, and the useful answer is a working remote session, not a failed run.
Where it sits in the suite
Archductor produces the change. Archfleet is where you find out whether the change actually works when a human-shaped user drives the product. The same isolation principle applies in both: one task, one environment, one reviewable result. In Archductor that unit is a workspace; in Archfleet it is a run.Requirements
Archfleet runs on your own hypervisor host. You will need libvirt/KVM with enough capacity for the guests you intend to run in parallel, guest images with a desktop environment and XRDP, and model access for Agent S.Exact version requirements, the install path, and the workflow schema are
pinned with the first release. Nothing here is a supported API yet.