6. A team: people and projects
Until now, one person used the fleet with the owner token. A team needs sign-in. Each member signs in with GitHub and gets their own user token. A project says who can spawn agents for a repo, and which secrets those agents get.
- An admin adds a member by GitHub login:
fleet member add <login>. The row binds at the first sign-in. - Roles: a fleet has
adminandmember. A project hasmaintainerandmember. - Each member's agents use only that member's profile.
- A secret is stored with
fleet secret set. A turn gets only the keys that its project names, as environment variables. See a secret to one turn. - A message from another member waits for the agent's next turn. It does not start a turn,
unless the owner sets
fleet wake <agent> project. The agent sees it marked as untrusted. fleet member rm <login>revokes the tokens, stops the agents, and erases the profiles and user secrets. See add and remove a person.- The page and the API need sign-in. A member sees only some panels. The panels about the box and the projects are for admins.
Details: a team with sign-in, sign-in.
Next: 7. Shared machines. Some machines run the turns of every member.