个人计算结构：在你拥有的机器间安排AI代理的工作和任务。大脑留在家里。
概览
Wefty是一个个人计算结构，用于在你拥有的机器间调度AI代理工作和其他作业。控制平面和节点代理将Mac、Linux服务器，最终的提供者容量整合成一个标签路由的作业队列，而工作流账本则记录运行、日志、切换和门。 关于单一本地节点的背景工作和分支门的配方，请参见 wefty 技能。 大脑留在家里：控制平面、运行账本、状态和历史总是运行在你的机器上，包括你直接租用的云机。托管代理系统将大脑放入服务中并发送你的代码;Wefty则将信任边界保留在你的集群内部。未来的云服务可能会提供连接或容量，但它们不会托管控制平面。 所有网络访问都被 Fabric 接缝隔离。L3 从不直接派遣到节点，L1 仍然是唯一的作业队列。请参见 v1 设计中的架构和构建顺序。
概述（AI 翻译）
Wefty是一个用于调度AI代理工作和其他任务的个人计算结构 跨越你拥有的机器。控制平面和节点代理推动Mac、Linux 服务器，最终将提供者容量整合到一个标签路由的作业队列中，同时 工作流程账本记录运行、日志、交接和门。
关于单一本地节点的背景工作和分支门的配方，请参见 wefty 技能。
大脑留在家里：控制平面、运行账本、状态和历史永远存在 运行在你的机器上，包括你直接租用的云端机器。托管 代理系统将该大脑放入服务中，并发送你的代码;WEFTY 保持 集群内部的信任边界。未来的云服务可能会提供 连接性或容量，但它们不会承载控制平面。
预发布。v0.1单机循环已被标记，OCI工作负载也已发布;目前还没有兼容性承诺。
建筑一览
| 图层 | 角色 | 它的作用 |
|---|---|---|
| L1：集群 | 调度与执行 | 运行控制平面和节点代理，然后通过拉取队列通过标签路由作业。 |
本页由 AI 翻译，技术细节请以原文为准。
README
以下为原文 README 节选，完整内容请查看原文。
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
| Layer | Role | What it does |
|---|---|---|
| L1: cluster | Scheduling and execution | Runs the control plane and node agents, then routes jobs by tags through a pull-claim queue. |
| L2: connectors | External capacity | Will present providers such as Daytona and Fly through the same scheduling model as owned machines. |
| L3: workflow ledger | Runs and coordination | Stores workflows, run lineage, envelopes, gates, artifacts, and logs; submits all work through L1. |
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.
推荐工具
换一个关键词，或者移除筛选条件。
安装
npx skillfish add derek-x-wang/wefty