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

Connect machines

Each machine runs a collector, connected to the hub over an outbound connection. No open ports, no public IP, no tunnel: it works behind firewalls and NAT.

What the machine needs

  • macOS, Linux or Windows.
  • At least one agent, Claude Code, Codex, Antigravity or GitHub Copilot, installed and signed in for the user who will run the collector. Without one, the collector shows the sessions but can’t answer for them. If it’s missing, the installer offers to install it (see A machine with nothing installed).
  • Node 20 or newer. If it’s missing, the installer downloads a Node just for the collector, checked against the official SHA-256 (not available on Alpine Linux). The Mac and Windows app doesn’t need Node.
  • git, for the Code tab (commit and push) and teams. On Windows, Claude Code needs Git for Windows.
  • Run it as your own user, never as root or administrator.

Install

On a Mac: download, drag to Applications, open and sign in with your account (23 s).
On Windows: download, the Edge and Windows warnings, install and sign in with your account (45 s).
Then: install and sign in to Claude Code and Codex from the Set up an agent screen, no terminal (56 s).

In Settings → Buildings → Machines → Add machine → With a command, name the machine, tap Generate command and copy the command, which already includes its token. The token is valid only for that machine and can be revoked right there.

On Mac and Linux, paste it into the terminal:

curl -fsSL https://ai.fleetly.tools/install.sh | bash -s -- --token <token> --hook

On Windows, paste it into PowerShell (not as administrator):

