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

Folders: what the building sees

Without folders set, the building sees every Claude Code, Codex, Antigravity and GitHub Copilot session on the machine. On a laptop with personal projects, choose the work folders: anything outside them never leaves the machine.

When installing

Add the folders to the command, separated by commas:

curl -fsSL https://ai.fleetly.tools/install.sh | bash -s -- --token <token> --hook --pastas ~/work/shop,~/work/api

On Windows, use -Pastas "C:\work\shop,C:\work\api".

After installing

On the machine itself:

node ~/.fleetly/collector/fleetly-collector.mjs pastas
node ~/.fleetly/collector/fleetly-collector.mjs pastas add ~/work/other
node ~/.fleetly/collector/fleetly-collector.mjs pastas remove ~/work/other
node ~/.fleetly/collector/fleetly-collector.mjs pastas limpar

The first one lists the folders; limpar (clear) shows the whole machine again. Changes apply right away, with no restart. If the installer downloaded Node, replace node with ~/.fleetly/node/bin/node. On Windows, use node "$env:USERPROFILE\.fleetly\collector\fleetly-collector.mjs" pastas. You can also run the install command again with a different --pastas.

What changes for the building

A session outside the folders doesn’t exist for the hub: it disappears from the office, search, reports, the timeline, the summary, approvals, open sessions and previews. Its permission requests keep showing up only on the machine itself.

  • New sessions from the dashboard start only inside the folders.
  • The dashboard’s folder picker starts at the allowed folders and can’t go above them.
  • Settings → Buildings → Machines shows what each machine shows the building, without letting anyone change it.

Why it is safe

The list lives in a file on the machine (~/.fleetly/pastas.json) that no action from the hub writes. Only you, on the machine, can widen what it shows. If the file becomes unreadable, the machine shows nothing rather than everything.

Folders separate what the building sees and controls. They don’t stop an agent running on the machine from reading other folders of the same user, if you ask it to.

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