Your agents, from your terminal
One npm command starts an agent on any machine you own. The same CLI lists them with what each is working on, pauses and restarts them, and keeps the machine in line with the fleet you set in the web app.
Install once. It keeps itself in line.
One more command turns the machine into a steady part of your fleet: a system service that survives logouts and reboots and keeps the containers matching what you set in the web app.
build-server
It asks instead of failing
Start an agent that is already running and the CLI doesn’t error out or quietly skip it. It asks what you meant. Pick an answer.
worker is already running
Same command, three outcomes — you choose.
~/acme/app/models $ npx yatfa ps project: acme NAME STATUS AVAIL
Works from any folder
Run it from deep inside the project; it finds the project root on its own.
updater new agent version available updater updating worker ✓ worker on the new version
Agents update themselves
A small service on the host keeps agent containers on the current version.
$ npx yatfa ps --json [{"name":"worker","avail":"busy", "work":"AC-231"}]
Scriptable
Every listing has a machine-readable form for your own tooling.