Teams
Many agents become a few outcomes you can name and steer.
Group agents by the outcome they serve, not the window they happen to live in.
- a release crew
- a bug-bash squad
- a docs team
Group agents by the outcome they serve, not the window they happen to live in. A team in CodeAF is a named, coloured group of conversations. It is a grouping, not a place: one conversation can be in several teams at once, and making or changing a team never opens, closes or stops any work.
Try it in CodeAF
- Where
On the wall (Alt+V).
- Press
- Space on each tile you want in the team.
- S.
- Enter to keep the name, or type over it first.
- You see
The Teams row says
Made shop-api · 2: the tiles are now one named, coloured team.
Living with teams
The name is chosen for you, the shared folder's name when the chats sit in one project, and you can type over it before you press Enter.
Each team gets its own colour, drawn as a dot on every tile it holds. Show a team by pressing its name on the Teams row, or 1 to 9, and the wall and the tab strip narrow to its members. Tab steps to the next team. When some members are not open in this window, the title bar offers Open them. To file one conversation, press M on its tile: a list of every team opens with a box beside each, and a box you tick is saved at once. O runs Organize, which suggests teams from shared folders and one cheap model call. Nothing changes until you apply.
The teams page
Alt+2 opens the teams page: your teams as a tree on the left, with teams inside teams drawn under their parent, and the chosen team on the right. Its header names who is working and how many are idle, and what the team spent today. Its Settings card shows what the team inherits, such as team depth 3 levels and sub-team share 50%. Questions waiting on you arrive here as cards, each led by ? and ending in waiting on you.
A team on its own only groups work. Give it a manager and it becomes a unit that takes one goal and reports back; nest teams and give each a manager, and the tree on this page is your org chart.
Things to build
- A team per project: Organize turns a window of unrelated chats into named teams, one per folder, in one pass. Organize a messy window
- A shared chat: one conversation filed in two teams, so both walls show it without a copy.
- A capped sandbox: a team with its own daily cap on its Settings card, so its work stops at the cap and asks you once.
- A tree of teams: a platform team with api and infra under it, each with its own manager, drawn as one tree. Your org chart
Go further
Managers: give a team an agent that runs it.
Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.