Your engineers

Your roster: each engineer's name, role and status (ACTIVE, PAUSED…), with Chat and Settings, plus + Hire engineer. A warning shows if GitHub isn't connected: without a code host, engineers can answer questions but can't read code, implement or open PRs.

Engineer settings (owners and admins; members see a note):

• Details: Name, Avatar URL, Persona, Working conventions, Model, Max concurrent sessions, Meeting voice, Status (ACTIVE / PAUSED). Save changes.
  • Changing the model re-provisions the engineer; conversations already running keep the old model until they restart.
  • Max concurrent sessions caps how many things they run at once (chats, delivery steps, code reviews, meetings). Empty = unlimited. At the limit, people are told to try again shortly and queued delivery work starts by itself when a slot frees. Lowering it never interrupts work in flight.
  • PAUSED: the engineer doesn't respond to Slack messages or meetings.
• A newer-model card with Switch to … when one is available.
• Skills: tick skills and Save skills (this regenerates the engineer), or Create a custom skill.
• Authored pull requests: PRs this engineer opened and their state. Requesting changes on one brings the engineer back to push a fix.
• Danger zone: type the engineer's name, then Let {name} go. Retiring is permanent: they stop responding, and their usage history is kept.