Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Install Fleet and build your first app

Before you start

Make sure Tailscale is installed and connected on this computer, and that you can edit DNS settings for your tailnet. Every device that opens your apps should accept Tailscale DNS settings.
Fleet runs on Bun 1.4 or later. If Bun isn't installed yet, the Fleet installer installs it for you automatically.
On Linux, 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.

1. Install Fleet

macOS and Linux:
curl -fsSL https://fleet.extoci.lol/install | bash
Windows (PowerShell):
irm https://fleet.extoci.lol/install.ps1 | iex
The installer verifies the release checksum, unpacks Fleet into ~/.fleet/runtime, adds the fleet command to your PATH, and installs Bun if needed. Re-running the same command updates Fleet in place.
Check that fleet is on your PATH:
fleet --version

Other ways to install

Want to install directly from the main branch instead of a tagged release?
curl -fsSL https://fleet.extoci.lol/install | FLEET_VERSION=main bash
Or clone the repository and link it with Bun:
git clone https://github.com/extoci/fleet.git cd fleet bun install bun link

2. Set up your gateway

Run setup on the computer you want to keep awake as your gateway:
fleet setup --install
Setup creates a private certificate authority for your installation, configures local HTTPS certificate trust, and registers Fleet to start automatically in the background. On macOS and Linux, setup asks for 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.

3. Add the tailnet DNS rule

Setup prints your gateway's Tailscale IP address. Open Tailscale DNS settings and add it as a restricted nameserver for the domain fleet:
  • Leave your existing DNS settings alone — only restrict fleet.
  • This is a one-time rule for your entire tailnet; every future app reuses it.
  • If your devices use an exit node, enable Use with exit node on this nameserver.
If 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.

4. Create and open your first app

Move to the folder where you keep your projects, then create a starter notes app:
fleet 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.

5. Let your coding agent edit it

Open the 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.
As soon as a file is saved, Fleet rebuilds the app with Bun and reloads any open browsers. If an edit fails to build, the last working build stays online and the error shows up in fleet logs notes.
fleet list --json fleet inspect notes fleet logs notes

Where next?

Work with your agent
Inspect apps, call server operations from the CLI, and verify edits cleanly.
Connect your iPhone
Scan a QR code once to open every .fleet app in Safari.
If an app won't load, check troubleshooting. To remove Fleet later, see removing Fleet.