wefty

Wefty is a personal compute fabric for scheduling AI agent work and other jobs across machines you own. A control plane and node agents turn Macs, Linux servers, and eventually provider capacity into one tag-routed job queue, while a workflow ledger records runs, logs, handoffs, and gates.

For background work on a single local node and the branch-gates recipe, see the wefty skill.

The brain stays home: the control plane, run ledger, state, and history always run on your machines, including cloud machines that you rent directly. Hosted agent systems put that brain in a service and send your code to it; wefty keeps the trust boundary inside your cluster. Future cloud services may provide connectivity or capacity, but they will not host the control plane.

Pre-release. The v0.1 single-machine loop is tagged, and OCI workloads have shipped since; nothing is a compatibility promise yet.

Architecture at a glance

All network access is isolated behind the Fabric seam. L3 never dispatches directly to nodes, and L1 remains the only job queue. See the v1 design for the architecture and build order.

Daily installation: wefty setup

For a fresh fleet control-plane Mac or Linux machine, build the four binaries below and run wefty setup --role control-plane. Setup prompts without echo for four separate single-use keys: L1, L3, node agent, then client. Make agent keys immediately before use with a short expiry. Enrolment shows progress and stops after 15 minutes per participant. Rerun setup to resume; it keeps saved participants and asks only for unsaved participants’ keys. A completed fleet rerun needs no keys. Keep both private staging files for resume. Missing resume records, unrecorded participant folders and coordinator conflicts refuse before any key. After commit, setup refuses profile edits; use wefty upgrade for binary replacement.

Fleet setup prints bounded readiness checks and runs a short pinned one-shot smoke test by default (--skip-smoke-run marks it NOT-RUN). A readiness failure keeps the installation published: repair the cause and rerun setup. Both fleet roles check L1 ↔ L3 reachability through the service-owned peer probes. wefty doctor --print-policy prints the private-network policy snippet.