Projects on a worker
Map dashboard projects to local checkouts, let the worker discover repositories on its disks, and clone repositories to a projects folder.
Agents run only inside project folders mapped on the worker. Usually you do not map anything by hand.
Discovery
Worker UI → Projects → Repositories on this computer: the worker scans every fixed drive (or the folders
you list) every six hours and on Scan now. It skips system, program, package-manager and build folders
(Windows, Program Files, AppData, node_modules, .venv, dist …), links and nested repositories.
- A clone of a repository that already belongs to a project is mapped automatically.
- Other repositories are suggested in the dashboard, where you accept or dismiss them.
- Only folder paths, names, branches, remote URLs and root commits are sent — never file contents.
AO_DISCOVERY_AUTOSTART=0turns off automatic scans.
Cloning
Set a projects folder in the worker UI. Repositories can then be cloned there from the dashboard (the project page's Clone to a worker, or a new GitHub repository). Clones use a token limited to that repository, passed to Git as a header and not stored in the clone.
Manual mapping
Map a dashboard project id to the absolute path of its checkout. For a project with several repositories, add one row per repository with its repository id.
The control plane can only map folders the worker found or cloned itself, never an arbitrary path.