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 只是多一跳。當多個代理程式同時工作、執行它們的機器不是保存原始碼的機器，或者遺失的回覆必須讀回而不能靠猜時，這一跳才有價值。