fleet setup --install targets Debian and Ubuntu systems with systemd and update-ca-certificates. macOS and Windows setup paths are included as well; see troubleshooting if your OS uses a different service or certificate store.1curl -fsSL https://fleet.extoci.lol/install | bash
1irm https://fleet.extoci.lol/install.ps1 | iex
~/.fleet/runtime, adds the fleet command to your PATH, and installs Bun if needed. Re-running the same command updates Fleet in place.fleet is on your PATH:1fleet --version
main branch instead of a tagged release?1curl -fsSL https://fleet.extoci.lol/install | FLEET_VERSION=main bash
1234git clone https://github.com/extoci/fleet.git cd fleet bun install bun link
1fleet setup --install
sudo once to install the root-owned port helper for ports 443 and 53; the Fleet daemon and your apps always run as your normal user. On Windows, setup registers a scheduled task under your account and prompts for administrator approval to add Tailscale firewall rules.fleet:fleet.FLEET_TAILSCALE_TOKEN (with the dns scope) is already set in your environment, fleet setup configures this rule for you automatically without overwriting any conflicting rule.12fleet init notes fleet open notes
fleet init notes creates a notes folder containing a working Preact client, server operations, fleet.json, TypeScript definitions in fleet.d.ts, and agent instructions in AGENTS.md. To initialize inside an existing folder instead, run fleet init --name notes — Fleet never overwrites existing source files.fleet open notes signs your local browser in through Fleet Gate and opens https://notes.fleet.notes folder with your coding agent and ask it to read AGENTS.md before making a change. Your agent edits files directly — it should not start Vite or another dev server.fleet logs notes.123fleet list --json fleet inspect notes fleet logs notes