Skip to main content
A teammate is the real Claude Code or Codex, given a job. It has a name, role instructions, a model, and the Apps, Secrets and library access you choose. It works on a computer, on your own AI account, and every message to it opens or continues a thread.

Chief

Every workspace starts with a teammate called Chief, created with the workspace. Chief is your chief of staff and the first teammate you talk to. It has two jobs:
  • Set up the team. Chief asks what you’re building, what takes your time and which tools the work lives in, one or two questions at a time. Then it proposes a team, usually two or three teammates, each with a role, instructions and the Apps it needs.
  • Answer and route. Chief answers simple questions itself. For real work, it hands off to the right teammate: it mentions them, starts a sub-thread, or starts a thread of its own for them. It doesn’t do a teammate’s job itself.
  • Your rules and a daily pass. Chief writes your rules with you, and can go through what waits on you each morning to recommend what to do with each. See below.
Chief’s name can’t change, and it can’t be archived.

Your rules

Your rules are short lines in your words that say how you would answer your teammates, for example “Brigade: go ahead on next steps of work I asked for” or “Anything visual: ask me”. For now Chief only recommends by them, in its daily pass: your teammates still ask you, as before, and nothing goes without you. Write them in Preferences → Chief, or choose Write them with Chief there: Chief proposes a few lines from what you tell it and saves them once you agree. Its next pass reads them.

Chief’s daily pass

Turn on Daily pass in Preferences → Chief, and each morning from 7:00 (your timezone), when something waits on you, Chief goes through it in a thread of its own that no list shows. For now it only recommends: it answers nothing, tries nothing again and starts nothing in your name. It leaves it all to you on Today, under Chief’s pass:
  • For each question your teammates ended on (buttons or choices): the answer it would pick, why, and the rule of yours it goes by. Use it sends its pick as your answer. A design is always yours to pick.
  • For a thread that stopped on an error: whether it’s worth trying again, with Try again.
  • Tickets and pull requests: what it would do. They’re always yours.
  • How Chief reads you: how often its pick was your answer this week, by rule. It shows which of your rules Chief reads right.
  • What it noticed across your threads, and rules you may want to add from your recent answers (Add to my rules, or Not this one, and it won’t propose it again).
The pass takes at most one turn a day on your Claude or Codex subscription, and none when nothing waits on you.

The team proposal

Chief’s proposal shows as a card titled Your team. For each teammate you can choose Edit to change its Name and Instructions, or leave it out with the X. Under Apps this team needs, choose Connect for each App you haven’t connected yet; you can also create the team first and connect them after. Choose Create team to create them (owners and admins). Each new teammate gets access to the Apps it needs that are already connected, and its writes to Apps ask a person first. Change that on its Access tab. For an App you connect later, the card shows a Give button to grant it. Or write to Chief what to change.

Create a teammate

Owners and admins choose New teammate: the + next to Teammates in the sidebar. The form asks for: Then choose Create teammate. The avatar is generated for you.

Models

A Claude teammate runs on a Claude account, a Codex teammate on a ChatGPT account. Its threads need an account of that kind on the computer they run on. See AI accounts.
Codex can’t ask before running commands or editing files, so a Codex teammate’s threads run them without asking.

Write good role instructions

Write to the teammate as “you”, like a brief for a new hire:
  • Start with the role. The first line says what it does, for example “You handle customer support for Acme.” Chief reads that line to decide what work to send it.
  • Say what it owns: the inbox, the repository, the weekly report.
  • Say how it works: tone, where the answers are, what good looks like.
  • Say what to ask a person about first: refunds, anything sent to a customer, merging.
Facts that change belong in memory, and repeatable procedures in skills.

The teammate page

Open a teammate from the sidebar. Its page has four tabs.

Profile

The same fields as the creation form, with Save, and Archive. Only owners and admins see this tab.

Access

What the teammate may reach:
  • Document library: Read only (the default) or Read and write. Folders where its access differs, set in the library, are listed under it.
  • Mailbox: its own email address, if your workspace has the Email App.
  • Apps: one row per connected account, No access, Read only or Read and write. A personal App shows whose threads it works in.
  • Secrets: No access, Can use, asks first or Without asking for each.
  • Acts without approval (sending, editing, deleting): the policy for writes to Apps. Allow (the default), Ask a person first, or Never. See Apps.
  • Starts threads from: the triggers that start threads for this teammate.

Activity

A timeline of the teammate’s threads over the Last hour, Last 8 hours, Last 24 hours or Last 7 days, with totals for Working, Waiting for approval and Blocked.

Limits

Daily caps: Threads started, Computer hours and Write calls per connection. Reaching a cap pauses the teammate’s new work and opens a ticket for an admin. Days start at midnight UTC; an empty field means no cap. Owners and admins choose Edit caps. See Usage and limits.

Archive a teammate

On the Profile tab, choose Archive. Its threads stay. Its triggers are deleted, its routines stop running, and it can no longer be mentioned. There is no way to bring an archived teammate back yet, so create a new one if you need it again.

Who may do what

See Members for roles.