Fughetta对比
Fughetta 与常见替代方案的对比
另外三种给编程智能体提供工作场所的方式。每种都是合理的选择；区别在于当智能体、机器或网络出问题时，什么能保留下来。
| 方式 | 文件所在位置 | 隔离 | 丢失回复之后 | 取舍 |
|---|---|---|---|---|
| FughettaThis | Hosted or self-hosted | A worldline per agent | Receipts by operation ID | The source is the product; the gateway never runs your code. |
| A Git host plus an agent | A code host, then the agent's machine | Branches and worktrees | Whatever the agent reports | A good fit when the commit is the unit of work and a human reviews it. |
| A local MCP file server | The agent's machine | None by default | None by default | Nothing to deploy, and nothing between the agent and the directory it was given. |
| Fughetta, self-hostedSame product | Your own network | A worldline per agent | Receipts by operation ID | The same gateway, source and worker, with your configuration and your backups. |
如果每项变更在合并前都由人审查，一个 Git 托管加上笔记本上的智能体就足够了，Fughetta 只是多一跳。当多个智能体同时工作、运行它们的机器不是保存源代码的机器，或者丢失的回复必须读回而不能靠猜时，这一跳才有价值。