& ([scriptblock]::Create((irm https://ai.fleetly.tools/install.ps1))) -Token <token> -Hook

The installer:

  • downloads the collector to ~/.fleetly/collector (on Windows, %USERPROFILE%\.fleetly\collector);
  • checks Node, the agents (Claude Code, Codex, Antigravity and GitHub Copilot), git and whether the hub answers, and offers to install what’s missing;
  • stores the token in a file only your user can read;
  • creates the service that starts the collector on its own: launchd on Mac, systemd on Linux (it asks for sudo to write the service) and a scheduled task at your login on Windows;
  • with --hook, asks before writing the Claude Code and Codex approval hooks, backing up the files first (see Approvals).

Mac: if your projects live in Documents, Desktop or Downloads, give Full Disk Access to the Node the installer shows (System Settings → Privacy & Security → Full Disk Access). Without it, the service can’t read those folders.

A machine with nothing installed

The installer and the app show what the machine has and what’s missing, with each tool’s official command for the system. In the terminal, the installer asks before installing each missing agent (and git on Mac and Windows); in the app, use Instalar under Agentes neste computador.

Mac and LinuxWindows
Claude Codecurl -fsSL https://claude.ai/install.sh | bashirm https://claude.ai/install.ps1 | iex
Codexnpm install -g @openai/codexnpm install -g @openai/codex or the Codex extension in VS Code
Antigravitycurl -fsSL https://antigravity.google/cli/install.sh | bashsee antigravity.google/cli
GitHub Copilotnpm install -g @github/copilotnpm install -g @github/copilot
gitMac: xcode-select --install. Linux: your package manager (sudo apt install git)winget install --id Git.Git

After installing, sign in to each agent from the panel: on the Set up an agent screen or under Settings → Buildings → Machines → Accounts on this machine (handy for a machine you’re not in front of), for Claude Code, Codex, Antigravity and GitHub Copilot. Copilot also uses the machine’s existing gh auth login.

To check again what’s missing, at any time:

node ~/.fleetly/collector/fleetly-collector.mjs diagnostico

Linux: Ubuntu Desktop ships without curl. Before the command, run sudo apt install -y curl. GitHub CLI (gh), VS Code and Python show up as optional: they’re for pull requests from the dashboard, for chatting with sessions open in VS Code and for the Claude plan % without the status line.

Command options

Mac and LinuxWindowsWhat for
--hook-HookWrites the Claude Code and Codex hooks, to approve from the dashboard and apply the building’s rules.
--pastas ~/work,~/other-PastasThe building sees only the sessions in these folders. See Folders.
--hook-port 4747-HookPortLocal port for the hooks. Change it if 4747 is already taken.
--dry-run-DryRunShows what would be done, without writing anything.
--trocar-TrocarConfirms moving to another building without asking, when the machine is already connected to one (see below).
--adicionar-AdicionarConnects the machine to this building too, without leaving the other one. Needs --pastas with this building’s folders (see below).
--pastas-atual ~/personal-PastasAtualWith --adicionar, the folders the previous building keeps seeing, if it saw the whole machine.

One machine, one building

Each machine connects to one building, unless you add it to more than one (see More than one building on the same computer). If you run another building’s command on it (with another account, for example), the installer tells you where from and where to, and asks whether to switch or add. Outside a terminal, it only switches with --trocar. From the app, the Connect page shows which building the machine leaves and which it joins, and only switches after you tick Got it and tap Move to this building.

  • After the switch, the old building sees the machine as Moved to another building (without knowing which one), its token there is revoked and the owner gets a phone notification. Everything goes to both buildings’ audit logs.
  • Reinstalling in the same building, with a new token, doesn’t ask anything: the old token is revoked and the old machine shows as Reinstalled.
  • On Enterprise, the owner can lock a single machine (Lock this machine, by tapping it in Settings → Buildings → Machines) or all of them (Lock the machines, in Settings → Buildings → Security): then the switch is refused until they unlock or revoke the machine in their building, and every attempt reaches their phone.

More than one building on the same computer

For people who work for more than one building under the same computer user, like your company and a client. Each building sees only its own folders, and no folder belongs to two.

In the Fleetly app (in Portuguese for now): in Configurar… → O que o prédio vê, click Adicionar outro prédio… (add another building). Pick the new building’s folders (and the current building’s, if it saw the whole computer) and click Entrar com a conta do novo prédio (sign in with the new building’s account). The menu then shows one line per building, and Sair de um prédio (leave a building) removes only that one.

In the terminal: run the other building’s command with --adicionar and its folders:

curl -fsSL https://ai.fleetly.tools/install.sh | bash -s -- --token <token> --adicionar --pastas ~/client

To check the machine’s buildings, fleetly-collector ligacoes. To change one building’s folders, fleetly-collector pastas --predio <id> add <folder>. To leave just one, fleetly-collector sair --predio <id>.

  • Each building sees sessions, git, approvals, previews, search and reports only from its own folders. A permission request goes only to the building that owns the folder, and only that building’s policy applies there.
  • Each building has its own approval mode (Automatic, Always here or Computer only). The app menu has one Aprovar em … (approve in …) per building; in the terminal, fleetly-collector aprovacao --predio <id> on.
  • Both buildings see the same computer name, operating system, Claude and Codex versions and plan usage, which is yours and not tied to a folder.
  • Each building’s owner sees in Settings → Buildings → Machines that the machine is also connected to another building, without knowing which.
  • On Enterprise with the machine locked (Lock this machine or Lock the machines), it belongs to that building only: connecting it to another is refused, even if the lock comes later, and the owner is notified.
  • An agent you run through one building runs as your user and sees the disk as usual. Folders limit what Fleetly shows and reaches, not what the agent can read.

Updates

The Fleetly app checks the hub for a new version one minute after it opens and every 6 hours. When there is one, the menu shows Instalar a versão … (install version …): one click downloads it, checks the package signature and restarts the app already updated (the collector inside it comes along). If you have version 0.1.0, install 0.1.1 once from the download; from then on, it’s from the menu.

The collector checks the hub’s version one minute after it starts and every 30 minutes, both the one installed by the command and the one inside the app. When there is a new version, it downloads it, checks the Fleetly publisher’s signature and the SHA-256 of every file, and restarts once no answer is in progress. There is nothing to do: in the app, collector updates don’t wait for a new app version. If the new version doesn’t stay up, the app goes back to the collector it shipped with.

Sign in to accounts remotely

On a machine you are not in front of (a server, a GitHub Codespace), you can sign in to Claude, Codex, Antigravity, Copilot and GitHub from the panel. In Settings → Buildings → Machines, tap the machine and then Accounts on this machine: the accounts show up as Signed in, Signed out or Not installed (with Install).

When the agent asks for a sign-in it can’t do itself (for example, “run gcloud auth login in the terminal”): on a machine that has the Google Cloud SDK, Accounts on this machine also shows Google Cloud (your account) and Google Cloud (application credential), the one Google’s libraries use. Tap Sign in, authorize on Google’s page, copy the code it shows at the end and paste it in the panel. In the chat, when the agent’s last answer contains the command (gcloud auth login, gcloud auth application-default login or gh auth login), the Sign in button appears right there; once connected, tell the agent to continue. The password and the code stay between you, Google and the machine.

  1. Sign in to Claude: the sign-in page opens by itself; authorize with your account and paste in the panel the code that appears. The machine keeps a long-lived token, only on itself.
  2. Sign in to Codex: the sign-in page opens by itself and the code is already copied: just paste it. If ChatGPT asks, first turn on device code sign-in in the ChatGPT security settings.
  3. Sign in to Antigravity: the Google page opens by itself; authorize with your account and paste in the panel the code that appears.
  4. Sign in to Copilot: the GitHub page opens by itself, with the code already copied: just paste it.
  5. Sign in to GitHub: the page opens by itself, with the code already copied. After that, the machine’s git clones and pushes your private repositories.

If the browser blocks the page, use Open the link. Only the building’s owner signs accounts in and out. The code is valid for 15 minutes. Passwords and tokens never go through the hub: the sign-in runs on the machine itself, with each vendor’s official program (claude setup-token, codex login --device-auth, gh auth login).

See what is going on

SystemCollector log
Mactail -f ~/Library/Logs/fleetly-coletor.log
Linuxjournalctl -u fleetly-coletor -f
Linux without systemd (container, Codespaces)tail -f ~/.fleetly/collector/coletor.log
WindowsGet-Content $env:USERPROFILE\.fleetly\collector\coletor.log -Wait

On Linux without systemd, the installer leaves the collector running in the background but does not start it again when the machine boots. Add to the machine’s startup (in Codespaces, the postStartCommand) the command the installer shows at the end: node ~/.fleetly/collector/fleetly-collector.mjs supervise.

System notifications

The Fleetly app on Mac and Windows uses system notifications when a session finishes and waits for you (Your turn), when the collector has no contact with the central for 5 minutes and, in Always here mode, when a permission request arrives. In Automatic mode the request already shows up in VS Code or the terminal, so it does not become a second notification. To turn them off, uncheck System notifications in the icon menu. The session shows up in the menu itself, to open in the dashboard.

Remove a machine

  1. In Settings → Buildings → Machines, tap the machine and use Revoke machine. The token stops working immediately and the machine leaves the building.
  2. On the machine, remove the service:
node ~/.fleetly/collector/fleetly-collector.mjs uninstall

On Windows, in PowerShell:

node "$env:USERPROFILE\.fleetly\collector\fleetly-collector.mjs" uninstall

If the installer downloaded Node, replace node with ~/.fleetly/node/bin/node (on Windows, $env:USERPROFILE\.fleetly\node\node.exe). The token stays in ~/.claude/painel/collector-token: delete the file if you won’t use it again.

From the machine itself: in the Fleetly app menu, use Sair do prédio… (leave the building). The token is revoked on Fleetly and deleted from the system keychain. With the collector installed by the command, node ~/.fleetly/collector/fleetly-collector.mjs sair --central https://ai.fleetly.tools revokes the token and removes the service. In an Enterprise building with machines locked, only the owner can remove the machine.

How many machines

Each machine has its own token, and revoking one doesn’t affect the others. The Personal plan has up to 2 machines; Team, 5 per paid person; Enterprise, no limit. See pricing.

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