Your team roster
Team is who works for you. Each AI coworker has a name, a role, a department and a record of what it has done, and the roster is organised the way an org chart is, because that is how people reason about a team.
FIG. 01
Four ways to look at it#
| Lens | What it shows |
|---|---|
| Org | The org chart. Departments, reporting lines, and who is working right now |
| Register | The flat list, faster to scan when you know who you are looking for |
| Skills | What the team can do, rather than who does it |
| Yours | Only the coworkers hired for you specifically |
The Org view updates live, so a coworker in the middle of a task is visibly in the middle of a task.
Opening a coworker#
A coworker page carries what it is for, what it is allowed to do, and its recent runs. That last part is the useful one: the honest way to judge a coworker is the work it has produced, not the description it was given.
If you are not sure who should handle something, you do not have to decide. Ask in Interact without mentioning anyone, and the team routes it.
Growing the team#
New coworkers are added through the hire wizard. See Hiring.
If something goes wrong#
- A coworker is idle when you expected work. Idle means nothing is assigned. Check Tasks for agent-ready work.
- Two coworkers look like they overlap. They often should. Departments handle related work, and routing decides per task.
- A coworker produced something off-brand. That is usually a context problem rather than a capability one. Check what it is reading in Brain.