PATCHFLEET GUIDE
From one local project to a supervised agent team.
Patchfleet has two parts: the open-source Local host owns execution and durable truth; the optional Cloud account receives a strict sanitized projection and sends only typed, expiring intents.
1. Install and start Local
Use the current installation instructions in the public repository. Run patchfleet doctor, register a Git worktree with patchfleet workspace add ., and open the loopback console.
2. Choose ready agents
Inspect the built-in Orchestrator, Product, Design, Frontend, Backend, Full-stack, QA, Review, Security, Release, Docs, and Research packs. Custom packs are validated local JSON; they cannot load executable code or widen the provider sandbox.
3. Form a bounded team
Choose a template, one orchestrator, worker agents, concurrency, retries, time budget, approval gates, and failure policy. Local creates a dependency graph and starts only ready Codex work.
4. Pair Cloud
Create a one-time code in Cloud and enter it in Local. The Local host connects outbound. Cloud cannot open an inbound shell or read source, paths, prompts, transcripts, credentials, tool output, or provider responses.
5. Supervise and decide
Cloud shows host freshness plus sanitized team, agent, and task states. Supported actions are run/team/agent cancellation, a bounded release answer, an approval decision, and a bounded team start using an existing anonymous project alias and installed pack IDs.
6. Verify the receipt
A click is never displayed as success. Local revalidates the current revision and returns an applied, rejected, expired, or failed receipt. Cloud keeps short operational history; Local remains canonical.