Managing your agent fleet and identities
This article shows you how to register and organize multiple coding agents per person or team, set identity metadata (name, project, type), use the fleet view, and run bulk actions where your plan allows.
Before you begin
- You need manager or org admin permissions to add or edit agents for others.
- Know which projects or repos each agent should represent so naming stays consistent.
Steps
- Open Dailybot and go to Agents, Fleet, or Agent identities (exact label depends on your workspace).
- Choose Add agent (or Register identity) to create a row for a new runner; link it to the user or service account that owns the token.
- Set Display name to something triagers recognize in Inbox and reports (for example, “payments-service — Cursor”).
- Set Project or Team tags so filters on the fleet and dashboard group related agents.
- Pick Agent type or Provider from the list (for example, CLI, IDE plugin, hosted worker) so health rules and docs match how the agent connects.
- Save the identity and confirm it appears in the fleet table with the expected status.
- Open the fleet or manager view and use column sort or filters to review all agents for a project before a release.
- Select multiple agents if bulk actions are enabled: pause, resume, rotate credentials, or apply the same tag in one pass.
- Document naming conventions for your org (prefix by squad, environment, or repo) so new identities do not duplicate purpose.
Identity fields reference
| Field | Why it matters |
|---|---|
| Display name | Shown in Inbox, alerts, and Home |
| Project / team | Filters fleet and reporting |
| Type / provider | Drives compatibility and troubleshooting paths |
What to expect after
Each agent has a clear identity in Dailybot, managers can scan the whole fleet quickly, and bulk updates stay consistent across similar runners.