fleet is a local tool that magically connects your development machines for ai coding.
one machine is the captain. the others get real .local names, passwordless ssh from the captain, persistent themed tmux sessions, and ai agent integrations.
fleet also gives agents a skill that tells them which machines exist and how to reach them.
fleet only handles the computers. your coding tools decide what work happens on them.
install or update to the latest release:
curl -fsSL https://extoci.lol/fleet | bashthe installer downloads the correct binary for macos or linux, verifies its checksum, and puts fleet in a writable user directory on your PATH when possible.
on the computer you want to use as the captain:
fleet initon another computer on the same trusted network:
fleet joinback on the captain:
fleet status
ssh machine.localthat ssh connection opens or reattaches to a tmux session named fleet, so closing your laptop does not also close whatever was running on emerald.
the machines get different terminal colors so you can easily tell where you're connected, at a glance.
the bottom-right of the Fleet tmux status bar shows the current whole-machine CPU and memory percentages. The values refresh every few seconds and fall back quietly if the operating system cannot provide a reading.
view a fleet-wide coding-agent usage summary, or include the full daily table:
fleet usage
fleet usage --allrun fleet without arguments or subcommands to view the full list of commands.
fleet is mostly an opinionated setup around things your computers already know how to do:
- mdns gives every machine a name like
emerald.local - ssh gives the captain passwordless access to members
- tmux keeps work alive between connections
- shell and tmux colors make it obvious which machine you are using
- a generated fleet skill makes the machine list readable by compatible coding agents
Fleet does not terminate or relay normal work after setup. ssh emerald.local, scp, sftp, and ordinary remote commands remain normal OpenSSH; Fleet's tiny local ProxyCommand only chooses the LAN or an already-connected Tailscale socket before OpenSSH performs its usual key exchange.
interactive ssh enters the persistent tmux session by default. bypass it once with:
ssh -t emerald.local 'NO_TMUX=1 exec "$SHELL" -l'fleet doctor --repair refreshes Fleet-owned shell and tmux files after an interrupted update.
fleet has no Fleet-hosted accounts, control plane, relay, or telemetry. its state and coordination stay local. when Tailscale is already installed and connected, Fleet can use the user's Tailnet for private remote reachability; Tailscale may use its own coordination service or DERP relays. installing fleet, system packages, codex, or claude code can obviously contact their official download sources.
captain discovery uses unauthenticated mdns. fleet join shows you the captain and its fingerprint before trusting it, which is trust-on-first-use for a trusted lan, not magic cryptographic proof that the person next to you is not doing something weird.
after joining, fleet pins machine identities and ssh host keys. registration and leave requests are signed with the pinned fleet identity.
fleet uses the operating system's openssh client for machine-to-machine commands. these commands are non-interactive, use the pinned fleet identity and host keys, send liveness probes, and have hard deadlines so an unreachable machine or stalled remote command cannot hang fleet indefinitely.
- macos or debian/ubuntu linux with systemd and apt
- bash or zsh
- machines on a trusted local network for initial joining
- one captain and one fleet per machine
fleet does optional Tailscale routing for members after their normal join or the next fleet update-all, while preserving ordinary ssh <name>.local; it does not install or administer Tailscale. Fleet also does not do task orchestration or Windows. it gives tools access to machines, it does not become the tool using them.
fleet was exclusively implemented by gpt-5.6 sol. it would've been impossible without it, due to its extremely impressive computer use capabilities across the network.
fleet was used in the development of fleet.
i wrote more on the blog post
most of the build scripts here are just documentation for my agents. i would recommend you ask your agents to explore the codebase, they'll pick up on everything.