All pages
  1. Getting started
  2. Connect machines
  3. Folders: what the building sees
  4. Views
  5. Chatting with sessions
  6. Approvals and notifications
  7. Everyday tools
  8. Agent teams
  9. Code and Git
  10. Preview on your phone
  11. On your phone
  12. Plan usage
  13. Codex
  14. Antigravity
  15. GitHub Copilot
  16. Buildings, people and roles
  17. Command
  18. Enterprise: policy, SSO and reports
  19. Your account
  20. Subscription
  21. Keyboard shortcuts
  22. Troubleshooting
Docs

Preview on your phone

The agent started the dev server on localhost:3000, on your Mac, and you are on your phone. The preview opens that address through Fleetly, over the collector’s same outbound connection: no open port, no tunnel, no Tailscale.

Open it

  • In the session’s chat, tap Open preview :3000. The button shows up when the chat mentions localhost:<port> or when a server is running inside the project folder.
  • Or, in Details → Preview on your phone, pick one of the ports found or type the port.

The preview opens in a tab, at its own address, separate from the dashboard. When a file in the session folder changes, the page reloads on its own, about a second after the app responds again. It reloads the whole page: the dev server’s own hot reload (HMR) is turned off in the preview.

When the agent finishes a turn in which it changed files and an app is running in the session folder, the phone notification says Ready to test. Tapping it opens the session with the Open preview button highlighted.

On the computer itself, no tunnel: if the dashboard is open in a browser on the same machine where the app runs, Open preview goes straight to localhost:<port>, without going through the hub. The dashboard recognizes the machine in two ways: when you open it from the tray app (Open the dashboard or a session in the menu), and, in Chrome and Edge, by asking the machine’s collector. The first time, the browser asks to let the site access the local network: allow it. In Safari, only the first way works.

Next 16 in development mode: the preview doesn’t forward the dev server’s WebSocket, and Next 16’s next dev only finishes loading the page through it. If the preview stays blank, the page itself shows a notice: in the project, add experimental: { reactDebugChannel: false } to next.config and restart next dev, or use the built version (next build and next start). Vite and other servers work without changes.

Which ports show up

The collector lists ports opened by processes running inside the session’s folder, from 1024 up, that answer like a website. Databases and VMs stay out. It figures out on its own whether the port speaks http or https.

On Windows, automatic port detection is still off: type the port.

Who can, and for how long

  • Opening a preview requires the operator or owner role in the building, and opening and closing go into the audit log.
  • Each machine has up to 3 open previews; opening a fourth closes the least recently used one.
  • The preview closes on its own after 30 minutes without use, or 8 hours after it was opened. Close it earlier in Details → Preview on your phone.
  • Blocking someone’s account cuts their previews immediately.

How it is isolated

  • The app under test was just written by an agent, so it runs at an address separate from the dashboard: it can’t reach your login or Fleetly’s APIs.
  • Opening it creates a single-use ticket, valid for 60 seconds, that becomes access to that address only.
  • The collector only forwards to the open preview’s port, never to another service on the machine, not even if the hub asks.
  • Responses over 10 MB get a clear error.

Didn’t find what you were looking for? Write to admin@fleetly.tools.