Fleet on your phone

Fleet runs as an app on your phone. It tells you when an agent needs you, lists everything waiting on you across your machines, and lets you read, answer and steer each session. It is the same Fleet, served by your own machine.

• Your computer and your phone on the same Tailscale tailnet.

• Fleet behind tailscale serve, so the phone gets HTTPS:

  fleet --port 2113 --require-token
  tailscale serve --bg --https=443 http://127.0.0.1:2113

  HTTPS certificates must be switched on for the tailnet (admin console, DNS, HTTPS Certificates). --require-token is needed behind the proxy. See More machines.

• On iPhone, iOS 16.4 or later, with Fleet added to the Home Screen. iOS only sends web notifications to Home Screen apps. On Android, use Chrome.

Plain http:// still works, but only as a web page. Browsers only install apps and allow notifications over HTTPS (or localhost). The setup screen tells you this.

1. On the computer, open Settings → Machines → This machine and choose Add a phone. The first time, Fleet asks which address the phone should open. Use the https://<machine>.<tailnet>.ts.net one.
2. On the phone, scan the QR code with the camera. The page asks Connect this phone to your machine and lets you name the phone. Connect.
3. The phone now has its own key. Devices with access lists it, with when it was added and last seen.

A QR code works once and expires after 10 minutes. Each phone has its own key, so removing one signs out only that phone. A key that goes 30 days without use stops working. Pair again.

No camera? Open <address>/pair on the phone and type the code under the QR code (XXXX-XXXX).

Add a phone first checks what the phone needs and shows the command to run for anything missing: Tailscale, an https:// address, and Fleet asking for a key.

After pairing, the phone shows Notifications.

1. On iPhone, tap Share, choose Add to Home Screen, and open Fleet from its icon. On Android, choose Install Fleet, or Chrome’s menu, then Install app.
2. Pick what to hear about: Something needs me, An agent asks, A session finishes, A session fails. Quiet at my desk skips the phone while Fleet is open on a computer.
3. Choose Turn on notifications, then Send a test notification.

Tapping a notification opens the session at the question. On Android, a permission request also has Allow once and Deny on the notification itself.

Pushes go through your phone’s own push service (Google for Chrome, Apple for Safari). They are encrypted and carry only the machine, the session, a title and one line.

• Needs you lists everything waiting on you, on every machine. Choose Allow once, answer a question from the list, or choose More… for every option. Below it are sessions that are working and ones that finished.
• Sessions shows the last month. Open the full Fleet covers anything the phone view doesn’t do.
• New session lets you describe the task, then pick the machine, folder, harness and model.
• Machines shows which machines the phone reaches, and why not when it can’t.
• In a session, a run of tool calls is one row. Tap it for the steps. While the agent works you can queue a message or choose Send now to steer it mid-turn, where the harness allows it. The menu has Changes, Files, Terminal, Fork, Rename and Archive.

Terminals, the editor and app previews are not on the phone.

The machine the phone paired with is its home. Home sends notifications for every machine in its list, and gets the phone a key on each one the first time you open the inbox. Other machines must be reachable over HTTPS. One added by an http:// address shows as reachable only from computers.

If home is off, notifications stop for every machine.

Open Settings → Machines → This machine → Devices with access and choose Remove. The phone’s key stops working at once and its notifications stop.

• No notifications. Check that the bell is on and the test arrives. On iPhone, open Fleet from the Home Screen icon, not Safari, and check Focus modes. Check the home machine is running.
• Nothing from another machine. Check it is in the home machine’s list. The Machines tab shows why the phone can’t reach it.
• The QR code expired. Make a new one.
• No install option. The page isn’t HTTPS. Use the tailscale serve address.

• More machines: add another computer and keep it running.
• Sessions: what a session is and how to manage it.
• Security: how access tokens and keys work.