Contribute
Run a fleet
A fleet is several workers that run unattended. Workers coordinate through GitHub claims rather than through each other: a worker takes a lease on its job, and claims steer it away from work another operator has registered, so adding workers adds throughput rather than duplicate work.
The worker has a built-in manager. Describe the workers you want and it keeps them running, restarting any that fail:
tauceti workers add # worker1: the whole cascade
tauceti workers add reviewer --only review # a focused, named worker
tauceti workers # desired and actual state
tauceti workers logs --follow reviewer
To keep them running after you log out and across reboots, hand the manager to a user service (systemd on Linux, a LaunchAgent on macOS):
tauceti workers manager-stop --leave-workers
tauceti workers service install
To pay per token instead of by subscription, add --agent claude --claude-billing api --budget and grant a dollar budget with tauceti budget --grant 100; workers share it. Details in the workers documentation.
tauceti-fleet runs several workers unattended, optionally against a target list of roadmap milestones you want proved. Authors open pull requests for the next milestone, fixers answer review and repair CI, reviewers review other people’s pull requests in return, and the fleet reshapes itself from the backlog after every round. It starts in pilot mode, with one author, one fixer and one reviewer.
You need:
- A host. Ubuntu with Incus, so every round runs in an egress-denied container;
up.sandbox = "host"runs without one, which is fine for trying it out. - The GitHub account it acts as. Every GitHub request goes through a rate gate: set
gate.mutations_per_hourandgate.reads_per_hourinfleet.toml(40 and 600 by default) to keep the fleet under GitHub’s rate limits, and split them between fleets that share an account. - A Claude subscription or an API key. Codex is optional; it adds authors that use Codex first.
- A target list of milestones from the roadmaps, or
--targets none, in which case each author picks a roadmap area at random.
On a host prepared as in the setup guide:
tauceti-fleet init --name myfleet --targets targets/my_targets.md --github-login LOGIN
tauceti-fleet logins # one `claude auth login` line per login chain still missing
tauceti-fleet round # one supervised round first; read its log
tauceti-fleet up # then the fleet, in pilot mode
up starts in pilot mode (one author, sandboxed rounds) until you turn it off. tauceti-fleet attention collects everything that needs a human.