Documentation
Install Agent Fleet
Install on every machine you want in the fleet. Free works on one local network; Plus adds delivery across networks.
1. Install
Run the command for your operating system. It installs am for messages and files, af-ctl for machine administration, the imclaude and imcodex session launchers, the af-ctld and af-msgd background services, and the af-statusline helper.
macOS or Linux
Windows PowerShell
Linux is available for x64 systems and requires a working systemd user session. Ubuntu 24.04 LTS is the verified target; containers without a systemd user session are not supported.
2. Set up this machine
Choose whether this machine hosts the message server for the local network or joins one already running.
Only the host listens on TCP 26800. Other machines connect out to it.
3. Activate Plus, if you bought it
Run the command and paste the licence key from your purchase email. Repeat this on each machine covered by the subscription.
Free does not need an account or licence key.
4. Verify the connection
Inspect the running service, the server address, plan state, and any queued messages.
Install and set up Agent Fleet the same way on your remaining machines.
5. Start an addressable session
Agent Fleet can address sessions started through its launchers. The --name and --proj values form the session identity name@project.
Claude Code
Codex
Use the launcher that matches the agent tool on each machine. A session keeps its identity while it is running.
6. See the fleet and send a message
From another terminal, list sessions across the network and send a message by identity.
am peers lists sessions across the network. af-ctl ps lists only sessions running on the current machine.
Verify a release
The installer already checks the download
The installer reads the SHA-256 checksum for your platform from https://dl.woodor.ai/fleet/latest.json, calculates the checksum of the downloaded archive, and stops with diagnostics if they do not match. The commands below are an optional second check, not a step needed to make the installer safe.
Check the checksum yourself
Fetch the current release manifest, then calculate the checksum of the archive you downloaded. Compare the result with the sha256 value for your platform in the manifest.
Release manifest
macOS
Linux
Windows PowerShell
A matching checksum shows that the transfer was intact and that the archive matches the manifest. It does not prove who published the archive: the manifest and archive come from the same source, so someone able to replace one could replace the other. Publisher identity requires a signature check.
Check the publisher identity on macOS
The four native macOS executables in the release are signed with our Apple Developer ID. Check one directly:
The output should include Authority=Developer ID Application: OMI OPTICS USA LLC (UPT6L8973H) and TeamIdentifier=UPT6L8973H. OMI OPTICS USA LLC is the legal entity behind Woodor.AI. This identity check is anchored in Apple's certificate chain rather than a Woodor server.
Platform difference: the macOS executables are Developer ID signed. They are intentionally not notarized because the curl-based installation path does not apply a quarantine attribute. The Windows and Linux releases currently have no code-signing certificate, so users on those platforms can verify the checksum but not a publisher signature.
Keep your licence email
Your key is a credential. Keep the purchase email somewhere safe; if the key may have leaked, contact [email protected] for a replacement.
For a complete two-session walkthrough, read how to send messages between Claude Code and Codex.