Agentlas
Agentlas
← Back to app
Trust & safety

Projects & staffing

A project's agent roster and a Network search are two different mechanisms — one is a persistent list you curate, the other is a fresh search scoped to a single task.

A project has a fixed, ordered roster

A Project bundles a shared folder with an ordered agent pool. Position zero is always the controller for that project's work, and it must be an agent actually installed on the machine doing the work — a remote (Cloud or Hub) agent can be a member, but never the controller.

What changes that roster, and from where

Add a locally installed agent
Allowed from Desktop or a paired phone.
Reorder or drop a member
Allowed from Desktop or a paired phone.
Add a new Cloud or Hub member
Desktop only — remote agent membership is managed from Desktop.
Rename a member
Not possible from a phone at all — display names are always resolved by Desktop, never sent from mobile.

How this differs from Network staffing

The project roster decides which agents are available to the project and who controls it. A single task can also use a fresh Network search (Local + your Cloud + the public Hub) to find a specialist for that task, without automatically adding it to the project roster.

Projects & staffing · Agentlas docs