Set member defaults
Name the agent your team uses, and a new member’s first screen points them at it by name. It only points the way; no other agent is made unavailable.
How it works
Section titled “How it works”| What you do | What Agent Fleet does |
|---|---|
| Choose the default agent under Member defaults | Names that agent on a new member’s welcome card |
| Completes the step whichever agent the member connects |
A new member’s first screen is Home, with a welcome card at the top. The card’s second step is Connect an agent. Agent Fleet supports several agents, and a new member usually cannot tell which one the team pays for. Choose one here and the step then reads, for example, “Your team’s default is Claude (any other agent works too)”.
Choose the default agent
Section titled “Choose the default agent”- Open Tenant settings → Operations → Member defaults
- Under Default agent, choose one of Claude, Codex, Cursor, Copilot, Kiro, opencode and Muse, or None
- Press Save
- None brings back the ordinary wording that lists the choices
- Agents that need no account of the member’s own are not offered: the shell, SSM and the deployment’s inference engines. Who may use the inference engines is set under Resource limits and sessions
- Each save is recorded in the audit log as
tenant.member_defaults, with the agent chosen
When members see it
Section titled “When members see it”- Members read the default each time the Console loads, even while their workspace is stopped
- A member who already has the page open sees it after a reload
- The welcome card shows only until a member creates a first session or starts a first chat, so it matters for members who have not started yet
Which agents a member may use is decided by the member’s own accounts and by the deployment, not on this screen.